Skip to content
TrustedSkillsbeta
Back to all skills

Update Docs

Checked
peteonrails·vlatest·writing·MIT

This skill automatically updates documentation files based on changes in your project, ensuring accurate and current guides.

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 peteonrails/voxtype --skill update-docs -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

peteonrails

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 peteonrails/voxtype at 6d2fc6ddbf.

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

Commit
6d2fc6ddbf
Manifest
.claude/skills/update-docs/SKILL.md
Scanned
1 file, 187 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

This skill, update-docs, likely automates updates to documentation based on changes in code or other sources. The specific functionality isn't detailed but implies the ability to modify and maintain documentation files automatically. It’s authored by peteonrails and part of the voxtype project.

When to use it

  • When you have a codebase with extensive documentation that needs frequent updates alongside code changes.
  • To automate the process of synchronizing API documentation with evolving APIs.
  • For maintaining user guides or tutorials that depend on specific software versions.
  • To reduce manual effort and potential errors in updating technical documentation.

Key capabilities

  • Automated documentation updates
  • Integration with code repositories (implied)
  • Part of the voxtype project

Example prompts

  • "Update the API documentation based on the latest commit."
  • "Synchronize the user guide with version 2.5 of the software."
  • “Generate updated release notes from the changelog.”

Tips & gotchas

The skill’s specific configuration and dependencies are not detailed in the source, so ensure you understand its requirements before use. It likely requires access to your code repository and documentation files.