agentsclimarketplace

Night watch

Skill runsagents/night-watch

Run a read-only repository maintenance sweep that files structured findings and never fixes them. Trigger on "night watch", "maintenance sweep", or scheduled/unattended repo checks.From its SKILL.md

Install
npx -y skills add runsagents/night-watch

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 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.

SKILL.md

2.5 KB, 523 tokens by cl100k_base, as published. Nobody here has run it

Night Watch

Run repository maintenance checks without changing the repository under inspection.

Non-negotiable boundary

This is a read-only inspection. The only writes permitted are new Markdown finding files beneath findings/. Do not edit, format, regenerate, delete, rename, commit, stage, install, upgrade, or fix any other file. Do not open a pull request or issue. Do not execute commands that mutate repository state, dependencies, services, or external systems.

File, don't fix: fixing without the human is how you wake up to confident nonsense.

If the environment cannot guarantee this boundary, stop and report that the sweep did not run.

Procedure

  1. Record the inspected repository path and immutable revision (prefer git rev-parse HEAD). Use read-only commands only.

  2. Ensure findings/ exists. Creating that directory is permitted. Never overwrite an existing finding; choose the next unused NW-YYYY-NNN identifier.

  3. Resolve this SKILL.md's installation directory as <night-watch-skill>. Read <night-watch-skill>/templates/finding.md and <night-watch-skill>/schemas/finding.schema.json before inspecting.

  4. Run every instruction in <night-watch-skill>/checks/, in filename order:

    • citations.md
    • dead-branches.md
    • docs-vs-code.md
    • invariants.md
  5. For each item that meets a check's finding threshold, create one evidence packet at findings/<id>-<short-slug>.md. Copy the template structure. Set synthetic: false. Report observations, not a proposed patch.

  6. Do not file duplicates. If two checks expose the same underlying discrepancy, create one packet and name both checks in its evidence.

  7. Validate all newly created packets:

    node <night-watch-skill>/scripts/validate-finding.mjs findings
    

    If a packet fails validation, edit only that new packet until it passes. If the validator itself fails, stop; do not modify the validator during an unattended run.

  8. Stop. Make no fixes and no other repository changes.

Final response

State the inspected revision, the checks completed, and the validation result. Summarize the number of valid findings by severity in this exact order: critical, high, medium, low. Include zeroes. If there were no findings, say so explicitly. End with: Inspection complete. No fixes attempted.

What ships with it: 16 files

35.8 KB alongside SKILL.md, 2 of them executable

schemas/

scripts/

templates/

tests/

Keep looking

Skills are one crate of 326,144. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.