OpenParable
Skip to content
← Back to skills

Docs Governance

Documents
docs-governance

Docs Governance is an Agent Skill for documents published in the clawdotnet/openclaw.net repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Organizes repository documentation and keeps new docs in the correct location.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/clawdotnet/openclaw.net/blob/HEAD/.github/skills/docs-governance/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/docs-governance, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Use this skill when creating, moving, or reorganizing Markdown documentation in this repository.

  1. 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, and LICENSE.
    • 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 into docs/.

  2. Naming and structure rules

    • Prefer docs/<topic>.md with 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.

  3. 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.md files unless the task is specifically about those systems.

  4. 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/.