Lighthouse AdvisorySLED AI Adoption Intelligence
← Back to results

From the Research Universities edition of October 29, 2026

Independent reportingEmergingPeer review status unknownNew this fortnight

DOE releases 35 Genesis Mission agent skills packaging national-lab know-how for Claude Code, Codex, Gemini CLI and other coding agents

U.S. Department of Energy (ModCon BASE team, co-led by PNNL and Berkeley Lab), reported by R&D World · Federal research infrastructure and national laboratories · United States

Publisher
R&D World
Original publication
29 October 2026 (R&D World)
Source retrieved
2026-10-30
Read original source

What happened

R&D World reports that DOE released 35 skills for AI coding agents as the first technical resources from ModCon and the American Science Cloud under the Genesis Mission. The skills follow the Agent Skills format (a folder built around a SKILL.md file). Twenty-three include Python or shell scripts; the other 12, including job-scheduling guides for the Frontier, Aurora and Perlmutter supercomputers, are text only. They cover HPC schedulers, data tools such as data cards, AI safety analysis, American Science Cloud clients such as Globus Compute, literature search and multi-agent systems. Documentation says they work with Claude Code, Codex, Cursor, OpenCode, Gemini CLI and LangChain Deep Agents, though individual skills may depend on client features. Researchers at seven national labs wrote them. The contribution guide permits disclosed AI-assisted work and requires a human reviewer on every pull request; eight of 69 commits list Claude or GitHub Copilot as co-author.

Why it matters

University research computing centers already write user guides for schedulers and data services; DOE has shown a way to publish that know-how so researchers' coding agents use it correctly. Universities with allocations on DOE systems can use these skills directly.

Evidence and measured results

Read the full article, which draws on the repository and its attribution files. No usage, accuracy or adoption data is reported, and the repository was not inspected directly.

Limitations and uncertainty

Trade press report; claims about compatibility come from project documentation and were not tested. No evidence yet that the skills improve agent accuracy. Federal terminology (SI) and the Genesis Mission context are U.S.-specific.

Put this evidence to work

Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-29; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.

Sales

Role takeaway
Customer problem
Researchers use general coding agents that do not know local cluster rules, producing broken job scripts and support tickets.
Stakeholders
  • Research computing director
  • HPC user-support lead
  • CIO
  • Research data management lead
Discovery questions
  • Which coding agents do researchers use on your clusters?
  • What share of support tickets involve job-script errors?
  • Do you hold allocations on DOE systems?
Value hypothesis
Published local skills may reduce agent-generated job errors and support load, if tested.
Potential engagement
Author and test a starter set of skills for the institution's scheduler and data services.
Unsupported claims
  • Accuracy or productivity gains
  • Uniform compatibility across all agents
  • Adoption by researchers

Pre-sales engineering

Role takeaway
Fit
Fits institutions whose researchers use coding agents on shared clusters.
Architecture and integration
SKILL.md-based folders with scripts, distributed through a repository and loaded by multiple coding agents.
Prerequisites
  • Current scheduler and storage documentation
  • Tested job templates
  • Repository with review workflow
Constraints
  • Skills may depend on client-specific features
  • Local policies differ from DOE systems
  • No evaluation data
Security
Review runnable scripts before publication and avoid embedding credentials or internal hostnames.
Proof of value
  • Compare job-script error rates with and without skills
  • Test each skill on at least two agents
  • Track support tickets after release

Delivery

Role takeaway
Work
Write, test and version skills for local systems; publish with documentation updates.
Dependencies
  • Scheduler and storage teams
  • Repository hosting
  • Agent tools researchers use
Ownership
Research computing user-support team.
Skills and adoption
Support staff learn skill authoring; researchers learn to install and update skills.
Governance checkpoints
  • Human review on every change
  • Disclosure of AI-assisted contributions
  • Re-test after system upgrades
Acceptance criteria
  • Fewer failed agent-generated submissions over a term (proposal)
  • Every skill tested on two agents
  • Skills updated within an agreed time after system changes
Risks
  • Stale skills after system changes
  • Scripts with unsafe defaults
  • Researchers trusting agents without checks

Implementation considerations

Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.

Architecture and integration

What must connect, and where does the AI sit in the workflow?

Agent skills become a distributable layer of site-specific documentation and scripts sitting between general coding agents and HPC or data services.

Governance

Who approves, reviews and stays accountable for outcomes?

Human review on every pull request and disclosure of AI-assisted contributions are concrete controls for shared agent instructions.

Security and privacy

What data, permissions and controls need testing?

Skills that include runnable scripts need review before use; individual skills may depend on external tools.

Accessibility and workforce

Who is affected, and what skills or accommodations follow?

Could lower the barrier for researchers new to supercomputer job submission, but is not evaluated.

Procurement

What should contracts, pricing and exit terms secure?

Skills are client-neutral, reducing lock-in to one coding agent; frontier AI companies are Genesis partners.

Operating model

Which teams own the service once it runs?

Research computing staff may maintain agent skills alongside user documentation.

Publication history

  1. 2026-10-29Research Universities · Issue 514 resources
Read preserved resource versions (JSON)

Stable resource ID: doe-genesis-mission-35-agent-skills-national-labs-20261029