Field noteNov 10, 20266 min read1 source

genesis-skills: repository for genesis mission skills for AI coding tools

In one minute

AI-ModCon’s Genesis Skills repository packages reusable procedures for scientific and engineering work as Agent Skills that can be exposed to several coding-agent clients. For teams exploring AI-assisted research, it offers a concrete way to test domain-specific workflows without building a new application, while leaving tool access and client compatibility to check skill by skill.

What happened

The public repository describes Genesis Skills as a collection of reusable Agent Skills for scientific discovery and engineering workflows, developed as part of the Genesis Mission. It lists Claude Code, Codex, Cursor, OpenCode, Gemini CLI and LangChain Deep Agents as compatible clients. The repository cautions that individual skills may still depend on client-specific features or external tools, so compatibility with a listed client does not establish that every skill works identically in every environment.

The repository defines a skill as Markdown files, with SKILL.md as the entry point and YAML frontmatter. Skills can combine domain expertise, tool access, structured workflows and supporting resources such as scripts, templates and references. Examples of areas named in the README include literature, high-performance computing, plasma simulation, scientific-data metadata and AI-system evaluation. The repository says an agent can select a skill based on a natural-language request; menus and explicit invocation shortcuts vary by client.

Genesis Skills presents two installation approaches. One uses unpack.sh to flatten the repository’s nested skills/<domain>/<skill>/ structure into a client’s configured skills directory. The script can copy or symlink skills, target a particular domain, list items for preview or show help. The README identifies $HOME/.agents/skills as an example for Codex, Cursor, OpenCode and Gemini CLI, and $HOME/.claude/skills for Claude Code. It says an explicit target is the client-neutral choice, notes that the legacy default is .claude/skills, and warns that existing same-named destination entries are replaced.

The second approach is to expose the included skill-search skill. Its README says it can discover the nested catalog through progressive disclosure or keyword search; a central clone can be specified for shared use. LangChain Deep Agents instead receive a catalog path in code rather than automatically discovering a user-level directory. The README advises following a client’s documented refresh behavior if a newly installed skill is not immediately recognized.

The repository groups skills into areas including scientific-data movement and APIs, data formats, evaluation, safety, HPC and plasma simulation. The top-level README includes example requests such as finding recent papers on machine-learning interatomic potentials or drafting a Slurm script for four GPUs. GitHub showed 37 stars, 16 forks and 83 commits when the page was captured. The repository is public and lists a BSD-2-Clause license at its root, but says some subdirectories contain third-party materials governed by separate licenses. It directs development, issues and pull requests to GitHub and identifies a read-only GitLab mirror.

What the archive adds

New Runtime’s earlier coverage described K-Dense-AI’s Scientific Agent Skills as a portable procedural layer for scientific agents. That earlier note makes Genesis Skills a new repository in a developing category, not a wholly new approach: both package research procedures as skills rather than as a single research application. Earlier coverage of Docker’s skills repository also examined distributable guidance for coding agents (New Runtime’s note). Genesis adds a science-and-engineering catalog and describes cross-client installation and search options.

Trend signal

Genesis Skills supports the pattern of skills becoming a portable capability layer: the repository presents domain procedures as installable units that can be exposed to multiple agent clients. The fit is qualified, since the README itself warns that individual skills may rely on client-specific features or external tools. The pattern is captured in Skills become a portable capability layer. The practical test is not simply whether a skill file can be copied, but whether its instructions, tools and dependencies behave reliably in the target agent.

Why now

The repository’s Genesis Mission framing connects its catalog to an effort to make AI-powered tools for science and engineering. Its README emphasizes access for researchers regardless of machine-learning expertise, acceleration from hypothesis to insight, reproducibility and collaboration. The publication therefore puts reusable workflow instructions alongside goals that require repeatable, inspectable computational work. The repository does not quantify whether its skills have yet advanced those goals.

Connections to other events

New Runtime’s earlier coverage of K-Dense-AI’s scientific skill collection described scientific agent capability as a portable procedural layer rather than a bundled research application. Genesis Skills meets that approach with a separate catalog oriented to science and engineering, while spelling out installation and search methods across several clients. New Runtime also covered Docker’s repository of agent skills for container work. Together, these repositories show the same packaging idea being applied to different domains; they do not establish shared infrastructure, coordinated development or comparative performance.

Why it matters

For a research or engineering team, the useful proposition is not that an agent now knows a scientific field. It is that some recurring procedures can be represented in a form an agent client can discover and follow, with supporting scripts and references alongside instructions. That can make a workflow easier to reuse than a prompt copied informally between projects.

There is also operational work hidden in the portability claim. Teams still need to confirm which tools a skill invokes, whether those tools are available and authorized in their environment, and whether the client handles discovery as expected. The README’s warning about client-specific features and external dependencies is important: a shared catalog is not the same as a universal runtime. Likewise, the root license does not settle reuse rights for every subdirectory, because the repository identifies third-party exceptions. A measured trial of one task can show whether the package saves setup effort without assuming the catalog as a whole is production-ready.

Limits and uncertainty

The repository’s README describes intended workflows and installation paths, but does not report independent evaluations of task accuracy, reproducibility or time saved. GitHub’s stars, forks and commit count are visible engagement indicators, not evidence that the skills work reliably in research settings. The repository does not establish that every listed client supports every skill or that external services and tools are available to every user. It also notes varying licenses for third-party subdirectories, so teams need to inspect the relevant attribution and license files before redistribution. No comparative results against unassisted work or other skill catalogs are stated.

Skill to build now

Choose one repetitive task in a scientific workflow, such as preparing a scheduler script or organizing literature searches. In a disposable project, install only the relevant skill using unpack.sh with an explicit client-appropriate target, then inspect its SKILL.md, scripts, required tools and license. Run the same task with and without the skill, and record missing dependencies, corrections needed and whether another team member can reproduce the result. This tests the repository’s concrete promise without granting broad access by default.

Reader takeaway

Genesis Skills makes scientific and engineering procedures available as reusable agent skills, with practical ways to install or discover them across several clients. Treat that as a starting point, not proof of portable performance: select one workflow, check its dependencies and license, and validate its output in the environment where the work will actually run.

Evidence / sources

  1. 1github.com/AI-ModCon/genesis-skills
All Field Notes

Next reads

Read next

Open the graph
  1. 01topicSkillsExplore the skills topic hub.
  2. 02topicClaudeExplore the claude topic hub.
  3. 03topicClaude CodeExplore the claude-code topic hub.
  4. 04archiveField NotesOpen the latest editorial analysis.
  5. 05sourcesSourcesSee the original sources this archive cites.
Who read this page?Machine requests, hidden until opened

Loading the privacy-safe route aggregate...

Open the JSON contract