Skip to content

Plugin Manifest Schema

The toolkit follows Anthropic’s plugin spec — a single marketplace manifest at the repo root listing each plugin, plus a per-plugin manifest under each plugin directory.

.claude-plugin/marketplace.json lists every plugin shipped by this marketplace. Plugins must appear in alphabetical order by name — CI will check this once the validators land in V1.5 (see CI Validators).

{
"name": "acn-claude-toolkit",
"owner": { "name": "ACN FDE Platform" },
"plugins": [
{ "name": "acn-base-sdlc", "source": "./plugins/acn-base-sdlc" },
{ "name": "acn-pursuit-toolkit", "source": "./plugins/acn-pursuit-toolkit" },
{ "name": "acn-slide-gen", "source": "./plugins/acn-slide-gen" }
]
}

source is a relative path to the plugin directory.

plugins/<name>/.claude-plugin/plugin.json describes a single plugin.

FieldTypeNotes
namestringMust match the directory name and the marketplace.json entry. Kebab-case.
versionstringSemVer. V1 plugins are at 0.1.0.
descriptionstringOne-sentence summary visible in /plugins list.
authorobject{ name, email }
keywordsstring[]For discovery — pursuit, sdlc, slides, etc.
{
"name": "acn-base-sdlc",
"version": "0.1.0",
"description": "Universal SDLC engineering practices — /review, /tdd, /commit, /pr skills with ACN security/testing/documentation rules and code-reviewer / security-auditor / debugger agents",
"author": {
"name": "ACN FDE Platform",
"email": "felix.i.n.d.alvez@accenture.com"
},
"keywords": ["sdlc", "code-review", "tdd", "pr", "commit", "acn"]
}

A plugin directory must contain plugin.json plus at least one of:

  • skills/<name>/SKILL.md — slash-command-invocable workflows
  • rules/<topic>.md — always-on system context
  • agents/<name>.md — specialist subagents
  • commands/ — alternate slash-command location
  • hooks/ — event hooks

A plugin with only a manifest does nothing. See Adding a Plugin for the new-plugin workflow.