# Update Docs

> Use when project knowledge, a design decision, a runbook, or human-facing documentation should be made durable. Triggers on "update docs", "更新文档", "写 README", "记下来", "归档", "save this", "update knowhow".

- Skill: `freemty/update-docs` (Agent Skill)
- Install (CLI): `npx skillmds@latest add freemty/update-docs`
- Raw SKILL.md: https://api.skillmd.com/api/skills/freemty/update-docs/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Docs & Writing
- Author: freemty (https://skillmd.com/u/freemty)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/freemty/update-docs

---


# Update Docs

Preserve the requested durable record without upgrading its evidence. Read
[the archival contract](../../references/archival-contract.md) before writing.

Use the destination already specified in the task; otherwise inspect the
project's existing conventions and a relevant document. LabMate project docs
and a personal selfOS wiki are different destinations, not automatic mirrors.
Ask only if choosing between them would materially change the requested record.

Use available file reading/search for local knowledge, a source reader or
integration for external text, and browser/media capabilities when the claim
requires visual or temporal evidence. Scripts are useful for extraction and
validation, not a mandatory acquisition chain. Do not repeat completed research
when its artifacts and provenance are adequate.

Update the smallest relevant document. Separate observed facts, user statements,
decisions, model analysis and unresolved hypotheses; include locators and actual
verification/coverage. A request to save an unresolved investigation is valid,
but its proposed cause must not be labeled a verified fix.

Inherit archival authorization from the current task. A read-only question,
generic hook, encountered error or fetched URL does not by itself authorize
writing, wiki compilation, a commit or publication. Existing authorization does
not require a second confirmation.

Check the changed document's links and substantive claims; validate affected
schemas or commands when relevant. Report paths, what was preserved/verified,
and unresolved limits. Do not expand a documentation edit into live-system
changes merely to make the document's instructions pass.