Correct
cursor/plugins
Find the mistakes agents keep repeating in this repo and make each one impossible.
Organizes repository documentation and keeps new docs in the correct location.
MITAuto-check passed
Install Docs Governance
$ npx skills add clawdotnet/openclaw.net --skill docs-governance -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install clawdotnet/openclaw.net docs-governance --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/clawdotnet/openclaw.net.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/docs-governance .claude/skills/docs-governance && 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 "docs-governance" agent skill from https://github.com/clawdotnet/openclaw.net/tree/main/.github/skills/docs-governance into .claude/skills/docs-governance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docs-governance", 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/clawdotnet/openclaw.net/tree/main/.github/skills/docs-governanceType 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 clawdotnet/openclaw.net --skill docs-governance -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install clawdotnet/openclaw.net docs-governance --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/clawdotnet/openclaw.net.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.github/skills/docs-governance .agents/skills/docs-governance && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "docs-governance" agent skill from https://github.com/clawdotnet/openclaw.net/tree/main/.github/skills/docs-governance into .agents/skills/docs-governance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docs-governance", 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 clawdotnet/openclaw.net --skill docs-governance -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install clawdotnet/openclaw.net docs-governance --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/clawdotnet/openclaw.net.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.github/skills/docs-governance .cursor/skills/docs-governance && 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 "docs-governance" agent skill from https://github.com/clawdotnet/openclaw.net/tree/main/.github/skills/docs-governance into .cursor/skills/docs-governance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docs-governance", 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/clawdotnet/openclaw.net.git --path .github/skills/docs-governance--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 clawdotnet/openclaw.net --skill docs-governance -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install clawdotnet/openclaw.net docs-governance --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/clawdotnet/openclaw.net.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.github/skills/docs-governance .gemini/skills/docs-governance && 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 "docs-governance" agent skill from https://github.com/clawdotnet/openclaw.net/tree/main/.github/skills/docs-governance into .gemini/skills/docs-governance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docs-governance", 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 clawdotnet/openclaw.net docs-governanceInstalls 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 clawdotnet/openclaw.net --skill docs-governance -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/clawdotnet/openclaw.net.git skills-src && mkdir -p .github/skills && cp -r skills-src/.github/skills/docs-governance .github/skills/docs-governance && 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 "docs-governance" agent skill from https://github.com/clawdotnet/openclaw.net/tree/main/.github/skills/docs-governance into .github/skills/docs-governance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docs-governance", 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 clawdotnet/openclaw.net --skill docs-governance -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install clawdotnet/openclaw.net docs-governance --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/clawdotnet/openclaw.net.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.github/skills/docs-governance .opencode/skills/docs-governance && 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 "docs-governance" agent skill from https://github.com/clawdotnet/openclaw.net/tree/main/.github/skills/docs-governance into .opencode/skills/docs-governance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docs-governance", 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
docs-governance- GitHub stars
- 519
- Token cost
- ~441 tokens
- SKILL.md length
- 213 words
- Files
- 1
- Skills in repo
- 12
- Repo updated
- First seen
- Licence
- MIT
At a glance
Organizes repository documentation and keeps new docs in the correct location.
- Works in 4 steps: Documentation placement rules → Naming and structure rules → Change rules → …
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Docs Governance is an agent skill from clawdotnet/openclaw.net. Organizes repository documentation and keeps new docs in the correct location.
Its SKILL.md is about 440 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: Self-hosted Enterprise and Personal AI + agent runtime in .NET (NativeAOT-friendly). The licence is MIT.
Example prompts
- “Use the docs-governance skill to organiz repository documentation and keeps new docs in the correct location”
- “/docs-governance”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Documentation placement rules
- Naming and structure rules
- Change rules
- Default behavior
What it can do on your machine
Read from SKILL.md and the folder at commit 2344435. 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
Docs Governance loads about 441 tokens when it runs. Until then it costs about 24 tokens; SKILL.md has 213 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 clawdotnet/openclaw.net at commit 2344435, republished under its MIT licence (© clawdotnet). 213 words, ~441 tokens.
Download SKILL.mdSave it as
.claude/skills/docs-governance/SKILL.md (or your agent's skills folder).- name
- docs-governance
- description
- Organizes repository documentation and keeps new docs in the correct location.
Use this skill when creating, moving, or reorganizing Markdown documentation in this repository.
Documentation placement rules
- Put product, setup, architecture, operations, compatibility, roadmap, and engineering notes in
docs/. - Keep repository-standard meta files at the repo root only when the platform or community expects them there:
README.md,CHANGELOG.md,SECURITY.md,CONTRIBUTING.md,CODE_OF_CONDUCT.md, andLICENSE. - Keep Copilot and agent customization files where the tooling expects them:
AGENTS.md,.github/copilot-instructions.md, and.github/skills/**/SKILL.md. - Keep shipped OpenClaw runtime skills under
src/OpenClaw.Gateway/skills/<skill>/SKILL.md; do not move those intodocs/.
- Put product, setup, architecture, operations, compatibility, roadmap, and engineering notes in
Naming and structure rules
- Prefer
docs/<topic>.mdwith descriptive kebab-case names for new documentation. - If a topic grows, create a focused subfolder under
docs/rather than adding more root Markdown files. - Do not add general documentation to the repository root.
- Prefer
Change rules
- When moving or adding docs, update relative links in the same change.
- Update README quick links when the document is user-facing or operationally important.
- Do not move issue templates, pull request templates, licenses, or any
SKILL.mdfiles unless the task is specifically about those systems.
Default behavior
- If a new Markdown document is requested and no location is specified, place it in
docs/. - If a document mixes repository policy and product guidance, keep the policy file in its standard root location and move the product guidance into
docs/.
- If a new Markdown document is requested and no location is specified, place it in
© clawdotnet, 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 .github/skills/docs-governance of clawdotnet/openclaw.net.
Open the folder on GitHubat commit 2344435
Compare with similar skills
Docs Governance 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 |
|---|---|---|---|---|---|---|
| Docs Governance this skillclawdotnet/openclaw.net | 519 | — | ~441 | Automated safety check: Pass | MIT | |
| Correctcursor/plugins | 10k | 3 repos | ~612 | Automated safety check: Pass | None | |
| Organizationthedaviddias/Front-End-Checklist | 74k | — | ~609 | Automated safety check: Pass | MIT | |
| File Organizerdavila7/claude-code-templates | 32k | 6 repos | ~1.6k | Automated safety check: Pass | MIT | |
| CorrectionNxcoreAI/EverRoom | 3k | — | ~290 | Automated safety check: Pass | Custom licence | |
| Living Docs Governanceaffaan-m/ECC | 274k | 1 repos | ~2.1k | Automated safety check: Pass | MIT |
Similar skills
- Official
Organization
thedaviddias/Front-End-Checklist
A skill your agent uses when auditing structured data on a business or brand website homepage.
File Organizer
davila7/claude-code-templates
Intelligently organizes files and folders by understanding context, finding duplicates, and suggesting better organizational structures.
Correction
NxcoreAI/EverRoom
Compute Room overview corrections—citation corrections as per-claim edits and general corrections as a single proposal.
Living Docs Governance
affaan-m/ECC
Keep a long-lived project's documentation from rotting by assigning existing project docs clear constitution, map, status, and history roles, then wiring the active agent harness to those canonical…
Organize Space
asgeirtj/system_prompts_leaks
Organize existing ChatGPT Pages and Space structure when the user requests changes to that structure.
More from clawdotnet/openclaw.net
All 12 skills in this repoHistory Explorer
clawdotnet/openclaw.net
Inspect recent session conversation turns and meta-run history.
Meta Skill Creator
clawdotnet/openclaw.net
Use this meta-skill instead of answering directly only when the current user explicitly asks to create, compose, synthesize, or propose a new meta-skill that orchestrates multiple existing skills.
Community Research Insight
clawdotnet/openclaw.net
Extract structured insight briefs from community research transcripts or notes.
Summarize
clawdotnet/openclaw.net
Summarize, condense, or digest content into structured key points, details, and action items.
Daily News Digest
clawdotnet/openclaw.net
Produce a daily news brief (AI/security/dev) with links, key takeaways, and action items.
Data Analyst
clawdotnet/openclaw.net
Connects to databases, runs SQL queries, and analyzes datasets using code to provide actionable business insights.
Questions about Docs Governance
What does Docs Governance do?
Organizes repository documentation and keeps new docs in the correct location. net. Organizes repository documentation and keeps new docs in the correct location.
How do I install Docs Governance in Claude Code?
Run `npx skills add clawdotnet/openclaw.net --skill docs-governance -a claude-code`. Or copy the skill folder (.github/skills/docs-governance in clawdotnet/openclaw.net) into .claude/skills/docs-governance in your project. Claude Code loads it when a task matches its description.
How do I install Docs Governance in Codex?
Run `npx skills add clawdotnet/openclaw.net --skill docs-governance -a codex`. Or copy the skill folder (.github/skills/docs-governance in clawdotnet/openclaw.net) into .agents/skills/docs-governance in your project. Codex loads it when a task matches its description.
Can I use Docs Governance 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 clawdotnet/openclaw.net --skill docs-governance -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/docs-governance, .gemini/skills/docs-governance, .github/skills/docs-governance and .opencode/skills/docs-governance in your project.
What does Docs Governance need to run?
SKILL.md names no scripts, command-line tools or credentials: Docs Governance is instructions for the agent only.
Does Docs Governance 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 Docs Governance 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 Docs Governance use?
Docs Governance 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 Docs Governance use?
About 441 tokens (SKILL.md is roughly 1.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 Docs Governance?
Skills that share tags, products or a category with Docs Governance: Correct (cursor/plugins, 10k stars), Organization (thedaviddias/Front-End-Checklist, 74k stars), File Organizer (davila7/claude-code-templates, 32k stars) and Correction (NxcoreAI/EverRoom, 3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Docs Governance?
clawdotnet (a GitHub organization) maintains it in clawdotnet/openclaw.net, which has 519 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on October 3, 2026.
Source: clawdotnet/openclaw.net on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.