Update Docs

Name: Update Docs
Author: anyproto

Checked

anyproto·vlatest·writing

This skill automatically updates documentation files (like Markdown) based on changes in your project, ensuring accurate and current records.

Repository

Install on your platform

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

Run this in your project

terminal

$ npx skills add anyproto/anytype-ts --skill update-docs -a claude-code

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

anyproto

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 11 Oct 2026

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 anyproto/anytype-ts at d965ea28b4.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit: d965ea28b4
Manifest: .claude/skills/update-docs/SKILL.md
Scanned: 1 file, 115 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, anyproto-update-docs, provides functionality to update documentation. It's designed to streamline the process of keeping documentation current and accurate. The specific capabilities are not detailed in the provided source.

When to use it

When you need to automatically refresh outdated documentation based on code changes.
To ensure that internal knowledge bases reflect the latest product features.
For maintaining API documentation alongside evolving APIs.
As part of a continuous integration/continuous delivery (CI/CD) pipeline for automated documentation updates.

Key capabilities

Documentation updating
Integration with anyproto/anytype-ts

Example prompts

"Update the documentation for the 'user authentication' module."
"Refresh the API reference guide based on recent code commits."
"Generate updated release notes from commit messages."

Tips & gotchas

The skill requires familiarity with anyproto/anytype-ts. Specific configuration and integration steps will depend on your documentation system and workflow.