Skip to content
TrustedSkillsbeta
Back to all skills

Documentation Update

Checked
geoffjay·vlatest·writing·MIT

Automatically updates existing documentation with new information extracted from conversations or project changes.

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 geoffjay/claude-plugins --skill documentation-update -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

geoffjay

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 geoffjay/claude-plugins at 0ab5ae1b22.

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

Scanned
2 files, 919 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 allows you to update existing documentation with new information or revisions. It can incorporate changes from various sources, such as user feedback, updated specifications, or newly available data. The skill aims to maintain accurate and current documentation for a wide range of topics.

When to use it

  • You need to integrate recent product updates into the official documentation.
  • User feedback highlights inaccuracies in existing documentation that require correction.
  • A new feature requires detailed explanations added to the user guide.
  • Technical specifications have changed and need to be reflected in the API reference.

Key capabilities

  • Incorporates changes from provided sources.
  • Updates existing documentation content.
  • Maintains accuracy of technical information.

Example prompts

  • "Update the 'Getting Started' section of our user guide with details on the new authentication flow."
  • "Revise the API reference for endpoint /users to reflect the updated request parameters."
  • “Incorporate this feedback from a user: ‘The instructions for setting up email notifications are unclear.’”

Tips & gotchas

  • Ensure the AI agent has access to the existing documentation files or a link to an online repository. Providing clear context and specific areas needing updates will improve results.