agentleFS
opendatadiscoveryopendatadiscovery/odd-team/.claude/skills/coverage/SKILL.md

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

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 AzureSkill

    lint

    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

  • julienamorganSkill

    profile

    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

  • asterkinSkill

    adr

    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

  • anombyte93Skill

    discover

    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

  • MicrosoftSkill

    worktree

    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

  • SentrySkill

    e2e

    Run E2E tests for Sentry JavaScript SDK test applications

    Also in 3 projects that use this

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
  1. Very specific:

    Read manifest for $ARGUMENTS

    line 44
  2. Distinctive:

    Check if target repo has new commits since last enumeration:

    line 49
  3. Distinctive:

    If yes, recommend re-enumeration

    line 51
  4. Very specific:

    If no manifests exist at all, explain the system and suggest starting with /enumerate

    line 64

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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)

  1. List all manifests in state/coverage/
  2. For each, read and extract: scanner_id, total_items, scanned_items, coverage_pct, last_enumerated
  3. List scanners that have NO manifest yet (from scanners/ directory)
  4. 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%)
  1. Flag "stale" if last_enumerated is >7 days ago (repo may have new files)
  2. Recommend next action: enumerate un-manifested scanners, or continue scanning lowest-coverage ones

Detail Mode (scanner path provided)

  1. Read manifest for $ARGUMENTS
  2. 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)
  3. 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_enumerated is >7 days ago AND target repo has new commits since
  • Items marked scanned have 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

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.