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 Vlux-Entertainment/VluxyBuildingTools (AGENTS.md). Install upstream with npx skills add Vlux-Entertainment/VluxyBuildingTools. Copyright stays with the author.
AGENTS.md
Repo rules are in CLAUDE.md; read it first.
Usage
Usage is limited, so work lean: read only the parts of files you need, batch Studio reads into one
execute_luau call, take screenshots only when the job needs them, at most 2 build-and-check rounds,
npm run verify once at the end. In a sandbox verify may print SKIP for tools it can't find and still
say "green": report every SKIP as not checked. Don't touch git; Claude commits.
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 VluxyBuildingTools 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": "vlux-entertainment-vluxybuildingtools-vluxybuildingtools",
"kind": "skill",
"name": "VluxyBuildingTools",
"description": "Repo rules are in `CLAUDE.md`; read it first.",
"publisher": "Vlux-Entertainment",
"version": "1.0.0",
"capabilities": {
"domains": [
"coding"
],
"tags": [
"skill-md",
"github-agents"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"Repo rules are in `CLAUDE.md`; read it first."
],
"primary": false,
"metadata": {
"source": {
"provider": "github-agents",
"repository": "https://github.com/Vlux-Entertainment/VluxyBuildingTools",
"path": "AGENTS.md",
"ref": "83323f0f6a7e3361db05939acdfa9f1b9d4e8be7",
"url": "https://github.com/Vlux-Entertainment/VluxyBuildingTools/blob/83323f0f6a7e3361db05939acdfa9f1b9d4e8be7/AGENTS.md",
"key": "Vlux-Entertainment/VluxyBuildingTools/AGENTS.md"
}
},
"instructions": "# AGENTS.md\n\nRepo rules are in `CLAUDE.md`; read it first.\n\n## Usage\n\nUsage is limited, so work lean: read only the parts of files you need, batch Studio reads into one\n`execute_luau` call, take screenshots only when the job needs them, at most 2 build-and-check rounds,\n`npm run verify` once at the end. In a sandbox verify may print SKIP for tools it can't find and still\nsay \"green\": report every SKIP as not checked. Don't touch git; Claude commits.",
"cost": {
"context_tokens": 113
}
}
Fetch it by URL: GET /api/v1/registry/vlux-entertainment-vluxybuildingtools-vluxybuildingtools/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.