What is technical-documentation?

A set of rules for writing and reviewing technical documentation and instruction files in a software repository. It covers product docs, contributor guides, and files that tell coding agents how to work.

Use it to create or overhaul documentation, review doc changes, audit repository docs, and align contributor or agent instructions.

It helps keep documentation clear, usable, consistent with the codebase, and maintainable as the project changes.

technical-documentation — Skill by vincentkoc

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add skills/vincentkoc/dotskills/technical-documentation

Any agent

npx skills add vincentkoc/dotskills --skill technical-documentation

Clone the repo

git clone --depth 1 https://github.com/vincentkoc/dotskills

Made for: Claude Code, Codex.

Per session 21 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,178 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5	$0.00021	$0.01178
Opus 5	$0.00010	$0.00589
Sonnet 5	$0.00004	$0.00236
Haiku 4.5	$0.00002	$0.00118

Measured 3d ago against content hash e9325cdfb92c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

technical-documentation scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/technical-documentation/SKILL.md · 76 lines

How it starts

The opening of the file, as written. The whole thing — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Technical Documentation

Purpose

Produce and review technical documentation that is clear, actionable, and maintainable for both humans and agents, including contributor-governance files and agent instruction files.

When to use

Creating or overhauling docs in an existing product/codebase (brownfield).
Building evergreen docs meant to stay accurate and reusable over time.
Reviewing doc diffs for structure, clarity, and operational correctness.
Running full-repo documentation audits that must include both governance files and product docs surfaces (docs/, README*, .md/.mdx/.mdc, Fern/Sphinx/Mintlify-style sources).
Updating or reviewing AGENTS.md and/or CONTRIBUTING.md to keep agent and contributor workflows aligned with current repo practices.
Improving repository onboarding/docs that include contribution instructions, issue templates, PR flow, and review gates.
Designing governance documentation strategy for repos with alias instruction files (for example CLAUDE.md, AGENT.md, .cursorrules, .cursor/rules/*, .agent/, .agents/, .pi/) where CLAUDE.md is treated as a canonical policy source and AGENTS.md should be kept as compatibility alias if present.
Diagnosing agent-file drift where teams had to prompt iteratively to surface missing files, broken commands, or policy conflicts.

Workflow

Classify task: build or review; context: brownfield or evergreen.
Inventory full documentation scope early (governance + product docs): AGENTS/CONTRIBUTING/aliases plus docs directories, framework sources, and root/module READMEs.
Detect multilingual scope (README/docs in multiple languages) and define required parity level.
Read references/agent-and-contributing.md for agent instruction and CONTRIBUTING.md workflow rules (inventory, canonical/alias mapping, dual-mode balance, deliverable standards, and precedence/conflict handling).
Read references/principles.md for the governing ruleset (Matt Palmer & OpenAI).
For build tasks, follow references/build.md.
For review tasks, follow references/review.md and proactively detect issues without waiting for repeated prompts.
For complex or high-risk tasks (build or review), it is acceptable to run longer, deeper, and more exhaustive investigations when needed for confidence.
When available, use sub-agents for bounded parallel discovery/review work, then merge outputs into one coherent final deliverable.
Use references/tooling.md when platform/tooling choices affect recommendations.
Run a proactive issue sweep for both governance and docs-content surfaces, and fix high-confidence defects in the same pass unless explicitly asked for report-only mode.
In brownfield mode, prioritize compatibility with current docs IA, tooling, and release state.
In evergreen mode, prioritize timeless wording, update strategy, and durable structure.
Return deliverables plus validation notes, parity status, and remaining gaps.

Read the full file on GitHub · 76 lines

Files

What ships with it

11 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

3d ago First seen · 76 lines · 21 tokens per session scan A e9325cdfb92c

Subscribe to this mod's changes

technical-documentation is a skill published in the GitHub repository vincentkoc/dotskills (102 stars, last pushed 11d ago), licensed MIT. It adds 21 tokens to every session and 1,178 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Building agents LLM Writing and docs agentic-workflows ai-assistant automation codex developer-tools

panel-app-creator

Create or update the Panel App UI part of a NextClaw lightweight app. Use after nextclaw-app-creator selects Panel-only or Panel + Service, or when the user explicitly asks for a right-side Panel App UI, folder-based static panel, Service Actions UI, Agent-powered Panel App, React/Vite/Tailwind Panel App, or asks what…

Peiiii/nextclaw · 93 tokens

service-app-creator

Create or update the Service App backend action part of a NextClaw lightweight app. Use after nextclaw-app-creator selects Service-only or Panel + Service, or when the user explicitly asks for workspace service-apps, MCP-compatible backend helpers, file access, external API calls, local commands, or privileged actions.

Peiiii/nextclaw · 69 tokens

technical-documentation