Answer: Every component key accepts a path relative to the plugin root; `commands` takes a path, an array of paths, or an object map, and `hooks` takes a `.json` file path, an inline hooks object, or an array mixing both. Status: Confirmed Entry: tool/claude-code/settings/plugin-component-paths Revision: 4 Digest: sha256:2a5308ddab939fbd (changes whenever the content changes) Timeline: Created: 2026-11-13T03:05:06Z Last changed: 2026-11-20T12:23:20Z (path-only fields: — → `agents`, `skills`, `outputStyles`, `workflows`, and `experimental.themes` take one path or an array of paths.) Last verified: 2026-11-20T12:23:20Z Next check: 2026-11-21T12:23:20Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of general path rule | a path relative to the plugin root | [1] | 2026-11-20 commands accepted forms | a path, an array of paths, or an object map | [1] | 2026-11-20 commands source field | Path to the command's Markdown file, relative to the plugin root | [1] | 2026-11-20 hooks accepted forms | a `.json` file path, an inline hooks object in the same shape as [`hooks` in `settings.json`](https://code.claude.com/docs/en/hooks#configuration), or an array mixing both | [1] | 2026-11-20 hooks file wrapper | A hooks file wraps the event map in a top-level `"hooks"` key | [1] | 2026-11-20 path-only fields | `agents`, `skills`, `outputStyles`, `workflows`, and `experimental.themes` take one path or an array of paths. | [1] | 2026-11-20 Sources: [1] Anthropic. "Plugin manifest reference". https://code.claude.com/docs/en/plugins/manifest-reference.md Role: primary. Accessed: 2026-11-20T12:23:20Z Quote: "Every component key accepts a path relative to the plugin root." (Supports: general path rule) Quote: "`commands` takes a path, an array of paths, or an object map." (Supports: commands accepted forms) Quote: "Path to the command's Markdown file, relative to the plugin root" (Supports: commands source field) Quote: "`hooks` takes a `.json` file path, an inline hooks object in the same shape as [`hooks` in `settings.json`](https://code.claude.com/docs/en/hooks#configuration), or an array mixing both." (Supports: hooks accepted forms) Quote: "A hooks file wraps the event map in a top-level `"hooks"` key" (Supports: hooks file wrapper) Quote: "`agents`, `skills`, `outputStyles`, `workflows`, and `experimental.themes` take one path or an array of paths." (Supports: path-only fields) Published: 2026-11-20T02:54:47Z Snapshot SHA-256: 881277b37c7b02ec0c5212ee0d1a4498de38c52a3e83b9fc2f0853ed16a76504 (captured 2026-11-20T12:23:18Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. Cross-check: not-available at 2026-11-20T12:23:20Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:23:20Z Last attempt: 2026-11-20T12:23:20Z Notes and limitations: Extracted automatically from a single official source (section "Component path forms"). Related: https://latestn.com/tool/claude-code/settings/plugin-environment-variables How do environment variables resolve in Claude Code plugins? https://latestn.com/tool/claude-code/settings/plugin-install-scopes What are the install scopes for Claude Code plugins? https://latestn.com/tool/claude-code/settings/plugin-manifest-fields What fields can I set in a Claude Code plugin's plugin.json manifest? https://latestn.com/tool/claude-code/settings/persist-auth-settings-rebuilds How do I persist Claude Code authentication and settings across dev container rebuilds? https://latestn.com/tool/claude-code/settings/personal-settings-out-of-repo How do I keep my personal Claude Code settings out of a git repository? https://latestn.com/tool/claude-code/settings/plugin-auto-update-timing How does Claude Code decide when to auto-update marketplaces and plugins? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-20T12:23:20Z | changed | path-only fields: — → `agents`, `skills`, `outputStyles`, `workflows`, and `experimental.themes` take one path or an array of paths. | [1] 2026-11-18T12:18:35Z | changed | commands source field: — → Path to the command's Markdown file, relative to the plugin root | [1] 2026-11-18T12:18:35Z | changed | path-only fields: `agents`, `skills`, `outputStyles`, `workflows`, and `experimental.themes` → — | [1] 2026-11-18T12:18:35Z | changed | hooks file wrapper: a top-level `"hooks"` key → A hooks file wraps the event map in a top-level `"hooks"` key | [1] 2026-11-18T12:18:35Z | changed | commands path target: a flat `.md` command file or a directory → — | [1] 2026-11-13T12:12:47Z | changed | path-only fields: — → `agents`, `skills`, `outputStyles`, `workflows`, and `experimental.themes` | [1] 2026-11-13T12:12:47Z | changed | commands source field: Path to the command's Markdown file, relative to the plugin root → — | [1] 2026-11-13T03:05:06Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/claude-code/settings/plugin-component-paths/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/claude-code/settings/plugin-component-paths POST: https://latestn.com/dispute/tool/claude-code/settings/plugin-component-paths with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/claude-code/settings/plugin-component-paths?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I specify component paths like commands or hooks in a Claude Code plugin manifest? Revision 4, last verified 2026-11-20T12:23:20Z. https://latestn.com/tool/claude-code/settings/plugin-component-paths (accessed 2026-11-21T09:50:32Z). @misc{LatestN_tool_claude_code_settings_plugin_component_paths_r4, title = {How do I specify component paths like commands or hooks in a Claude Code plugin manifest?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/claude-code/settings/plugin-component-paths}}, note = {Revision 4; digest sha256:2a5308ddab939fbd; last verified 2026-11-20T12:23:20Z; accessed 2026-11-21T09:50:32Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/claude-code/settings/plugin-component-paths