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.
Imported from jeremylongshore/tons-of-skills-marketplace (plugins/saas-packs/skill-databases/windsurf/skills/windsurf-release-automation/SKILL.md). Install upstream with npx skills add jeremylongshore/tons-of-skills-marketplace --skill windsurf-release-automation. Copyright stays with the author (MIT).
Windsurf Release Automation
Overview
This skill enables automated release workflows within Windsurf using Cascade AI. It analyzes commits to determine semantic version bumps, generates comprehensive changelogs, manages Git tags, and publishes releases.
Prerequisites
Windsurf IDE with Cascade enabled
Git repository with commit history
Conventional commits or consistent commit format
npm/yarn/pnpm for JavaScript projects (or equivalent)
CI/CD pipeline for automated publishing (optional)
Instructions
Configure Version Strategy
Set Up Automation
Prepare Release
Execute Release
Post-Release Tasks
See ${CLAUDE_SKILL_DIR}/references/implementation.md for detailed implementation guide.
Output
Updated version in package.json
Generated CHANGELOG.md entry
Git tag for release version
Published package to registry
Release notes for distribution
Error Handling
See ${CLAUDE_SKILL_DIR}/references/errors.md for comprehensive error handling.
Examples
See ${CLAUDE_SKILL_DIR}/references/examples.md for detailed examples.
Install windsurf-release-automation 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.
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}'
Manifest
An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.
