Upkeep audit
Run the Upkeep repo audit locally against any repository path. Use when asked to audit a repo, check docs/spec/asset drift, or run upkeep without GitHub Actions.From its SKILL.md
npx -y skills add wei18/Upkeep --skill upkeep-auditAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 12 stars12 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
- runs commandsInstructs the agent to run 4 commands, including `git clone --depth 1 https://github.com/wei18/upkeep ~/.cache/upkeep` and 3 more.
SKILL.md
2.1 KB, 478 tokens by cl100k_base, as published. Nobody here has run it
Upkeep Local Audit
Run the full Upkeep audit pipeline (discovery → parallel reviewers → synthesis → HTML report) against a local repository. Output-only: the target repo is never modified.
Steps
- Ensure the Upkeep checkout at
~/.cache/upkeep:- Missing:
git clone --depth 1 https://github.com/wei18/upkeep ~/.cache/upkeep - Present:
git -C ~/.cache/upkeep pull --ff-only(if the pull fails — diverged or dirty checkout — delete~/.cache/upkeepand re-clone; it is disposable) - Then
(cd ~/.cache/upkeep && npm ci)after a fresh clone or whenever the pull changedpackage-lock.json(when unsure, run it — it is idempotent).
- Missing:
- Run the audit (takes several minutes; reviewers run as parallel
claude -psubprocesses — run it in the background and report progress):
Pass flags only when the user asked for them, with one exception: the report defaults to~/.cache/upkeep/scripts/local-audit.sh <target-path> [--model M] [--rubric-lang L] [--max-turns N] [--out FILE]./upkeep-report.htmlin the current working directory, so if the working directory is inside the target repo, pass--outpointing outside it (e.g.~/upkeep-report.html) — the audit must never write into the target repo. Other defaults match the CI inputs (claude-opus-4-8, rubricen,30turns);--rubric-langacceptsenorzh-TW. - Summarize: the script prints the report markdown at the end. Present the findings grouped by severity (high → medium → low), each with its file path and a one-line problem statement, then give the absolute path of the generated report file (
upkeep-report.htmlby default, or the--outpath). If any reviewers failed, name them.
Requirements (tell the user what is missing instead of failing silently)
claudeCLI installed and logged in (Claude Pro/Max subscription).- Node 20+, git.
What ships with it: 1 file
323 B alongside SKILL.md
.claude-plugin/
- plugin.json323 B
Gives 0 of the 12 instructions most audit compliance skills give in 478 tokens
Counted across 960 of the 1,589 authors here whose files we hold, read 2026-09-06
- Read product marketing context before asking questionsin 29 of 960, across 11 files
- Rank findings by severityin 29 of 960, across 22 files
- Generate audit reportin 22 of 960
- Run the audit scriptin 20 of 960, across 19 files
- Generate a prioritized action plan reportin 19 of 960, across 11 files
- Ensure one H1 per pagein 15 of 960, across 5 files
- Ensure sitemap exists and is accessiblein 14 of 960, across 4 files
- Verify alt text on all imagesin 12 of 960, across 3 files
- Determine the audit scope before startingin 12 of 960, across 4 files
- Verify important pages allowed in robots.txtin 11 of 960, across 2 files
- Detect business type from homepage signalsin 11 of 960, across 7 files
- Delegate specialized tasks to subagentsin 11 of 960, across 7 files
Said here and by no other author read
- Ensure the Upkeep checkout at ~/.cache/upkeep
- Run the audit script against a local repository
- Give the absolute path of the generated report file
- Name any reviewers that failed
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.