coverage
Skill0 starsChanged 2 months agoApache-2.0View on GitHub
Show scan coverage across all scanners — what's been analyzed, what remains, what changed since last scan.
33 other projects use a version of this.
Adopted by
Most recently taken up by
- LeanMeanCleanApps/CleanLambdaFunctiontheir own version, first seen Nov 15, 2026
- oberemokis/skillstheir own version, first seen Nov 15, 2026
- LeanMeanCleanApps/CleanWebApitheir own version, first seen Nov 15, 2026
- LeanMeanCleanApps/CleanGraphQLApitheir own version, first seen Nov 15, 2026
- LeanMeanCleanApps/CleanMinimalApitheir own version, first seen Nov 15, 2026
- wboayue/rust-ibapitheir own version, first seen Nov 9, 2026
Used with
Projects with it also use lint, profile and 9 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.
Microsoft AzureSkilllint
Run all linting and spell checking for TypeScript and Rust code. Run this before committing to catch style issues, clippy warnings, and misspellings.
Also in 4 projects that use this
julienamorganSkillprofile
Researches the user's market, competitors, and competitive positioning to build a complete ICP profile. Shows findings for user approval before proceeding. Triggers: /profile, "research my market", "who are my competitors". Reads: ./gtm/company.md, ./gtm/icp.md. Writes: updates ./gtm/icp.md with competitive positioning. Standalone: yes (asks for domain if company.md missing).
Also in 3 projects that use this
asterkinSkilladr
Create Architecture Decision Records (ADRs) following project standards. Guides template usage, process, and best practices for documenting architecturally significant decisions.
Also in 4 projects that use this
anombyte93Skilldiscover
Phase 1 of the prd-taskmaster pipeline: brainstorm-driven discovery. Delegates to superpowers:brainstorming in Interactive Mode (one adaptive question at a time), or self-brainstorms in Autonomous Mode when no user is present. Intercepts before the brainstorming chain hands off to writing-plans — this skill owns the exit. Extracts constraints, calibrates scale (Solo / Team / Enterprise), and advances the pipeline to GENERATE.
Also in 3 projects that use this
MicrosoftSkillworktree
Create, reuse or clean up a dedicated git worktree for working on a pull request or a private branch. Use from any PR-scoped workflow that needs an isolated checkout to keep current code and build output untouched.
Also in 3 projects that use this
SentrySkille2e
Run E2E tests for Sentry JavaScript SDK test applications
Also in 3 projects that use this
Other versions33 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 33
- FalkorDB/FalkorDB★ 11ksame name
- pydantic/monty★ 8.9ksame name
- LiberatedPixelCup/Universal-LPC-Spritesheet-Character-Generator★ 1.9ksame name
- firedancer-io/firedancer★ 1.6ksame name
- hegeldev/hegel-rust★ 400same name
- LeanMeanCleanApps/CleanMinimalApi★ 400same name
- wboayue/rust-ibapi★ 400same name
- nockawa/Typhon★ 253same name
- Amplicode/spring-skills★ 126same name
- AsiaOstrich/universal-dev-standards★ 84same name
23 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 repository27 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- alignSkill
- code-walkSkill
- conceptsSkill
- contributeSkill
- doc-gap-checkSkill
- enrichSkill
- enumerateSkill
- find-implicit-adrsSkill
- implementSkill
- ingest-docsSkill
- log-issueSkill
- navigateSkill
- next-batchSkill
- orientSkill
- panelSkill
- probe-defineSkill
- probe-runSkill
- probeSkill
- reflect-featureSkill
- retrieveSkill
- reviewSkill
- scanSkill
- statusSkill
- streamsSkill
- test-coverageSkill
- triageSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 29 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 44
Read manifest for $ARGUMENTS
- Distinctive: line 49
Check if target repo has new commits since last enumeration:
- Distinctive: line 51
If yes, recommend re-enumeration
- Very specific: line 64
If no manifests exist at all, explain the system and suggest starting with /enumerate
“Common” is measured: kept by at least 6 in 10 of the 29 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
Coverage Report
Show scan coverage status. If $ARGUMENTS is provided, show details for that specific scanner. Otherwise show summary across all scanners.
Protocol
Summary Mode (no arguments)
- List all manifests in
state/coverage/ - For each, read and extract: scanner_id, total_items, scanned_items, coverage_pct, last_enumerated
- List scanners that have NO manifest yet (from
scanners/directory) - Display:
## Scan Coverage
| Scanner | Coverage | Scanned | Total | Last Active | Stale? |
|---------|----------|---------|-------|-------------|--------|
| tests/collectors-adapters | 23% | 10 | 43 | 2026-04-20 | No |
| tests/collectors-sdk | 100% | 8 | 8 | 2026-04-19 | No |
| docs/accuracy/feature-behavior | 0% | 0 | 25 | - | - |
| ... | | | | | |
Not yet enumerated:
- scanners/docs/accuracy/architecture-drift.md
- scanners/docs/completeness/missing-limitations.md
- ...
Overall: X/Y items scanned across all scanners (Z%)- Flag "stale" if last_enumerated is >7 days ago (repo may have new files)
- Recommend next action: enumerate un-manifested scanners, or continue scanning lowest-coverage ones
Detail Mode (scanner path provided)
- Read manifest for
$ARGUMENTS - Display:
- Full item list grouped by status (scanned, not-scanned, changed-since-scan, new, error)
- Dates and commit refs for scanned items
- Suggested next batch (first 10-15 not-scanned items)
- Check if target repo has new commits since last enumeration:
git log --oneline {repo_commit_at_enumeration}..HEAD -- {scope paths}- If yes, recommend re-enumeration
Staleness Detection
A manifest is stale when:
last_enumeratedis >7 days ago AND target repo has new commits since- Items marked
scannedhave files that changed (detected via git log)
Report: "N items may need re-scanning. Run /enumerate $ARGUMENTS to refresh."
Rules
- This is read-only — never modify manifests, only report
- If no manifests exist at all, explain the system and suggest starting with
/enumerate - Show actionable next steps, not just numbers
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.

