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.
testing - Skill - OpenSmartRoute
Skillv1.0.0
testing
Use for XCTest targets, DVR, and CI config secrets in contentstack-swift.
Imported from contentstack/contentstack-swift (skills/testing/SKILL.md). Install upstream with npx skills add contentstack/contentstack-swift --skill testing. Copyright stays with the author.
Testing – contentstack-swift
When to use
Adding or fixing tests under Tests/
Debugging CI-only failures that need Tests/config.json
Instructions
XCTest
Tests target ContentstackTests in Package.swift; run via swift test or Xcode schemes.
CI secrets
Workflow may generate Tests/config.json from GitHub secrets—do not commit real stack credentials; mirror structure locally for integration runs only.
HTTP recording
DVR (dev dependency) may be used for recorded sessions—keep cassettes maintainable and free of secrets.
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 testing 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": "contentstack-contentstack-swift-testing",
"kind": "skill",
"name": "testing",
"description": "Use for XCTest targets, DVR, and CI config secrets in contentstack-swift.",
"publisher": "contentstack",
"version": "1.0.0",
"capabilities": {
"domains": [
"coding"
],
"tags": [
"skill-md",
"github"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"Use for XCTest targets, DVR, and CI config secrets in contentstack-swift."
],
"primary": false,
"metadata": {
"source": {
"provider": "github",
"repository": "https://github.com/contentstack/contentstack-swift",
"path": "skills/testing/SKILL.md",
"ref": "6f3406b50b5ec5570cd51b53b7c80ec79ddb524f",
"url": "https://github.com/contentstack/contentstack-swift/blob/6f3406b50b5ec5570cd51b53b7c80ec79ddb524f/skills/testing/SKILL.md",
"key": "contentstack/contentstack-swift/skills/testing/SKILL.md"
}
},
"instructions": "# Testing – contentstack-swift\n\n## When to use\n\n- Adding or fixing tests under `Tests/`\n- Debugging CI-only failures that need `Tests/config.json`\n\n## Instructions\n\n### XCTest\n\n- Tests target **`ContentstackTests`** in `Package.swift`; run via `swift test` or Xcode schemes.\n\n### CI secrets\n\n- Workflow may generate **`Tests/config.json`** from GitHub secrets—do not commit real stack credentials; mirror structure locally for integration runs only.\n\n### HTTP recording\n\n- **DVR** (dev dependency) may be used for recorded sessions—keep cassettes maintainable and free of secrets.",
"cost": {
"context_tokens": 145
}
}
Fetch it by URL: GET /api/v1/registry/contentstack-contentstack-swift-testing/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.