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.
review-simplify - Skill - OpenSmartRoute
Skillv1.0.0
review-simplify
Review a PR for code that can be deleted or simplified. Use when asked to review for simplicity or unnecessary edge-case overengineering.
Imported from every-app/open-seo (.agents/skills/review-simplify/SKILL.md). Install upstream with npx skills add every-app/open-seo --skill review-simplify. Copyright stays with the author.
Review this PR.
Make sure you understand every product decision and change in functionality.
Is there anything that can be deleted or simplified given the end state of the branch?
Are there any edge cases that resulted in overengineering which are unlikely to truly affect customers?
We prefer to delete code.
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://osr-api.kindrock-caaab1a2.centralindia.azurecontainerapps.io/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 review-simplify 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.
When a provider is down or over quota the request moves on; the trace says it did.
Manifest
An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.
every-app-open-seo-review-simplify.ocm.jsonjson
{
"ocm": "1",
"id": "every-app-open-seo-review-simplify",
"kind": "skill",
"name": "review-simplify",
"description": "Review a PR for code that can be deleted or simplified. Use when asked to review for simplicity or unnecessary edge-case overengineering.",
"publisher": "every-app",
"version": "1.0.0",
"capabilities": {
"domains": [
"coding"
],
"tags": [
"skill-md",
"skills-sh"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"Review a PR for code that can be deleted or simplified. Use when asked to review for simplicity or unnecessary edge-case overengineering."
],
"primary": false,
"metadata": {
"source": {
"provider": "skills.sh",
"repository": "https://github.com/every-app/open-seo",
"path": ".agents/skills/review-simplify/SKILL.md",
"ref": "HEAD",
"url": "https://github.com/every-app/open-seo/blob/HEAD/.agents/skills/review-simplify/SKILL.md",
"key": "every-app/open-seo/.agents/skills/review-simplify/SKILL.md"
}
},
"instructions": "Review this PR.\n\nMake sure you understand every product decision and change in functionality.\n\nIs there anything that can be deleted or simplified given the end state of the branch?\n\nAre there any edge cases that resulted in overengineering which are unlikely to truly affect customers?\n\nWe prefer to delete code.",
"cost": {
"context_tokens": 78
}
}
Fetch it by URL: GET /api/v1/registry/every-app-open-seo-review-simplify/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.
