deliverable-lintlisted

Reviews a whole deliverable, such as a talk, course module, paper, chapter, or referee report, against its manifest without rewriting. Runs a deterministic gate for build, citations, numbers, facts, and leaks, then stops on failure. It assigns a cheap finder to each section, runs a strong-model whole-work pass, and adjudicates into checks/<date>/findings.json and report.md with anchors, severities, and honest NOT-CHECKED coverage within a dollar budget. Use when the user says "lint the deliverable", "review the whole talk/module/paper", "night shift", "pre-ship review", or before release. Revision remains serial and author-led.
scdenney/open-science-skills · ★ 57 · AI & Automation · score 77

Install: claude install-skill scdenney/open-science-skills

# Deliverable lint Detection is parallel; revision is serial. This skill finds; it never edits a source file, never edits the wiki, and never runs a rewrite. The author (or `sci-edit`, one section at a time under its guard) does the revising afterwards. ## Stage 0 and 1: prepare the run (shared script) - **Resolve the toolchain once, before any path below.** `$DTOOL` is the deliverable toolchain, which now ships with this library at `plugin/tools/deliverable`. Take the first that exists: `$DELIVERABLE_TOOLS`, `${CLAUDE_PLUGIN_ROOT}/tools/deliverable` (Claude Code sets that variable for a plugin skill), the `plugin/tools/deliverable` directory of an `open-science-skills` checkout, then a legacy `project_hygiene/scripts` checkout for installations that predate the move. Scripts are at `$DTOOL/scripts/` and kind profiles at `$DTOOL/kinds/`, and the two must stay siblings because `lint_prepare.py` resolves profiles relative to its own directory. If none exists, stop, name the paths you tried, and never continue with a degraded run. - The nearest `deliverable.yml` upward from cwd. Refuse to run without one; point at `deliverable-open`. - `python3 $DTOOL/scripts/lint_prepare.py --root <dir> --budget <usd> --mode manual|headless [--sections a,b] [--skip-fast]` where `$DTOOL` resolves as above. It reserves `checks/YYYY-MM-DD[-N]/` (never reuses a directory), runs the fast gate into `<run>/fast.json` (`--build` unless headless; `--skip-fast` records a skipped gate, which can never