Matt Pocock skills
A skills provenance explorer: a practical extension for this repository
Design a local read-only explorer for promoted inventory, invocation metadata and version drift; distinguish a proposed learning tool from an upstream roadmap.
What you will learn
- Build around a question the current files can answer
- Keep provenance and mutation separate
- Prefer an accessible two-dimensional explanation
Before you start
- Basic repository, issue-tracker and test concepts
- An understanding that instructions and permission are different
Choose an adoption model and trace its files, authority boundaries and verification evidence.
Key takeaways
- An inventory explorer should expose source paths behind each count.
- Consistent source metadata does not prove an installed update.
- The proposed explorer remains read-only and is not a shipped application.
Build around a question the current files can answer
A useful extension would answer: which skills would this distribution expose, and which source files justify that answer? Read the pinned plugin list, locate each SKILL.md and its host metadata, and show the bucket and invocation declarations. This is a proposed local inspection tool, not a feature shipped by the repository or delivered as an interactive application in this article.
The existing 25-versus-33-versus-37 distinction makes a good first dataset. Let a reader switch between the promoted manifest, development-link selection and complete tree. Each count should expose the selected paths, not merely animate a number. Missing targets or inconsistent invocation declarations should be visible findings, not silently repaired by the viewer.
Keep provenance and mutation separate
A second view could trace package version, plugin version and a manually supplied installed revision. The executed version-script fixtures provide concrete examples of agreement, mismatch and guarded refusal. The explorer should label what it read, what it inferred and what remains unverified; a consistent manifest alone must never become an installed-update badge.
Keep the first version read-only. It should not run installers, create user-level links, change issue labels or execute instructions embedded in skill text. If repair operations are added later, give each a separately reviewed diff and explicit approval step. This design constraint limits surprising side effects while still teaching the repository’s real structure.
Prefer an accessible two-dimensional explanation
A table of source paths and a small dependency graph would communicate this information more directly than a 3D scene. The static diagrams delivered with this series illustrate the intended relationships, while text and source links remain the complete explanation. Three.js would only be justified by a concrete spatial interaction that the simpler view cannot express.
Evaluate the proposed tool with tasks such as finding an unpromoted skill, locating a version mismatch and explaining an invocation-policy disagreement. Measure correctness and time only after real trials. The present review ships articles, static SVGs and bounded fixtures; it makes no claim that a provenance explorer, hosted compiler or live agent dashboard has been implemented.
Implementation steps
- 1
Build a read-only inventory from a fixed manifest and tree.
- 2
Expose invocation declarations with their source paths.
- 3
Add version comparisons that preserve unknown installed state.
- 4
Test reader tasks before adding richer interaction.
Copy-ready example
{
"proposal": "local skills provenance explorer",
"readOnly": true,
"views": ["distribution inventory", "invocation metadata", "version provenance"],
"interactiveExplorerShipped": false,
"installerExecution": false,
"threeJsRequired": false
}Frequently asked questions
Is this an official roadmap item?
No. It is an editorial project idea derived from the inspected repository’s structure.
Would Three.js make the first version better?
Not without a demonstrated need. Source tables and a two-dimensional graph are a clearer starting point for these relationships.
Sources
- .claude-plugin/plugin.jsonSource checked 2026-09-08
- scripts/link-skills.shSource checked 2026-09-08
- scripts/list-skills.shSource checked 2026-09-08
- scripts/sync-plugin-version.mjsSource checked 2026-09-08
- .agents/invocation.mdSource checked 2026-09-08