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.
Apply when introducing a new internal API while old callers still exist. Migrate callers and delete the old API in the same wave instead of preserving compatibility layers.
Imported from cursor/plugins (pstack/skills/principle-migrate-callers-then-delete-legacy-apis/SKILL.md) via skills.sh. Install upstream with npx skills add cursor/plugins --skill principle-migrate-callers-then-delete-legacy-apis. Copyright stays with the author.
Migrate Callers Then Delete Legacy APIs
Update tests to assert the new contract, and delete tests that only protect pre-refactor implementation details
When this applies:
No external users depend on backward compatibility
The project can absorb coordinated breaking changes
The new API is part of a simplification or refactor initiative
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 principle-migrate-callers-then-delete-legacy-apis 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": "cursor-plugins-principle-migrate-callers-then-delete-leg-9c5d92",
"kind": "skill",
"name": "principle-migrate-callers-then-delete-legacy-apis",
"description": "Apply when introducing a new internal API while old callers still exist. Migrate callers and delete the old API in the same wave instead of preserving compatibility layers.",
"publisher": "cursor",
"version": "1.0.0",
"capabilities": {
"domains": [
"coding",
"legal"
],
"tags": [
"skill-md",
"skills-sh"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"Apply when introducing a new internal API while old callers still exist. Migrate callers and delete the old API in the same wave instead of preserving compatibility layers."
],
"primary": false,
"metadata": {
"source": {
"provider": "skills.sh",
"repository": "https://github.com/cursor/plugins",
"path": "pstack/skills/principle-migrate-callers-then-delete-legacy-apis/SKILL.md",
"ref": "HEAD",
"url": "https://www.skills.sh/cursor/plugins/principle-migrate-callers-then-delete-legacy-apis",
"key": "cursor/plugins/pstack/skills/principle-migrate-callers-then-delete-legacy-apis/SKILL.md"
}
},
"instructions": "# Migrate Callers Then Delete Legacy APIs\n\n- Update tests to assert the new contract, and delete tests that only protect pre-refactor implementation details\n\n**When this applies:**\n- No external users depend on backward compatibility\n- The project can absorb coordinated breaking changes\n- The new API is part of a simplification or refactor initiative",
"cost": {
"context_tokens": 88
}
}
Fetch it by URL: GET /api/v1/registry/cursor-plugins-principle-migrate-callers-then-delete-leg-9c5d92/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.
