Technical Documentation

This one tackles both product docs and agent instruction files like AGENTS.md, CONTRIBUTING.md, and their aliases across Cursor, Claude, and other tooling. It runs full repo audits, catches governance drift, handles multilingual parity checks, and can spin up sub-agents for large codebases or complex reviews. The workflow distinguishes brownfield (fit existing structure) from evergreen (timeless, maintainable) modes and ships with reference playbooks covering Matt Palmer and OpenAI doc principles. It applies fixes by default instead of just reporting, which saves a round trip. Useful when your repo has grown messy or you're onboarding agents and contributors at the same time.

skills.sh installs: 231
GitHub stars: 111
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add vincentkoc/dotskills --skill technical-documentation --agent claude-code

Installs into .claude/skills of the current project.

Files

Technical Documentation

Purpose

Produce, review, and audit technical documentation that is clear, unambiguous, and maintainable for both humans and agents. Covers product docs, contributor-governance files, and agent instruction files. Prose follows Simplified Technical English so a reader or an agent cannot misread it. Audits scale to trees with hundreds of pages through sharding, adversarial checks, and parallel remediation.