skill-stocktake
Skill0 starsChanged 2 months agoMITView on GitHub
Audit and maintain quality, hygiene, and boundary integrity across OpenCodeBestFriend skills. Checks frontmatter schema, trigger keywords, exclusivity fences, path references, and test coverage. Use when reviewing installed or warehouse skills, auditing catalog health, or cleaning up skill bloat. Not for code-level security audits (full-audit-keamanan), code style review (matt-code-review), or prompt text optimization (prompt-optimizer).
27 other projects use a version of this.
Adopted by
Most recently taken up by
- Rojios/everything-claude-codetheir own version, first seen Nov 8, 2026
- shimo4228/akc-cycletheir own version, first seen Nov 8, 2026
- shimo4228/skill-stocktaketheir own version, first seen Nov 7, 2026
- pankaj-mahaur/Agent-Daemontheir own version, first seen Nov 6, 2026
- TsinHzl/claude-code-configtheir own version, first seen Nov 1, 2026
- renepf/claude-skillstheir own version, first seen Oct 25, 2026
Used with
Projects with it also use configure-ecc, foundation-models-on-device and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
royaluniondesign-sysSkillconfigure-ecc
Interactive installer for Everything Claude Code — guides users through selecting and installing skills and rules to user-level or project-level directories, verifies paths, and optionally optimizes installed files.
Also in 4 projects that use this
- royaluniondesign-sysSkill
foundation-models-on-device
Apple FoundationModels framework for on-device LLM — text generation, guided generation with @Generable, tool calling, and snapshot streaming in iOS 26+.
Also in 4 projects that use this
HABUBUSSSkillproject-guidelines-example
Also in 4 projects that use this
loulanyueSkillrules-distill
Scan skills to extract cross-cutting principles and distill them into rules — append, revise, or create new rule files
Also in 4 projects that use this
- loulanyueSkill
skill-comply
Visualize whether skills, rules, and agent definitions are actually followed — auto-generates scenarios at 3 prompt strictness levels, runs agents, classifies behavioral sequences, and reports compliance rates with full tool call timelines
Also in 3 projects that use this
InfopibeSkillarticle-writing
Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.
Also in 6 projects that use this
- +5 more from royaluniondesign-sys
Other versions27 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 27
- zereight/gitlab-mcp★ 2.1ksame name
- loulanyue/awesome-claude-notes★ 272same name
- Fmarzochi/EGC★ 61same name
- frankxai/agentic-creator-os★ 10same name
- FaisalAlqarni/sp-ecc★ 9same name
- gongyijie85/dsh-ecc★ 8same name
- shimo4228/claude-harness★ 4same name
- shimo4228/skill-stocktake★ 3same name
- shimo4228/akc-cycle★ 2same name
- TsinHzl/claude-code-config★ 2same name
17 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository47 other files it gives its agents.
- templates/AGENTS.mdAGENTS.md
- academicSkill
- adhdSkill
- agent-architecture-auditSkill
- api-designSkill
- automation-audit-opsSkill
- browser-actSkill
- chrome-devtools-axiSkill
- click-path-auditSkill
- codebase-designSkill
- code-tourSkill
- contract-firstSkill
- cost-aware-llm-pipelineSkill
- diagnosing-bugsSkill
- diagram-designSkill
- domain-modelingSkill
- emil-design-engSkill
- eval-harnessSkill
- found-this-designSkill
- full-audit-keamananSkill
- full-performance-auditSkill
- gh-axiSkill
- grill-with-docsSkill
- humanizerSkill
- hyperframesSkill
- id-demo-videoSkill
- img2threejsSkill
- impeccableSkill
- install-anti-slopSkill
- markitdownSkill
- matt-code-reviewSkill
- mongodb-opsSkill
- playwright-qaSkill
- prompt-optimizerSkill
- prototypeSkill
- researchSkill
- scroll-craftSkill
- scroll-worldSkill
- smartbook-ingestSkill
- smartdocSkill
- supabase-opsSkill
- tddSkill
- to-specSkill
- to-ticketsSkill
- vercel-opsSkill
- visual-studioSkill
- writing-for-agentsSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 25 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 29
Every audited skill or command resolves to exactly one verdict.
- Distinctive: line 44
If this file disappeared, would the user lose a job that no other skill, rule, core MCP, or cheap on-demand generation already covers?
- Distinctive: line 60
Verify model-invoked skills do not shadow manual slash commands.
- Distinctive: line 82
Never auto-delete a file, never auto-edit another skill's body, and never mutate a catalog from a learning log.
“Common” is measured: kept by at least 6 in 10 of the 25 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Skill Stocktake
Quality audit and catalog hygiene specialist for OpenCodeBestFriend skills and commands.
This skill inspects installed skills (~/.config/opencode/skills/), manual commands (~/.config/opencode/commands/), and repository sources (skills/, manual-skills/) to maintain tight trigger discipline, clean boundaries, and zero catalog bloat.
Boundaries & Handoffs
| Need | Route |
| Reviewing application source code quality or standards | matt-code-review |
| Auditing code security, secrets, permissions, or supply chain | full-audit-keamanan |
| Authoring or rewriting SKILL.md bodies and descriptions | writing-for-agents |
| Optimizing prompt wording and instructional clarity | prompt-optimizer |
| Measuring whether a skill actually beats no-skill | eval-harness |
| Auditing skill catalog hygiene, boundaries, and schema conformance | skill-stocktake |
This skill audits and reports. It does not rewrite another skill's body, and it does not delete files.
Verdict Protocol
Every audited skill or command resolves to exactly one verdict. No item is left unjudged, and no item carries two verdicts.
| Verdict | Meaning |
KEEP | Unique trigger, current artifacts, defensible cost asymmetry, existence pass clears |
COMPRESS | Still needed, but the body is longer than the judgment it carries. Scripts and verification gates survive; prose shrinks |
UPDATE | Artifacts, versions, paths, or flags are stale. Requires cited evidence |
MERGE → <target> | Overlaps a sibling. Name the single target and the residue that moves |
RETIRE | Existence pass fails, or the no-skill baseline matches the with-skill run, or the trigger was always covered by runtime, rules, Context7, or the model itself |
Audit Methodology
Consult references/checklist.md for the full inspection protocol.
- Existence pass (ask explicitly, per item):
- If this file disappeared, would the user lose a job that no other skill, rule, core MCP, or cheap on-demand generation already covers?
- Does an independent trigger plus reusable judgment justify the selection cost, drift risk, and maintenance burden?
- A skill that only restates what a current model does unprompted fails this pass.
- Currency pass:
- Paths resolve under
~/.config/opencode/..., not foreign agent-host directories. - Flag references to foreign platforms and stale CLI flags, versions, or pinned artifacts.
- Preserve greppable terms, self-enforcing prohibitions, and numeric thresholds verbatim. Do not abstract them into softer prose.
- Paths resolve under
- Frontmatter schema validation:
- Mandatory keys:
name,description,compatibility: opencode,license. namematches the directory name.- Description carries unambiguous positive triggers and explicit negative boundaries ("Use when... Not for...").
- Mandatory keys:
- Trigger and routing discipline:
- Detect overlapping or competing trigger phrases across skills.
- Verify model-invoked skills do not shadow manual slash commands.
- Confirm each high-traffic intent has one owner.
- Provenance and policy parity:
- Non-first-party skills carry a compliant
NOTICE.mdunder MIT or Apache-2.0. Unknown license is not a grant. - Name is registered in
vendor/skill-policy.jsonand listed alphabetically invendor/skill-allowlist.txt. tests/test_skills.pyassertions match the measured tree, not a remembered count.
- Non-first-party skills carry a compliant
Evidence Requirement
UPDATE, MERGE, and RETIRE are not opinions. Cite at least one of: a path listing, a --help or version probe, a checksum, an upstream doc reference, or a no-skill baseline from eval-harness. An unproven claim downgrades to KEEP with a follow-up note.
Output
Report a single table, one row per audited item, plus a short list of follow-ups.
| Skill | Verdict | Evidence | Handoff |Handoffs: COMPRESS and UPDATE go to writing-for-agents (structure, description, pointers) or prompt-optimizer (instruction phrasing). Security findings go to full-audit-keamanan. Application code style goes to matt-code-review. Utility measurement goes to eval-harness.
Never auto-delete a file, never auto-edit another skill's body, and never mutate a catalog from a learning log.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.