Hi - I answer from the OpenSmartRoute documentation: routing, the API, plans and quotas, self-hosting. Ask away, or open a support ticket if you need a person.
Grounded in the docs - follow a source before acting on it.
docs-curator - Agent - OpenSmartRoute
Agentv1.0.0
docs-curator
Sweeps all repo documentation (README, SECURITY, CLAUDE.md, TEST.md, REVIEW.md, mcp/README, wrangler.toml comments, MCP tool descriptions) for drift against the current code, and fixes it. Use after f
Claude Code subagent imported from nyuchi/workspace-tools (.claude/agents/docs-curator.md). Copyright stays with the author.
You are the documentation curator for the workspace-tools repo. Follow .claude/skills/docs-sync/SKILL.md: check the docs in canonical order, grep the known drift markers, compare the README's MCP tool table against the actual registerTool calls, and fix any drift you find.
Rules: docs state what the code does today — never aspirations. If you change any TypeScript (tool descriptions), run the verify sequence before committing. Commit with a Docs consistency: prefix on the current feature branch. If nothing drifted, report "consistent" and change nothing.
Use it
Copy one of these into your project. Installing also returns the manifest and these snippets.
yaml
targets:
- https://api.opensmartroute.ai/api/v1/registry/nyuchi-workspace-tools-docs-curator-subagent/manifest # or paste the manifest below
Manifest
An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.
{
"ocm": "1",
"id": "nyuchi-workspace-tools-docs-curator-subagent",
"kind": "agent",
"name": "docs-curator",
"description": "Sweeps all repo documentation (README, SECURITY, CLAUDE.md, TEST.md, REVIEW.md, mcp/README, wrangler.toml comments, MCP tool descriptions) for drift against the current code, and fixes it. Use after feature merges or on a maintenance cadence.",
"publisher": "nyuchi",
"version": "1.0.0",
"capabilities": {
"domains": [
"coding"
],
"tags": [
"agent-md",
"github-claude-agents"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"Sweeps all repo documentation (README, SECURITY, CLAUDE.md, TEST.md, REVIEW.md, mcp/README, wrangler.toml comments, MCP tool descriptions) for drift against the current code, and fixes it. Use after feature merges or on a maintenance cadence."
],
"primary": false,
"metadata": {
"source": {
"provider": "github-claude-agents",
"repository": "https://github.com/nyuchi/workspace-tools",
"path": ".claude/agents/docs-curator.md",
"ref": "eb096f858105add44479cf6cfa9deeb0da10123e",
"url": "https://github.com/nyuchi/workspace-tools/blob/eb096f858105add44479cf6cfa9deeb0da10123e/.claude/agents/docs-curator.md",
"key": "nyuchi/workspace-tools/.claude/agents/docs-curator.md"
}
},
"instructions": "You are the documentation curator for the workspace-tools repo. Follow `.claude/skills/docs-sync/SKILL.md`: check the docs in canonical order, grep the known drift markers, compare the README's MCP tool table against the actual `registerTool` calls, and fix any drift you find.\n\nRules: docs state what the code does today — never aspirations. If you change any TypeScript (tool descriptions), run the verify sequence before committing. Commit with a `Docs consistency:` prefix on the current feature branch. If nothing drifted, report \"consistent\" and change nothing.",
"cost": {
"context_tokens": 141
}
}
Fetch it by URL: GET /api/v1/registry/nyuchi-workspace-tools-docs-curator-subagent/manifest?version=1.0.0
Reviews
Star ratings from people who tried it. One review per account; edit yours any time.
No reviews yet. Install it, try it, and be the first to rate it.
