Name: docko-docs
Author: 4riel

Imported from 4riel/docko (.agents/skills/docko-docs/SKILL.md). Install upstream with npx skills add 4riel/docko --skill docko-docs. Copyright stays with the author.

docko Docs

Rules for editing docko's documentation set. Use it before changing any prose surface in this repo.

Read first

docs/development.md
docs/INDEX.md
README.md
The specific guide or example you are changing

Writing rules

Treat protocol docs and schemas as the source of truth.
Do not create a second truth system for command behavior or runtime semantics.
Distinguish clearly between implemented behavior, recommended usage, and roadmap material.
Confirm commands, file paths, and runtime claims in source, templates, or tests before documenting them.
Keep examples short, copy-pastable, and shell-neutral.
Update indexes and contributor-facing docs when adding new guides.
Label runtime examples clearly as one of: shipped Claude Code asset or manual Codex guidance.
Do not present non-Claude runtimes as implemented runtime adapters unless matching packages, templates, and tests exist.

Verify

Re-read every changed doc against the implementation.
Run pnpm build or pnpm test when the documentation depends on command behavior that changed.
Call out any unverified command examples or environment-specific assumptions.

# after Install: the listing is in your workspace's routing pool - a plan picks it for its slot curl -s -X POST https://api.opensmartroute.ai/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'

{ "ocm": "1", "id": "4riel-docko-docko-docs", "kind": "skill", "name": "docko-docs", "description": "Documentation guidance for the docko repository. Use when editing README, docs, examples, snippets, or onboarding guides so the written guidance stays aligned with the implemented protocol and adapters.", "publisher": "4riel", "version": "1.0.0", "capabilities": { "domains": [ "coding", "hr" ], "tags": [ "skill-md", "github" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Documentation guidance for the docko repository. Use when editing README, docs, examples, snippets, or onboarding guides so the written guidance stays aligned with the implemented protocol and adapters." ], "primary": false, "metadata": { "source": { "provider": "github", "repository": "https://github.com/4riel/docko", "path": ".agents/skills/docko-docs/SKILL.md", "ref": "cc31e41ee35b1bad4a717432dd7cd1dda4f12633", "url": "https://github.com/4riel/docko/blob/cc31e41ee35b1bad4a717432dd7cd1dda4f12633/.agents/skills/docko-docs/SKILL.md", "key": "4riel/docko/.agents/skills/docko-docs/SKILL.md" } }, "instructions": "# docko Docs\n\nRules for editing docko's documentation set. Use it before changing any prose surface in this repo.\n\n## Read first\n\n- `docs/development.md`\n- `docs/INDEX.md`\n- `README.md`\n- The specific guide or example you are changing\n\n## Writing rules\n\n- Treat protocol docs and schemas as the source of truth.\n- Do not create a second truth system for command behavior or runtime semantics.\n- Distinguish clearly between implemented behavior, recommended usage, and roadmap material.\n- Confirm commands, file paths, and runtime claims in source, templates, or tests before documenting them.\n- Keep ", "cost": { "context_tokens": 296 } }

docko-docs

About

docko Docs

Read first

Writing rules

Verify

Use it

Manifest

Reviews