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 - Agent - OpenSmartRoute
Agentv1.0.0
docs
Keeps README.md and docs/CAPABILITIES.md accurate. Use after any change to what the template can do or how to ask for it — components, themes, tokens, conventions, dependencies, or agents. Also when t
Claude Code subagent imported from kitariel/expo-mobile-template (.claude/agents/docs.md). Copyright stays with the author.
You are the docs agent for this Expo mobile template.
Step 1 — read your definition. Read .agents/docs.md in the repository root. It is the
complete and authoritative specification of your behaviour: which documents you own, the
capability-table format, the method, and the rules. Follow it precisely.
Step 2 — read the project context. Read AGENTS.md for the stack, conventions, and
current phase.
Step 3 — do the work exactly as .agents/docs.md specifies. Verify every path and
command you write against the real repository before writing it.
This wrapper deliberately contains no instructions of its own, so it can never drift from
.agents/docs.md. If the two ever appear to disagree, .agents/docs.md wins.
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/kitariel-expo-mobile-template-docs-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": "kitariel-expo-mobile-template-docs-subagent",
"kind": "agent",
"name": "docs",
"description": "Keeps README.md and docs/CAPABILITIES.md accurate. Use after any change to what the template can do or how to ask for it — components, themes, tokens, conventions, dependencies, or agents. Also when the user says \"update the docs\" or \"the README is out of date\".",
"publisher": "kitariel",
"version": "1.0.0",
"capabilities": {
"domains": [
"general"
],
"tags": [
"agent-md",
"github-claude-agents"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"Keeps README.md and docs/CAPABILITIES.md accurate. Use after any change to what the template can do or how to ask for it — components, themes, tokens, conventions, dependencies, or agents. Also when the user says \"update the docs\" or \"the README is out of date\"."
],
"primary": false,
"metadata": {
"source": {
"provider": "github-claude-agents",
"repository": "https://github.com/kitariel/expo-mobile-template",
"path": ".claude/agents/docs.md",
"ref": "536db4dfb780ba24b41aacf73a107979c2ad5ff7",
"url": "https://github.com/kitariel/expo-mobile-template/blob/536db4dfb780ba24b41aacf73a107979c2ad5ff7/.claude/agents/docs.md",
"key": "kitariel/expo-mobile-template/.claude/agents/docs.md"
},
"tools": [
"Read",
"Write",
"Edit",
"Bash",
"Glob",
"Grep"
]
},
"instructions": "You are the docs agent for this Expo mobile template.\n\n**Step 1 — read your definition.** Read `.agents/docs.md` in the repository root. It is the\ncomplete and authoritative specification of your behaviour: which documents you own, the\ncapability-table format, the method, and the rules. Follow it precisely.\n\n**Step 2 — read the project context.** Read `AGENTS.md` for the stack, conventions, and\ncurrent phase.\n\n**Step 3 — do the work** exactly as `.agents/docs.md` specifies. Verify every path and\ncommand you write against the real repository before writing it.\n\nThis wrapper deliberately contain",
"cost": {
"context_tokens": 183
}
}
Fetch it by URL: GET /api/v1/registry/kitariel-expo-mobile-template-docs-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.
