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.
windsurf-team-settings - Skill - OpenSmartRoute
Skillv1.0.0
windsurf-team-settings
Manage team-wide Windsurf settings and AI policies. Activate when users mention "team settings", "organization config", "team policies", "shared settings", or "team standardization".
Imported from jeremylongshore/tons-of-skills-marketplace (plugins/saas-packs/skill-databases/windsurf/skills/windsurf-team-settings/SKILL.md). Install upstream with npx skills add jeremylongshore/tons-of-skills-marketplace --skill windsurf-team-settings. Copyright stays with the author (MIT).
Windsurf Team Settings
Overview
This skill enables centralized management of Windsurf settings across teams and organizations. It covers editor preferences, AI behavior policies, tool approvals, and compliance requirements.
Prerequisites
Windsurf Enterprise subscription
Organization administrator role
Understanding of team structure and needs
Compliance requirements documentation
Team feedback on desired settings
Instructions
Define Organization Defaults
Create Team Overrides
Set Up Policies
Deploy Settings
Monitor and Iterate
See ${CLAUDE_SKILL_DIR}/references/implementation.md for detailed implementation guide.
Output
Organization-wide settings configuration
Team-specific override files
Policy documentation
Compliance reports
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-team-settings 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.
