Answers from the documentation; checking which model is on duty
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.
aqe-plan-quality - Skill - OpenSmartRoute
Skillv1.0.0
aqe-plan-quality
Create risk-based quality and test plans for Agentic QE changes. Use when scoping a feature, translating requirements into verification work, selecting QE specialties, assessing testability, or…
Imported from proffesor-for-testing/agentic-qe (.agents/skills/aqe-plan-quality/SKILL.md). Install upstream with npx skills add proffesor-for-testing/agentic-qe --skill aqe-plan-quality. Copyright stays with the author.
Plan AQE Quality
Read AGENTS.md, the requested change, and the affected public boundaries.
Inspect the closest implementation and tests before proposing work.
Select only the QE specialties needed. Treat Claude agent definitions as
domain references; do not copy their Claude-only Task, SendMessage, or
hook syntax into Codex actions.
Produce a plan that covers:
observable requirements and acceptance criteria;
affected boundaries, dependencies, and failure modes;
durable tests first, then implementation-coupled tests;
security, performance, accessibility, contract, or resilience checks when
triggered by the change;
the narrowest repository verification commands.
Flag assumptions, unavailable environments, destructive operations, and
decisions requiring human approval.
Prefer evidence from repository code and configuration over generic test
checklists. Keep the selected fleet small and explain each specialty’s purpose.
Use it
Copy one of these into your project. Installing also returns the manifest and these snippets.
# after Install: the listing is in your workspace's routing pool - a plan picks it for its slotcurl-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}'
Installed into a catalogue, chosen by a router
Install aqe-plan-quality and it becomes one more candidate the router can pick - when it fits.
A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.
{
"ocm": "1",
"id": "proffesor-for-testing-agentic-qe-aqe-plan-quality",
"kind": "skill",
"name": "aqe-plan-quality",
"description": "Create risk-based quality and test plans for Agentic QE changes. Use when scoping a feature, translating requirements into verification work, selecting QE specialties, assessing testability, or deciding which `.claude/agents/v3/qe-*.md` capabilities should inform a task. Do not use merely to execute an already-defined test command.",
"publisher": "proffesor-for-testing",
"version": "1.0.0",
"capabilities": {
"domains": [
"coding",
"legal"
],
"tags": [
"skill-md",
"skills-sh"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"Create risk-based quality and test plans for Agentic QE changes. Use when scoping a feature, translating requirements into verification work, selecting QE specialties, assessing testability, or deciding which `.claude/agents/v3/qe-*.md` capabilities should inform a task. Do not use merely to execute an already-defined test command."
],
"primary": false,
"metadata": {
"source": {
"provider": "skills.sh",
"repository": "https://github.com/proffesor-for-testing/agentic-qe",
"path": ".agents/skills/aqe-plan-quality/SKILL.md",
"ref": "HEAD",
"url": "https://github.com/proffesor-for-testing/agentic-qe/blob/HEAD/.agents/skills/aqe-plan-quality/SKILL.md",
"key": "proffesor-for-testing/agentic-qe/.agents/skills/aqe-plan-quality/SKILL.md"
}
},
"instructions": "# Plan AQE Quality\n\n1. Read `AGENTS.md`, the requested change, and the affected public boundaries.\n2. Inspect the closest implementation and tests before proposing work.\n3. Classify the risk domains using [references/qe-routing.md](references/qe-routing.md).\n4. Select only the QE specialties needed. Treat Claude agent definitions as\n domain references; do not copy their Claude-only `Task`, `SendMessage`, or\n hook syntax into Codex actions.\n5. Produce a plan that covers:\n - observable requirements and acceptance criteria;\n - affected boundaries, dependencies, and failure modes;\n - durable tests first, then implementation-coupled tests;\n - security, performance, accessibility, contract, or resilience checks when\n triggered by the change;\n - the narrowest repository verification commands.\n6. Flag assumptions, unavailable environments, destructive operations, and\n decisions requiring human approval.\n\nPrefer evidence from repository code and configuration over generic test\nchecklists. Keep the selected fleet small and explain each specialty’s purpose.",
"cost": {
"context_tokens": 270
}
}
Fetch it by URL: GET /api/v1/registry/proffesor-for-testing-agentic-qe-aqe-plan-quality/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.