agent-authoring
ACTIVATE when creating a Claude Code subagent .md file, a VS Code Copilot custom agent/chat mode, or comparing agent formats across platforms. ACTIVATE for 'subagent', 'agent frontmatter', 'custom agent', 'chat mode', 'agent tools list', 'agent model field'. Covers: Claude Code agent frontmatter (name/description/tools/model/color), the `skills` preload field and its certification rules, VS Code Copilot's custom agent format (chat modes, tool lists, model pinning). DO NOT use for: SKILL.md conventions (see skill-authoring), plugin.json/marketplace.json (see plugin-conventions).
- License 许可
- MIT
- 最近更新
- 2026-10-13
- Stars
- ★ 9
- Forks
- 2
01 前言 Front Matter
- name
- agent-authoring
- metadata
- { "version": "1.0" }
- description
- ACTIVATE when creating a Claude Code subagent .md file, a VS Code Copilot custom agent/chat mode, or comparing agent formats across platforms. ACTIVATE for 'subagent', 'agent frontmatter', 'custom agent', 'chat mode', 'agent tools list', 'agent model field'. Covers: Claude Code agent frontmatter (name/description/tools/model/color), the `skills` preload field and its certification rules, VS Code Copilot's custom agent format (chat modes, tool lists, model pinning). DO NOT use for: SKILL.md conventions (see skill-authoring), plugin.json/marketplace.json (see plugin-conventions).
02 资源文件 2
- 参考文档evals/evals.json932 B
- 参考文档index.json480 B
03 SKILL.md 正文
Agent Authoring Conventions
Formats for defining an autonomous agent, sourced across the two platforms this marketplace ships agents for: Claude Code subagents and VS Code Copilot custom agents.
Claude Code Subagents
Source: platform.claude.com/docs/en/agents-and-tools/agent-skills/subagents.
---
name: agent-name
description: "One paragraph the orchestrator uses to decide when to delegate to this agent. Third
person, with <example> blocks showing Context/assistant/commentary when helpful."
tools: Read, Grep, Glob, Bash
model: sonnet
color: purple
skills: ["plugin-name:skill-name"]
---
Agent instructions in the body, same conventions as a SKILL.md body: imperative, no second person.
| Field | Required | Constraints |
|---|---|---|
name |
Yes | Kebab-case, must match the file's own purpose (not the filename, but convention keeps them equal) |
description |
Yes | The orchestrator's only signal for when to delegate — write it as a routing decision, not a summary |
tools |
No | Comma-separated allowlist; omit to inherit the caller's tools |
model |
No | One of sonnet, opus, haiku, inherit — any other value fails certification |
color |
No | UI hint, no functional effect |
skills |
No | Array of plugin:skill-name refs to preload; each ref must resolve to an existing SKILL.md and must not carry disable-model-invocation: true, or the agent cannot actually load it |
Agents live at <plugin>/agents/<agent-name>.md, one file per agent, discovered automatically —
no manifest entry needed unless plugin.json supplements the default path.
VS Code Copilot Custom Agents
Source: code.visualstudio.com/docs/copilot/customization/custom-chat-modes (custom agents, also
called chat modes).
---
description: "One-line summary shown in the agent picker."
tools: ["codebase", "terminal"]
model: gpt-4.1
---
Agent instructions in the body: scope, constraints, and the workflow this agent follows.
| Field | Required | Constraints |
|---|---|---|
description |
Recommended | Shown in the picker; no hard length limit documented, keep it a single sentence |
tools |
No | Array of tool names or tool-set names; unlisted tools are unavailable to the agent |
model |
No | Any model identifier the editor's model picker exposes; unset inherits the active chat model |
Custom agents live under .github/chatmodes/*.chatmode.md (workspace) or the user profile
equivalent — there is no plugin-relative path, unlike Claude Code subagents.
Cross-Platform Differences That Matter
| Aspect | Claude Code | VS Code Copilot |
|---|---|---|
| File location | <plugin>/agents/*.md, plugin-relative |
.github/chatmodes/*.chatmode.md, workspace-relative |
| Tool restriction | tools: allowlist, comma-separated |
tools: allowlist, array of tool/tool-set names |
| Model pinning | sonnet/opus/haiku/inherit enum |
free-form model identifier from the editor's picker |
| Preloading skills | skills: array, certified for resolvability and preloadability |
no equivalent field |
Do not port one platform's field names to the other verbatim — tools exists on both but takes a
different shape, and skills: has no VS Code counterpart at all.
See also: plugin-conventions for where the agent file sits inside a Claude plugin directory,
skill-authoring for the SKILL.md body conventions an agent's instructions should follow.
04 同仓库更多 Skills
vitest-test-conventions
ACTIVATE when writing Vitest tests, creating test files, using vi.fn()/vi.mock()/vi.spyOn(), or test factories. ACTIVATE for 'Vitest', 'it.each', 'NestJS testing module', 'supertest', 'vi.fn', 'vi.mock', 'spyOn'. Provides Vitest/NestJS-specific testing patterns; cross-language testing principles (DAMP, AAA, spy over mock, what NOT to test) live in craft:testing-principles. DO NOT use for: node:test files (a file importing node:test) or a project whose tests run under node --test (see node-test:node-test-conventions), TDD workflow/iterations (see vitest:vitest-tdd-workflow), PHP/PHPUnit tests (see phpunit:php-test-conventions).
vitest-tdd-workflow
ACTIVATE when building new features, endpoints, or user stories using TDD with Vitest in a TypeScript/NestJS context. ACTIVATE for '/feature-tdd-dev', 'TDD', 'red-green-refactor' in TS context. Provides Vitest/NestJS-specific TDD examples and commands; cross-language TDD workflow (cross-layer iterations, RED-GREEN-REFACTOR, working app, bug-fix-first-test, mocks-hiding-bugs) lives in craft:tdd-workflow-principles. DO NOT use for: node:test files (a file importing node:test) or a project whose tests run under node --test (see node-test:node-test-conventions), test writing conventions (see vitest:vitest-test-conventions), PHP TDD (see phpunit:php-tdd-workflow).
ts-refactoring
ACTIVATE when refactoring TypeScript code. ACTIVATE for 'refactor', 'extract', 'redesign', 'simplify', or 'clean up' in a TypeScript / Node / NestJS context. This skill provides TS-specific examples for the cross-language refactoring rules defined in craft:refactoring-principles. DO NOT use for: writing new features from scratch, general OOP patterns (see ts-oop).
ts-ports-adapters
ACTIVATE when a TypeScript codebase with no dependency-injection container has to declare a port and wire its adapter — a repository, a clock, an id generator, an event dispatcher the domain depends on. ACTIVATE for 'port', 'adapter', 'SPI', 'dependency inversion' or 'composition root' in a codebase that wires its dependencies by hand. Covers: the port as a type of functions in the domain layer, the adapter as an object literal annotated with it, the handler that takes its dependencies first and its data second, the composition root in the infrastructure layer, and the in-memory stub that substitutes for the adapter in a unit test. DO NOT use for: NestJS, or any container-based DI with decorators and tokens (see nest-ddd-conventions), aggregate operations and smart constructors (see ddd-ts-fp), the Result type itself (see ts-functional).
ts-oop
ACTIVATE when designing TypeScript classes, and the value objects or collections modelled as classes, or when the user asks about object design, encapsulation, Tell Don't Ask, or Symbol.iterator. Provides TS-specific examples for the cross-language OOP rules defined in craft:oop-principles, plus TS-specific patterns (Symbol.iterator, branded types for primitive identifiers). DO NOT use for: a value object or an aggregate modelled as an immutable record rather than a class (see ddd-ts-fp), refactoring methodology (see ts-refactoring).
ts-layer-boundaries
ACTIVATE when wiring a Worker entry point, a Router, a controller, or a domain event consumer in a TypeScript CQRS codebase, or when deciding where a port belongs. ACTIVATE for 'composition root', 'layer boundary', 'ESLint zones', 'domain must not import infrastructure'. Covers: the *Worker.ts composition root, the curried consumer, Router wiring of command endpoints, the five-gesture controller, the domain-to-infrastructure import boundary enforced by ESLint, infrastructure-only ports, in-memory doubles for every port, the read-can-reach-write asymmetry, and read endpoints going through a domain handler. DO NOT use for: the port's own shape and adapter binding (see ts-ports-adapters), the Result type (see ts-functional), domain event structure (see ts-ddd-events).