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.
tests - Skill - OpenSmartRoute
Skillv1.0.0
tests
Conventions for defining tests. Use when the user wants to create or modify tests, including test structure, naming conventions, and best practices.
Imported from djaiss/jacques (.claude/skills/tests/SKILL.md). Install upstream with npx skills add djaiss/jacques --skill tests. Copyright stays with the author.
Tests
You MUST read and follow the testing rules in .claude/rules/testing.md.
You MUST use use PHPUnit\Framework\Attributes\Test; and #[Test] for test
methods, instead of public function testX().
Test method names MUST be descriptive and use snake_case, like
it_can_list_the_api_keys_of_the_current_user.
You MUST not test sanitization (i.e. TextSanitizer).
You MUST not test casts (Model casting).
You MUST test blade components: one file per component under
tests/Feature/Views/Components, rendered with $this->blade(...). See the
view tests section of .claude/rules/testing.md.
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 slot
curl -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.
djaiss-jacques-tests.ocm.jsonjson
{
"ocm": "1",
"id": "djaiss-jacques-tests",
"kind": "skill",
"name": "tests",
"description": "Conventions for defining tests. Use when the user wants to create or modify tests, including test structure, naming conventions, and best practices.",
"publisher": "djaiss",
"version": "1.0.0",
"capabilities": {
"domains": [
"coding"
],
"tags": [
"skill-md",
"github"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"Conventions for defining tests. Use when the user wants to create or modify tests, including test structure, naming conventions, and best practices."
],
"primary": false,
"metadata": {
"source": {
"provider": "github",
"repository": "https://github.com/djaiss/jacques",
"path": ".claude/skills/tests/SKILL.md",
"ref": "485c1e5cbb6f8b53491ad58e1314c9a883aa53fd",
"url": "https://github.com/djaiss/jacques/blob/485c1e5cbb6f8b53491ad58e1314c9a883aa53fd/.claude/skills/tests/SKILL.md",
"key": "djaiss/jacques/.claude/skills/tests/SKILL.md"
}
},
"instructions": "# Tests\n\n- You MUST read and follow the testing rules in `.claude/rules/testing.md`.\n- You MUST use `use PHPUnit\\Framework\\Attributes\\Test;` and `#[Test]` for test\n methods, instead of `public function testX()`.\n- Test method names MUST be descriptive and use `snake_case`, like\n `it_can_list_the_api_keys_of_the_current_user`.\n- You MUST not test sanitization (i.e. `TextSanitizer`).\n- You MUST not test casts (Model casting).\n- You MUST test blade components: one file per component under\n `tests/Feature/Views/Components`, rendered with `$this->blade(...)`. See the\n view tests section of `.cl",
"cost": {
"context_tokens": 155
}
}
Fetch it by URL: GET /api/v1/registry/djaiss-jacques-tests/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.
