mirror of
https://github.com/mattpocock/skills.git
synced 2026-09-12 10:28:06 +07:00
docs: sharpen the canonical install block after review
- install-block.md: state the invariant as a requirement rather than as already-true (docs/ is brought into line downstream); mark all three canonical snippets, not just the Claude Code one; pin the `skills@latest` spelling; restore the `setup-matt-pocock-skills` instruction the whole-set form carries; cite the docs source for the auto-update claim. - writing-docs.md: say plainly that the template's Quickstart is the older wording, so the file no longer contradicts itself. - CLAUDE.md: split the paragraph, stop restating the fallback rationale. - ADR 0002: record what was actually verified, on which version, and the two things that were not — the pinned sha in the official listing, and the in-session slash command. Refs mattpocock/personal-wiki#250 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Opus 5
parent
c474642895
commit
ad98b80dbd
@@ -9,7 +9,9 @@ Skills are organized into bucket folders under `skills/`:
|
||||
|
||||
Every skill in `engineering/` or `productivity/` (the **promoted** buckets) must have a reference in the top-level `README.md` and an entry in `.claude-plugin/plugin.json`'s `skills` array (the Claude Code plugin ships exactly the promoted set). Skills in `misc/`, `personal/`, `in-progress/`, and `deprecated/` must not appear in either.
|
||||
|
||||
`mattpocock-skills` is listed in **Claude Code's official marketplace** (`claude-plugins-official`), which is the one install route we document — see [.agents/install-block.md](./.agents/install-block.md) for the exact wording, and use it verbatim rather than rewording it per page. The repo is *also* its own single-plugin marketplace (`.claude-plugin/marketplace.json` lists the one `mattpocock-skills` plugin), kept only as a fallback for installing the repo directly; the official listing does not depend on it. When bumping the release version, keep `.claude-plugin/plugin.json`'s `version` in sync with `package.json`'s — Claude uses the plugin `version` to decide when installed users see an update. Run `claude plugin validate . --strict` after touching either manifest. Why a Claude plugin but not (yet) a Codex one lives in [.agents/adr/0002-ship-as-a-claude-code-plugin.md](./.agents/adr/0002-ship-as-a-claude-code-plugin.md).
|
||||
`mattpocock-skills` is listed in **Claude Code's official marketplace** (`claude-plugins-official`), and that is the one install route we document. Never reword an install command in place — copy it verbatim from [.agents/install-block.md](./.agents/install-block.md), which is the single source for install wording.
|
||||
|
||||
The repo is *also* its own single-plugin marketplace: `.claude-plugin/marketplace.json` lists the one `mattpocock-skills` plugin. The official listing does not depend on it, and it is not documented to users — it survives only as the fallback described in the install block. When bumping the release version, keep `.claude-plugin/plugin.json`'s `version` in sync with `package.json`'s — Claude uses the plugin `version` to decide when installed users see an update. Run `claude plugin validate . --strict` after touching either manifest. Why a Claude plugin but not (yet) a Codex one lives in [.agents/adr/0002-ship-as-a-claude-code-plugin.md](./.agents/adr/0002-ship-as-a-claude-code-plugin.md).
|
||||
|
||||
Each skill entry in the top-level `README.md` must link the skill name to its `SKILL.md`.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user