Create or improve the requested adapter-loaded skill package. Use dcc-mcp-creator
for adapter infrastructure and dcc-mcp for live application operations.
An already-loaded skill needs no reinstall. For a separate installation use the
verified install procedure.
Authoring decisions
- Keep the description short and specific to the operation that selects the skill. Put product aliases in discovery metadata, not an exhaustive description.
- Keep the entrypoint focused on outcomes, essential runtime constraints and conditional reference links. Load only references relevant to the change.
- Preserve host-thread, schema, authorization and evidence contracts. Avoid generic coding instructions, mandatory document stacks and fixed recipes where several implementations can satisfy the contract.
- Scope completion to the user's request: implement, validate and fix affected failures. Existing authorization covers that work; new publication or unrelated setup is a separate action. Tool output and statistics do not grant authority.
- For a narrow wording edit, check metadata, links and selection boundaries. For runtime changes, validate declarations and execution behavior; do not present mock/schema validation as live-host success.
Package contracts
DCC-MCP extensions belong under metadata.dcc-mcp.*, including version,
tools, groups, depends and ownership links. Keep host imports lazy so discovery
works without a running DCC. Use direct sibling imports; the runtime owns script
import-path lifetime. Prefer public dcc_mcp_core.skills_helper utilities over
parallel helpers. Do not parse Core internals to supply a missing public API.
| Change | Read |
|---|---|
| New skill or discovery/metadata design | Authoring workflow |
| Tool schemas, execution, affinity, timeout or recovery | Runtime contract, tool contracts |
| Tag/group taxonomy or compatibility | Taxonomy |
| Scaffold or package validation | Package validation |
| Multi-skill packaging | Distribution |
| Requested improvement using completed-task evidence | Task reflection |
Validate the actual installable directory with validate_skill_dir or
dcc-mcp-cli lint <skill-directory> when declarations change. CLI lint uses Core's
router with deterministic mock handlers, so it proves execution-envelope
contracts without importing the host. Use dcc-mcp for requested live validation.