Doc Co-Authoring Workflow
shareAI-lab/Kode-CLI
Guides a three-stage workflow for turning partial context into a clear PRD, RFC or design doc: capture context, draft section by section, then test with a fresh reader.
Maintain project documentation in .claude/skills/project-knowledge/: audit, edit, check consistency, track status.
Install Documentation Writing
$ npx skills add radix-ng/primitives --skill documentation-writing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install radix-ng/primitives documentation-writing --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/radix-ng/primitives.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/documentation-writing .claude/skills/documentation-writing && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "documentation-writing" agent skill from https://github.com/radix-ng/primitives/tree/main/.claude/skills/documentation-writing into .claude/skills/documentation-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "documentation-writing", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/radix-ng/primitives/tree/main/.claude/skills/documentation-writingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add radix-ng/primitives --skill documentation-writing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install radix-ng/primitives documentation-writing --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/radix-ng/primitives.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/documentation-writing .agents/skills/documentation-writing && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "documentation-writing" agent skill from https://github.com/radix-ng/primitives/tree/main/.claude/skills/documentation-writing into .agents/skills/documentation-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "documentation-writing", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add radix-ng/primitives --skill documentation-writing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install radix-ng/primitives documentation-writing --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/radix-ng/primitives.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/documentation-writing .cursor/skills/documentation-writing && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "documentation-writing" agent skill from https://github.com/radix-ng/primitives/tree/main/.claude/skills/documentation-writing into .cursor/skills/documentation-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "documentation-writing", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/radix-ng/primitives.git --path .claude/skills/documentation-writing--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add radix-ng/primitives --skill documentation-writing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install radix-ng/primitives documentation-writing --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/radix-ng/primitives.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/documentation-writing .gemini/skills/documentation-writing && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "documentation-writing" agent skill from https://github.com/radix-ng/primitives/tree/main/.claude/skills/documentation-writing into .gemini/skills/documentation-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "documentation-writing", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install radix-ng/primitives documentation-writingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add radix-ng/primitives --skill documentation-writing -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/radix-ng/primitives.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/documentation-writing .github/skills/documentation-writing && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "documentation-writing" agent skill from https://github.com/radix-ng/primitives/tree/main/.claude/skills/documentation-writing into .github/skills/documentation-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "documentation-writing", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add radix-ng/primitives --skill documentation-writing -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install radix-ng/primitives documentation-writing --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/radix-ng/primitives.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/documentation-writing .opencode/skills/documentation-writing && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "documentation-writing" agent skill from https://github.com/radix-ng/primitives/tree/main/.claude/skills/documentation-writing into .opencode/skills/documentation-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "documentation-writing", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
documentation-writing- GitHub stars
- 274
- Token cost
- ~1.4k tokens
- SKILL.md length
- 626 words
- Files
- 1
- Skills in repo
- 7
- Repo updated
- First seen
- Licence
- MIT
At a glance
Maintain project documentation in .claude/skills/project-knowledge/: audit, edit, check consistency, track status.
- Works in 4 steps: Audit → Edit → Check Consistency → …
- : проверь документацию
- SKILL.md covers Documentation Principles, File Structure, Workflows and Root Project Files, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Documentation Writing is an agent skill from radix-ng/primitives. Maintain project documentation in .claude/skills/project-knowledge/: audit, edit, check consistency, track status. Use when: "проверь документацию", "обнови документацию", "аудит документации", "check docs", "audit documentation", "update docs", "проверь базу знаний проекта" For creating documentation from scratch use project-planning skill. For reading docs or explaining concepts, read project-knowledge skill directly.
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Writing & Content, covering Technical writing and Project management. The repository describes itself as: Headless, signals-first UI primitives for Angular. Accessible. Customizable. The licence is MIT.
When your agent uses it
- : проверь документацию
- Обнови документацию
- Аудит документации
- Audit documentation
Example prompts
- “check docs”
- “audit documentation”
- “update docs”
- “/documentation-writing”
Workflow steps
4 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit eed2a31. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Documentation Writing loads about 1.4k tokens when it runs. Until then it costs about 112 tokens; SKILL.md has 626 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from radix-ng/primitives at commit eed2a31, republished under its MIT licence (© radix-ng). 626 words, ~1,447 tokens.
Download SKILL.mdSave it as
.claude/skills/documentation-writing/SKILL.md (or your agent's skills folder).- name
- documentation-writing
- description
- Maintain project documentation in .claude/skills/project-knowledge/: audit, edit, check consistency, track status. Use when: "проверь документацию", "обнови документацию", "аудит документации", "check docs", "audit documentation", "update docs", "проверь базу знаний проекта" For creating documentation from scratch use project-planning skill. For reading docs or explaining concepts, read project-knowledge skill directly.
Documentation Management
Maintain project documentation in .claude/skills/project-knowledge/references/. Audit for bloat, edit files, check consistency, track status.
For creating documentation from scratch (new project or empty docs), use project-planning skill.
Documentation Principles
These rules apply to ALL documentation operations (audit, edit, create).
Goal: open docs → understand the project without reading code. What is this project, how it's structured, what it does, where to find key things, how to deploy, where are logs. A high-level navigation guide.
Describe what exists, what it does, and why. High-level overview of components, how they work together, decisions made (why this stack, why this architecture), operational details (server addresses, deploy procedures, log locations, env var names). Skip what's obvious from reading the code itself — function signatures, implementation details, generic framework behavior.
No code blocks, no pseudocode. Code in docs gets outdated and bloats context.
No duplication between files. Information lives in ONE place. Cross-reference: "See deployment.md for env vars."
patterns.md: only project-specific patterns. Universal coding standards. Project patterns.md contains only what's unique to THIS project.
File Structure
4 core files in .claude/skills/project-knowledge/references/:
| File | Contains |
|---|---|
| project.md | Overview, audience, problem, 3-5 key features, out of scope |
| architecture.md | Tech stack (with WHY), project structure, dependencies, integrations, data model |
| patterns.md | Project-specific code patterns, git workflow, testing methods, business rules |
| deployment.md | Platform, env var names, CI/CD triggers, rollback, monitoring |
Optional:
- ux-guidelines.md — only for projects with significant UI
- {custom}.md — domain-specific
Templates with placeholder structure are in .claude/shared/templates/new-project/.claude/skills/project-knowledge/references/. The templates are self-documenting — each section has comments explaining what to write.
Workflows
1. Audit
Trigger: User asks to audit, check quality, or find bloat.
- Read all files from
.claude/skills/project-knowledge/references/+ CLAUDE.md + README.md - Flag issues:
- Code blocks → replace with file references
- Generic framework knowledge (belongs in official docs) → remove
- Function-level details → suggest moving to code comments
- Bloated sections (>3-5KB per file is suspicious) → condense
- Duplication across files → consolidate to one place
- Placeholder text (
[Project Name],TODO) → fill or remove - Inconsistent terminology → standardize
- Outdated info (files/functions that no longer exist) → update or remove
- Universal patterns in patterns.md → flag for removal (those belong in code-writing skill)
- Preserve operational details: server addresses, SSH configs, deploy commands, log paths, env var names, monitoring URLs. These belong in docs even if they seem "obvious" — they can't be read from code.
- Create audit report with issues by file
- Ask user which to fix → apply approved changes → verify consistency
Show full SKILL.md (235 more words)Show less
2. Edit
Trigger: User asks to edit or update specific documentation.
- Identify target file/section (ask if unclear)
- Read current content
- Apply changes following documentation principles
- Check if changes affect other files (e.g., tech stack mentioned elsewhere) → update related files
3. Check Consistency
Trigger: User asks to verify terminology or check for mismatches.
- Read all project-knowledge files
- Extract: tech stack names/versions, service names, DB names, env var names, platform names
- Find inconsistencies (e.g., "PostgreSQL" vs "Postgres" vs "postgres")
- Report → ask user for correct terminology → standardize across all files
4. Show Status
Trigger: User asks about documentation completeness.
- Check each file: exists? filled or template? size? last modified?
- Classify: filled / partially filled / template / missing
- Show status report with recommendations
Root Project Files
CLAUDE.md and README.md are entry points, not documentation. Keep them minimal — they point to project-knowledge, not contain information.
CLAUDE.md (for AI agents): project name, one-line description, reference to project-knowledge skill, backlog path, default branch. Template: .claude/shared/templates/new-project/CLAUDE.md.
README.md (for humans, in Russian): project title, purpose, folder structure overview, link to references/. Template: .claude/shared/templates/new-project/README.md.
When auditing, verify that CLAUDE.md and README.md stay minimal — detailed info belongs in project-knowledge.
Custom Domain Files
Add when project has a significant domain not covered by 4 core files (bot.md, vault.md, trading.md).
Process: create in references/ → update project-knowledge SKILL.md to list it → update CLAUDE.md and README.md if they list doc files.
© radix-ng, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .claude/skills/documentation-writing of radix-ng/primitives.
Open the folder on GitHubat commit eed2a31
Compare with similar skills
Documentation Writing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Documentation Writing this skillradix-ng/primitives | 274 | — | ~1.4k | Automated safety check: Pass | MIT | |
| Doc Co-Authoring WorkflowshareAI-lab/Kode-CLI | 5.2k | — | ~977 | Automated safety check: Pass | Apache-2.0 | |
| Program Managerborghei/Claude-Skills | 881 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Linkedin Announcement Generatordmccreary/ibook-skills | 105 | — | ~5k | Automated safety check: Pass | CC-BY-NC-4.0 | |
| JavaScript Concept Fact Checkerleonardomso/33-js-concepts | 67k | 1 repos | ~5k | Automated safety check: Pass | MIT | |
| Beads Documentation Style Guidegastownhall/beads | 28k | — | ~3.2k | Automated safety check: Pass | MIT |
Similar skills
Program Manager
borghei/Claude-Skills
Program management for multi-project coordination, portfolio governance, dependency tracking, benefits realization, charters, and steering-committee reporting.
Linkedin Announcement Generator
dmccreary/ibook-skills
Generates a LinkedIn post announcing an intelligent textbook milestone by pulling book metrics, chapter count, and key statistics.
JavaScript Concept Fact Checker
leonardomso/33-js-concepts
Verifies the technical accuracy of JavaScript concept pages by checking code examples, MDN and ECMAScript claims and external links through a five-phase method.
Beads Documentation Style Guide
gastownhall/beads
Sets the house style for the beads user docs: the canonical concept model, required terminology, prose and diagram conventions, and checks before docs work is done.
JavaScript Concept Page Workflow
leonardomso/33-js-concepts
Orchestrates five skills to produce a complete JavaScript concept documentation page, from resource curation through writing, tests, fact-checking and SEO.
More from radix-ng/primitives
Radix Ng
radix-ng/primitives
Build correct, accessible UI with @radix-ng/primitives — the signals-first, headless Angular primitive library.
Radix Ng Examples
radix-ng/primitives
Index of every documented @radix-ng/primitives example. An agent skill from radix-ng/primitives.
Project Knowledge
radix-ng/primitives
A skill your agent uses when you need information about this project's architecture, tech stack, coding patterns, data model, deployment setup, git workflow, or UX guidelines.
Storybook Story
radix-ng/primitives
Write or update Storybook stories and docs MDX for a Radix NG primitive following project conventions.
Testing
radix-ng/primitives
Test Radix NG primitives across every layer and pick the RIGHT one for a change: Vitest unit (zoneless), jest-axe a11y, Playwright browser regression (apps/visual-regression), SSR…
Angular Developer
radix-ng/primitives
Angular framework reference for building this signals-first, headless directive library.
Related
Questions about Documentation Writing
What does Documentation Writing do?
Maintain project documentation in .claude/skills/project-knowledge/: audit, edit, check consistency, track status. Documentation Writing is an agent skill from radix-ng/primitives.claude/skills/project-knowledge/: audit, edit, check consistency, track status.
When should I use Documentation Writing?
Documentation Writing fits situations like: : проверь документацию; Обнови документацию; Аудит документации; audit documentation.
How do I install Documentation Writing in Claude Code?
Run `npx skills add radix-ng/primitives --skill documentation-writing -a claude-code`. Or copy the skill folder (.claude/skills/documentation-writing in radix-ng/primitives) into .claude/skills/documentation-writing in your project. Claude Code loads it when a task matches its description.
How do I install Documentation Writing in Codex?
Run `npx skills add radix-ng/primitives --skill documentation-writing -a codex`. Or copy the skill folder (.claude/skills/documentation-writing in radix-ng/primitives) into .agents/skills/documentation-writing in your project. Codex loads it when a task matches its description.
Can I use Documentation Writing in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add radix-ng/primitives --skill documentation-writing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/documentation-writing, .gemini/skills/documentation-writing, .github/skills/documentation-writing and .opencode/skills/documentation-writing in your project.
What does Documentation Writing need to run?
SKILL.md names no scripts, command-line tools or credentials: Documentation Writing is instructions for the agent only.
Does Documentation Writing access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Documentation Writing safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Documentation Writing use?
Documentation Writing is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Documentation Writing use?
About 1.4k tokens (SKILL.md is roughly 5.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Documentation Writing?
Skills that share tags, products or a category with Documentation Writing: Doc Co-Authoring Workflow (shareAI-lab/Kode-CLI, 5.2k stars), Program Manager (borghei/Claude-Skills, 881 stars), Linkedin Announcement Generator (dmccreary/ibook-skills, 105 stars) and JavaScript Concept Fact Checker (leonardomso/33-js-concepts, 67k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Documentation Writing?
radix-ng (a GitHub organization) maintains it in radix-ng/primitives, which has 274 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on September 28, 2026.
Source: radix-ng/primitives on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.