Install the plugin

Coding agents read skills from the antelopejs plugin, published in the AntelopeJS/agent-skills repository for Claude Code and Codex. The plugin keeps the project's skills folder in sync with the skills your installed packages ship: the framework skills from @antelopejs/core, the DMS, dms-frontend and every dms-* module. The skill catalog lists them all.

How a skill reaches the agent

Add the plugin

Run these commands once. The install lands in your user scope, so every project sees it:

claude plugin marketplace add AntelopeJS/agent-skills
claude plugin install antelopejs@antelopejs

/plugin marketplace add AntelopeJS/agent-skills
/plugin install antelopejs@antelopejs

codex plugin marketplace add AntelopeJS/agent-skills
codex plugin add antelopejs@antelopejs

npx -y github:AntelopeJS/agent-skills sync --target codex

Projects created from a template

template-dms-demo and template-dms-adonis ship a .claude/settings.json that declares the marketplace and enables the plugin. Claude Code offers to install it once you trust the folder: accept, and there is nothing else to do. Their AGENTS.md gives Codex the sync command.

{
  "extraKnownMarketplaces": {
    "antelopejs": {
      "source": { "source": "github", "repo": "AntelopeJS/agent-skills" }
    }
  },
  "enabledPlugins": {
    "antelopejs@antelopejs": true
  }
}

Commit the same file in an existing project to give every Claude Code contributor the same prompt.

How the sync works

In Claude Code, the plugin syncs at session start and again after every Bash command, so a pnpm install or an ajs run that adds a module brings its skills into the running session. In Codex, run the sync command after such a change.

• Which projects. A directory holding an antelope.config.* file, or an app whose package.json depends on @antelopejs/core: an embedded runtime such as the AdonisJS template. Anywhere else the sync does nothing.
• Where it looks, the first hit per package winning:
  1. the workspace: the current package, its parents up to the repository root, and the packages of the root's pnpm-workspace.yaml or workspaces field (source checkouts and module playgrounds);
  2. node_modules of the project and of the workspace root, pnpm's symlinks included;
  3. .antelope/cache, where ajs downloads the modules declared in antelope.config.ts.
• What it creates. One relative symlink per skill, named <package>--<skill> after the package's short name: dms--dms-pages, dms-frontend--dms-frontend, dms-mailing--dms-mailing. The link follows the installed package, so the skill always matches its version.
• What it leaves alone. It records its entries in an .ajs-managed.json inside each skills folder and lists them in a generated .gitignore next to it, so your repository stays clean. A skill of yours with the same name is reported and skipped, never overwritten, and entries whose package disappeared are removed.

Update and uninstall

The synced skills follow your packages, not the plugin: upgrade @antelopejs/core, @antelopejs/dms or a module, and the next sync points at the new version. The framework skills ship with @antelopejs/core from its first release after 1.15.2; a project on an older core gets them once it upgrades.

claude plugin marketplace update antelopejs
claude plugin update antelopejs@antelopejs

claude plugin uninstall antelopejs@antelopejs
claude plugin marketplace remove antelopejs

codex plugin marketplace upgrade antelopejs

codex plugin remove antelopejs@antelopejs
codex plugin marketplace remove antelopejs

To drop the synced skills from a project, delete the entries listed in .claude/skills/.ajs-managed.json and .agents/skills/.ajs-managed.json, then those files and the .gitignore next to each.

Next steps