Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .claude-plugin/marketplace.json
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@
"source": "github",
"repo": "mattpocock/skills"
},
"strict": false,
"strict": true,
Comment thread
coderabbitai[bot] marked this conversation as resolved.
"description": "Curated picks from mattpocock/skills, tracking upstream.",
"skills": [
"./skills/productivity/caveman",
Expand Down
6 changes: 4 additions & 2 deletions .claude/skills/create-hoopit-skill/SKILL.md
Original file line number Diff line number Diff line change
Expand Up @@ -70,8 +70,10 @@ The `README.md` does **not** list individual skills (deliberately — it was a
maintenance burden), so adding a skill needs no README change.

`hoopit-matt-picks` is special: it has a `github` source pointing at
`mattpocock/skills` with `strict: false` and an explicit `skills` array, so its
skills resolve against *that* repo. To curate it, edit only its `skills` array in
`mattpocock/skills` with `strict: true` and an explicit `skills` array, so its
skills resolve against *that* repo. `strict: true` is required because the
upstream plugin ships its own manifest; it makes our `skills` list authoritative
instead of conflicting with theirs. To curate it, edit only its `skills` array in
the manifest.

## Checklist
Expand Down
5 changes: 3 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -46,9 +46,10 @@ each group gets its own directory rather than a shared top-level `skills/` (a
single shared folder would leak every skill into every plugin).

`hoopit-matt-picks` is the exception: it uses a `github` source pointing at
`mattpocock/skills` with `strict: false` and an explicit `skills` array listing
`mattpocock/skills` with `strict: true` and an explicit `skills` array listing
the specific skill paths to surface (a marketplace can list a plugin fetched from
a different repo).
a different repo). `strict: true` makes that curated list authoritative, so it
overrides the upstream plugin's own manifest instead of conflicting with it.

> **Adding or removing a Hoopit skill?** When working in this repo, Claude has a
> project-local `create-hoopit-skill` skill (under `.claude/skills/`) that
Expand Down