Skip to content
Diagnosis · Automation

update-project-docs

MANDATORY for every coding agent (Claude Code, Codex, or any other) — keep this repository's documentation in sync after any change to…

Connecting the steps of a workflow

Works with
ClaudeChatGPTGeminiClaude CodeCodexCursorCopilotGemini CLI
Setup
One command
Best in a coding tool, where its scripts can run.
Contains
Instructions + 2 scripts
Shell.
Maintained
Last change 4 Oct 2026
On the repository’s main branch.

What it does

This repository keeps an unusually large, multi-surface, multi-language doc set. Docs drift silently because a change often belongs in 6–10 files across 4 languages plus two HTML pages. This skill encodes which docs exist, which change-types touch which docs, and how to propagate consistently (including the wiki i18n + cache-bump dance).

What it can touch

  • Includes 2 scripts

    Your AI can run these when the skill is used — on your computer in a coding tool (which asks first unless you have told it not to), or in the AI’s own sandbox in Claude and ChatGPT.

    How we know

    Found in the skill’s folder: scripts/doc-coverage.sh, scripts/wiki-block-lengths.sh.

  • No known risk pattern found

    Launch7’s automated check read all 4 text files in this skill and matched none of its risk patterns. This is not a guarantee: a check like this can miss new or disguised tricks, and the author can change the files after the check.

    How we know

    Read 2026-10-05, commit dc58196 by pipeline/trust/analyze.py — 40+ patterns for hidden text, prompt injection, downloads that run, credential access and more. It reads; it never runs the skill.

  • Recently maintained

    Its repository has had changes recently.

    How we know

    Last push to hoangsonww/Claude-Code-Agent-Monitor: 2026-10-04 (1 days before the scan).

Read automatically from the skill’s own files on GitHub on 5 Oct 2026. Launch7 does not run or manually review skills: this lists what the check saw, and nothing here means “safe”. How we check

Add it to your AI

Partly. Upload it in Claude’s settings — the instructions work; the scripts need the full folder.

  1. Built in your browser from the SKILL.md on GitHub — nothing passes through Launch7.

  2. In Claude, open Customize → Skills, press +, then Create skill → Upload a skill, and choose the .zip.

  3. Make sure code execution is switched on (Settings → Capabilities). Skills need it.

  4. Start a new chat and ask for the job in your own words — Claude picks the skill up when it fits.

This skill ships 2 scripts beside its instructions. The download here is the SKILL.md alone — enough for the instructions, not for the parts that run code. Use the command route, or take the full folder from the repository.

How Claude does this: support.claude.com · checked 28 Sep 2026 · “Supported” means documented by the vendor; Launch7 has not run it end to end

More from hoangsonww

All from this publisher →
  • benchmark

    Benchmark one session (or a small recent set) against the rolling average using Agent Monitor data — cost, total tokens, tool count, and workflow…

    hoangsonwwInstructions only
  • budget-set

    Define a spend budget for Claude Code and, optionally, create a cost alert rule that fires when usage crosses the limit, via POST /api/alerts/rules on the…

    hoangsonwwIts code sends data over the internet
  • cache-efficiency

    Analyze prompt-cache effectiveness for Claude Code usage from the Agent Monitor dashboard — cache hit rate (total_cache_read /…

    hoangsonwwInstructions only
  • config-audit

    Run a full audit of the user's Claude Code configuration via the Agent Monitor Config Explorer API: counts per surface (user vs project), duplicate or…

    hoangsonwwInstructions only
  • cost-alert

    Review the configured cost alert rules and the alerts currently fired on the Agent Monitor dashboard, then explain exactly what tripped and why.

    hoangsonwwInstructions only