agentsclimarketplace

Nightly docs sweep

Skill leek/agent-skills/skills/nightly-docs-sweep

Run a documentation sweep so repo docs match the current implementation.From its SKILL.md

Install
npx -y skills add leek/agent-skills --skill nightly-docs-sweep

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

  • 3 stars3 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.1 KB, as published. Nobody here has run it

Nightly Docs Sweep

Goal

Make repository documentation match the current implementation, then leave a reviewable change set or pull request.

Loop Prompt

Whenever a documentation pass is needed, review the codebase in full and make sure all documentation reflects the current implementation. Update stale documentation, verify the changes, then open a pull request.

Stop when documentation matches the current implementation and the docs changes are ready for review.

When To Use

Use this whenever implementation changes may have left READMEs, setup guides, API references, examples, architecture notes, comments, or runbooks behind.

Workflow

  1. Review implementation changes since the last documentation pass.
  2. Compare the repository's documentation with the code, configuration, commands, and behavior that currently ship.
  3. Update only stale or missing material. Do not rewrite accurate documentation just to create activity.
  4. Verify commands, links, examples, configuration names, API shapes, and setup steps against the current repository.
  5. Run the relevant checks available in the project, such as documentation tests, link checks, type checks, unit tests, or linting.
  6. Summarize the documentation drift found, the files changed, and the verification performed.
  7. If the user asked for a PR and the environment supports it, open a pull request with a clear title and body.

Report

End with:

  • Documentation areas checked.
  • Stale or missing docs found.
  • Files updated.
  • Verification commands run and their results.
  • Remaining gaps or blockers.
  • Pull request link, if one was opened.

Guardrails

  • Keep scope tied to real implementation behavior.
  • Preserve accurate documentation and user-authored wording where practical.
  • Do not invent behavior that is not backed by code, configuration, tests, or project docs.
  • If the repository is too large for a full sweep in one pass, prioritize changed or high-traffic docs first and clearly state the remaining scope.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most docs writing skills give

Counted across 1,951 of the 3,904 authors here whose files we hold, read 2026-09-06

  • Use third-person for skill descriptionsin 54 of 1951, across 35 files
  • Start descriptions with Use whenin 43 of 1951, across 29 files
  • Run baseline scenarios before writing any skillin 40 of 1951, across 26 files
  • Use active voicein 40 of 1951, across 36 files
  • Map file responsibilities before defining tasksin 36 of 1951, across 29 files
  • Use checkbox syntax for tracking stepsin 35 of 1951, across 27 files
  • Ask one question at a timein 35 of 1951
  • Offer execution options after saving the planin 33 of 1951, across 24 files
  • Include complete code in every stepin 33 of 1951, across 27 files
  • Design units with clear boundaries and interfacesin 31 of 1951, across 23 files
  • Announce the skill usage at the startin 30 of 1951
  • Verify agent compliance after adding the skillin 29 of 1951, across 17 files

Said here and by no other author read

  • Verify commands and links against current code
  • Prioritize high-traffic documentation if repository is large

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.

Keep looking

Skills are one crate of 611,884. 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.