Skip to content
TrustedSkillsbeta
Back to all skills

Docs Audit

Checked
outfitter-dev·vlatest·writing·MIT

Scans documents for compliance, outdated information, and inconsistencies against specified guidelines.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add outfitter-dev/agents --skill docs-audit -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

outfitter-dev

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned outfitter-dev/agents at d37fffdd50.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
d37fffdd50
Manifest
plugins/outfitter/skills/docs-audit/SKILL.md
Scanned
5 files, 1,373 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The docs-audit skill allows AI agents to review and assess documentation for accuracy, completeness, and clarity. It can identify missing sections, outdated information, and areas where the writing could be improved. This ensures that technical documentation remains reliable and helpful for users.

When to use it

  • Before a major product release: To ensure all relevant documentation is up-to-date and accurate.
  • After significant code changes: To verify that documentation reflects the current state of the software.
  • When onboarding new technical writers: As a tool for evaluating their work and providing feedback.
  • For ongoing maintenance of knowledge bases: To proactively identify and fix issues in existing documentation.

Key capabilities

  • Documentation review
  • Accuracy assessment
  • Completeness checks
  • Clarity evaluation

Example prompts

  • "Review the 'Getting Started' guide for our new API and flag any inaccuracies."
  • "Assess this document for completeness, ensuring all features are described."
  • "Can you evaluate this section of documentation for clarity and suggest improvements?"

Tips & gotchas

The quality of the audit depends heavily on the quality of the source documentation. Providing clear instructions and context will help the agent produce more useful results.