Individual skill
octocode-documentation
Use when docs are missing, wrong, stale, or badly written, or need a copyedit against the Google style guide: README, API reference, runbook, CONTRIBUTING, changelog, onboarding, AGENTS.md/CLAUDE.md, ADR, migration guide, Diátaxis or whole-codebase restructure, docstrings, alt text, prose linting. Not for code, commits, or marketing copy. Code investigation → octocode-research; SKILL.md folders → octocode-skills.
skills/octocode-documentation/SKILL.md
Source commit c265e3f9413161c900cbf4aa70d451b8e6b3920a
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Network or broad shell
- Last checked
- Nov 4, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 957
- Repository last updated
- Nov 6, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai Repository topic
- claude-ai Repository topic
- cursor-ai Repository topic
- development Repository topic
- mcp Repository topic
- modelcontextprotocol Repository topic
- octocode Repository topic
- ai-agents Repository topic
- ai-tools Repository topic
- code-intelligence Repository topic
- docs Derived category
- marketing Derived category
- research Derived category
- docs-api Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
README.mddoc · 4,984 bytesSKILL.mdcore · 8,189 bytesassets/google-style-pages.tsvasset · 6,546 bytesassets/google-word-list.tsvasset · 106,691 bytesreferences/adr.mddoc · 1,523 bytesreferences/agent-readable.mddoc · 1,737 bytesreferences/agents-md.mddoc · 1,818 bytesreferences/diataxis.mddoc · 1,410 bytesreferences/evidence-research.mddoc · 1,616 bytesreferences/modes.mddoc · 2,247 bytesreferences/style-abbreviations.mddoc · 2,790 bytesreferences/style-api.mddoc · 3,191 bytesreferences/style-blocks.mddoc · 3,168 bytesreferences/style-claims.mddoc · 3,842 bytesreferences/style-cli.mddoc · 3,771 bytesreferences/style-code.mddoc · 3,228 bytesreferences/style-examples.mddoc · 2,524 bytesreferences/style-format.mddoc · 4,438 bytesreferences/style-global.mddoc · 3,511 bytesreferences/style-grammar.mddoc · 4,151 bytesreferences/style-images.mddoc · 3,136 bytesreferences/style-inclusive.mddoc · 3,418 bytesreferences/style-index.mddoc · 4,133 bytesreferences/style-links.mddoc · 3,409 bytesreferences/style-numbers.mddoc · 5,241 bytesreferences/style-procedures.mddoc · 2,658 bytesreferences/style-punctuation.mddoc · 5,898 bytesreferences/style-review.mddoc · 2,855 bytesreferences/style-sources.mddoc · 3,380 bytesreferences/style-structure.mddoc · 3,974 bytesreferences/style-ui.mddoc · 3,901 bytesreferences/style-voice.mddoc · 4,858 bytesreferences/style-words.mddoc · 3,200 bytesreferences/write-verify.mddoc · 2,338 bytesscripts/refresh-word-list.mjsruns · 7,417 bytesscripts/style-lint.mjsruns · 24,674 bytes
Read excerpt
# Octocode Documentation
Evidence-backed docs for humans and agents, written to the Google developer documentation style guide. Classify first. Gate writes. Prefer durable cross-refs over code dumps.
## Flow
`UNDERSTAND → RESEARCH → CLASSIFY → OUTLINE GATE → WRITE → STYLE → VERIFY`
UNDERSTAND names the deliverable, audience, and target paths. Compress when the request already names targets and type. Expand when claims need verification. A copyedit request starts at STYLE. Answer a single-term question ("is `allows you to` okay?") straight from `assets/google-word-list.tsv` — quote the guidance and stop.
## Rules
- Verify claims in the repository before asserting them. Invented commands, paths, APIs, and env vars are the one unrecoverable failure — omit or mark "Not verified in repository" instead.
- Pick one mode and load its routes before writing.