lp-coverage-scan
Coverage gap scanner for startup loop. Reads a business coverage manifest, scans the repo and known integrations for actual artifact/data-source state, classifies gaps as CRITICAL/MAJOR/MINOR, writes a gap report, and emits dispatch packets to queue-state.json for all CRITICAL and MAJOR gaps.
npx skills add majiayu000/claude-skill-registry --skill lp-coverage-scan --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Coverage Scan Orchestrator `/lp-coverage-scan` is the scan and emission layer for startup loop coverage gap detection. This skill does four things: 1. Read coverage manifest from `docs/business-os/strategy/<BIZ>/coverage-manifest.yaml` 2. Scan repo and known integration paths for each domain entry via `modules/scan-phase.md` 3. Classify gaps as CRITICAL/MAJOR/MINOR and produce a human-readable gap report 4. Emit dispatch packets for CRITICAL/MAJOR gaps to queue-state.json via `modules/emit-phase.md` Keep this file thin. Do not embed scan rules, classification rubrics, or dispatch templates here. ## Invocation ``` /lp-coverage-scan --biz <BIZ> [--as-of-date <YYYY-MM-DD>] [--dry-run] ``` ### Parameters | Parameter | Required | Default | Notes | |---|---|---|---| | `--biz` | Required | — | Business identifier (e.g. `BRIK`, `PWRB`). Must match a directory under `docs/business-os/strategy/`. | | `--as-of-date` | Optional | Today (YYYY-MM-DD) | Date used for artifact naming and staleness calculation. | | `--dry-run` | Optional | — | When present: write gap report but skip all queue-state.json writes. Safe read-only mode for verifying scan behavior. | ## Global Invariants ### Operating
- Invocation
- Parameters
- Global Invariants
- Operating mode
- Allowed actions
- Prohibited actions
- Inputs
- Module Routing
- Preflight Gate
- Output Paths
- Dry-Run Mode
What does the lp-coverage-scan skill do?
Coverage gap scanner for startup loop. Reads a business coverage manifest, scans the repo and known integrations for actual artifact/data-source state, classifies gaps as CRITICAL/MAJOR/MINOR, writes a gap report, and emits dispatch packets to queue-state.json for all CRITICAL and MAJOR gaps.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill lp-coverage-scan --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.