update-docs is agent-read markdown (skill) from arthur-ai/arthur-engine.
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
## Changes to review
Read the git diff from the file path provided as the first argument: $0
## Target docs
- docs/getting-started.md — Arthur init, session/user/attributes helpers, instrumentation
- docs/prompt-management.md — get_prompt, render_prompt, span attributes
## Update rules
- Changes to arthur.py (session/user/attributes, instrument_* methods) → getting-started.md
- Changes to _client.py or arthur.py prompt methods → prompt-management.md
- Pure refactors with no behaviour change → skip both
- Changes to telemetry.py → getting-started.md (init/shutdown section)
## When to create a NEW doc file (Write tool)
Only create a new file in docs/ when ALL of these are true:
1. The change introduces a major new user-facing feature (not a refinement of existing behaviour).
2. The content does not fit naturally into either existing guide.
3. The new file would be at least 200 words of meaningful content.
Otherwise, edit the most relevant existing file.
## Instructions
1. Read the diff file at path $0.
2. Decide which docs (if any) need updating using the rules above.
3. Read the affected doc file(s).
…
Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
GET https://markdownregistry.com/api/v1/artifacts/art_redi3hfyxnydp6bp
GET https://markdownregistry.com/api/v1/resolve?ref=arthur-ai/arthur-engine/update-docs
GET https://markdownregistry.com/api/v1/blob/fa5de7c08dc6d46e3ff5d95709a6259a3b3047546decd367888d8362fe74638a
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
arthur-ai/arthur-engine · .claude/skills/setup-genai-dev/SKILL.md · Set up the GenAI Engine development environment. Use when starting work on the project for the first time, or when…
arthur-ai/arthur-engine · .claude/skills/start-genai-backend/SKILL.md · Start the GenAI Engine backend server and frontend UI. Use when you need to launch the API server and the frontend…
arthur-ai/arthur-engine · .claude/skills/start-genai-frontend/SKILL.md · Start the GenAI Engine frontend UI dev server. Use when you need to launch the React app locally.
arthur-ai/arthur-engine · arthur-observability-sdk/.claude/skills/generate-client/SKILL.md · Regenerate the arthur_genai_client package from the GenAI Engine OpenAPI spec. Use when the GenAI Engine API has…
arthur-ai/arthur-engine · arthur-observability-sdk/.claude/skills/test-integration/SKILL.md · Run the arthur-observability-sdk integration tests. These build the SDK wheel into a fresh venv and verify OTLP…
arthur-ai/arthur-engine · arthur-observability-sdk/.claude/skills/test-unit/SKILL.md · Run the arthur-observability-sdk unit tests. Use when you want to verify SDK logic without building a wheel or spinning…
benkapner/claude-code-basecamp · skills/update-docs/SKILL.md · Use when implementing features, fixing bugs, or refactoring code that may invalidate existing docs. Detects stale…
lukaskellerstein/claude-my-marketplace · plugins/dev-tools-plugin/skills/update-docs/SKILL.md · Create or update project documentation. If no docs/ folder exists, creates comprehensive documentation from scratch…
