agentleFS
zyphr-labszyphr-labs/bounty-harness/.claude/skills/coverage/SKILL.md

coverage

Skill1 starsChanged 3 months agoMITView on GitHub

This is a thin human-facing router. Use skill.yaml as the source of truth for exact commands, inputs, outputs, and workflow chaining.

33 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use scan, lint 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.
  • rajnavakotiSkill

    scan

    Run the AI dashboard scanner and generate the HTML report.

    Also in 4 projects that use this

  • 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

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 2 are distinctive, and 3 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.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Start with calculate for raw coverage percentages.

    line 16
  2. Very specific:

    Run find-gaps to identify highest-priority missing coverage.

    line 17
  3. Very specific:

    Run report for a full markdown dashboard.

    line 18
  4. Distinctive:

    If a workflow has no script reference, treat it as a manual or tool-native workflow.

    line 20
  5. Distinctive:

    No runtime evidence needed.

    line 30

“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

Overview

Tracks what the bug bounty toolkit covers and what is missing. The coverage ledger maps every standard testing item (WSTG, ASVS, API Top 10, Bugcrowd VRT) to existing skills, scripts, and workflows — then produces a measurable coverage report. No more vibes.

This is a thin human-facing router. Use skill.yaml as the source of truth for exact commands, inputs, outputs, and workflow chaining.

Quick Reference

  • Skill: coverage
  • Severity range: info
  • Required tools: python3
  • Expected input files: coverage_matrix.yaml
  • Scope check: not applicable — read-only coverage analysis.

Workflow Selection

  • Start with calculate for raw coverage percentages.
  • Run find-gaps to identify highest-priority missing coverage.
  • Run report for a full markdown dashboard.
  • Runbooks: use runbooks/.
  • If a workflow has no script reference, treat it as a manual or tool-native workflow.

Available Workflows

WorkflowPurposeScript pathsPrimary outputsEvidence
calculateCompute coverage percentages from matrix..claude/skills/coverage/scripts/coverage_calculator.py$OUTDIR/coverage/stats.json$OUTDIR/coverage/evidence/
find-gapsIdentify highest-priority missing coverage..claude/skills/coverage/scripts/gap_finder.py$OUTDIR/coverage/gaps.json$OUTDIR/coverage/evidence/
reportGenerate full markdown coverage dashboard..claude/skills/coverage/scripts/coverage_report.py$OUTDIR/coverage/coverage_report.md$OUTDIR/coverage/evidence/

Evidence Required

  • No runtime evidence needed. Coverage reports are self-contained artifacts.
  • Timestamps are embedded in generated files via ISO 8601 UTC.
  • Matrix includes last_updated date for provenance tracking.

References

  • Source of truth: skill.yaml
  • Runbooks: runbooks/
  • OWASP WSTG v5.0 — Web Security Testing Guide
  • OWASP ASVS v5.0 — Application Security Verification Standard
  • OWASP API Security Top 10 (2023)
  • Bugcrowd Vulnerability Rating Taxonomy (VRT)
  • .claude/skills/*/skill.yaml — actual implemented workflows

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.