AGENT SKILL

add-agent-to-repo

暂无简介

License 许可
MIT
最近更新
2026-05-27
Stars
★ 0
Forks
0

02 资源文件 1

03 SKILL.md 正文

Add an agent to the repository

Use this skill when the user wants to add a new agent to this agent-skills repository so it appears in the catalogue and is installable from the VS Code extension.

When to use

  • "Add an agent that does X to the repo"
  • "Publish this sub-agent definition"

Layout you must produce

Agents live under examples/agents/ and are seeded into the agents Azure Blob container. Each agent is its own directory; the path below examples/agents/ becomes the agent id. The marker file must be named after the directory: directory browser-smoke-tester/ → marker browser-smoke-tester.md. Only that .md file is installed.

examples/agents/<category>/[<sub>/...]/<agent-name>/
├── <agent-name>.md   # REQUIRED — marker, name MUST equal the directory name
└── agent.yml         # optional — metadata for the catalogue UI

Steps

  1. Pick a category + name, mirroring the existing tree (e.g. examples/agents/testing/browser-smoke-tester/).
  2. Write <agent-name>.md. This is the agent definition Claude Code installs. The filename must match the directory name exactly, or the API will not detect the agent.
  3. Write agent.yml (recommended; same schema as skill.yml):
    name: Browser Smoke Tester
    version: 1.0.0
    author: Your Name <you@example.com>
    description: One-line summary shown in the tree tooltip.
    tags: [testing, browser]
    
  4. (Optional) Declare dependencies. Agents commonly need a skill or an MCP. Add a dependencies list to agent.yml:
    dependencies:
      - type: mcp
        id: browser/playwright
      - type: agent
        id: testing/some-other-agent
    
    id is the path below the type root. Unknown types, missing id/type, and duplicate entries are ignored. Dependencies are resolved transitively at install time.
  5. Publish. From api/:
    npm run seed             # overwrites same-named blobs
    npm run seed -- --wipe   # only if you removed/renamed files
    
  6. Verify. Restart the API (or ?refresh=1) and open the agent in the extension to check metadata, dependencies and the marker .md content preview.

Validation checklist

  • [ ] The marker .md file name equals the directory name exactly.
  • [ ] agent.yml name/version/author are filled; bump version when editing an existing agent so the "update available" badge fires.
  • [ ] Any dependencies ids actually exist in their catalogue.

04 同仓库更多 Skills