Skip to content
TrustedSkillsbeta
Back to all skills

Docs Check

Checked
lukasstrickler·vlatest·writing·MIT

Docs Check verifies documentation for accuracy and consistency, ensuring high-quality content and reducing errors.

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 lukasstrickler/ai-dev-atelier --skill docs-check -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

lukasstrickler

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 lukasstrickler/ai-dev-atelier at 251d639e18.

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

Commit
251d639e18
Manifest
content/skills/docs-check/SKILL.md
Scanned
3 files, 838 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 lukasstrickler-docs-check skill provides a way to verify documentation against specific criteria. It can check if all required sections are present, ensuring completeness and consistency across documents. This helps maintain high quality and accuracy in technical writing and knowledge bases.

When to use it

  • Technical Writing Review: Use this skill when reviewing newly written or updated documentation to ensure it meets established standards.
  • Knowledge Base Maintenance: Regularly check your internal knowledge base for completeness and adherence to formatting guidelines.
  • Onboarding Documentation: Validate onboarding materials to guarantee new team members receive all necessary information.
  • API Reference Generation: Verify that API reference documents include all required parameters, descriptions, and examples.

Key capabilities

  • Documentation verification
  • Section presence checks
  • Consistency enforcement

Example prompts

  • "Check the documentation for our 'User Authentication' feature."
  • "Verify that the 'Installation Guide' includes a troubleshooting section."
  • "Ensure all API endpoints in the reference document have descriptions."

Tips & gotchas

The skill requires clear definitions of expected sections and criteria to be effective. Providing detailed instructions or templates will improve accuracy and results.