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.
Voxel-Game-Engine - Skill - OpenSmartRoute
Skillv1.0.0
Voxel-Game-Engine
Do not run `cargo fmt` on the whole codebase or on any file. Do not run tests unless asked to or you are fixing bugs. Tests should not be run while reviewing code. If you do run tests or other builds,
Imported from ItchyTrack/Voxel-Game-Engine (AGENTS.md). Install upstream with npx skills add ItchyTrack/Voxel-Game-Engine. Copyright stays with the author.
Do not run cargo fmt on the whole codebase or on any file.
Do not run tests unless asked to or you are fixing bugs. Tests should not be run while reviewing code.
If you do run tests or other builds, always use release as debug is not built.
Do not revert files through git unless explicitly asked to do so. Even if you were told that you did something wrong, it is not a reason to throw everything away without talking first.
Do not make design choises ever. Always ask the user what should be done.
Use it
Copy one of these into your project. Installing also returns the manifest and these snippets.
yaml
targets:
- https://api.opensmartroute.ai/api/v1/registry/itchytrack-voxel-game-engine-voxel-game-engine/manifest # or paste the manifest below
Manifest
An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.
{
"ocm": "1",
"id": "itchytrack-voxel-game-engine-voxel-game-engine",
"kind": "skill",
"name": "Voxel-Game-Engine",
"description": "Do not run `cargo fmt` on the whole codebase or on any file. Do not run tests unless asked to or you are fixing bugs. Tests should not be run while reviewing code. If you do run tests or other builds, always use release as debug is not built. Do not revert files through git unless explicitly asked to do so. Even if you were told that you did something wrong, it is not a reason to throw everything away without talking first. Do not make design choises ever. Always ask the user what should be done.",
"publisher": "ItchyTrack",
"version": "1.0.0",
"capabilities": {
"domains": [
"coding"
],
"tags": [
"skill-md",
"github-agents"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"Do not run `cargo fmt` on the whole codebase or on any file. Do not run tests unless asked to or you are fixing bugs. Tests should not be run while reviewing code. If you do run tests or other builds, always use release as debug is not built. Do not revert files through git unless explicitly asked to do so. Even if you were told that you did something wrong, it is not a reason to throw everything away without talking first. Do not make design choises ever. Always ask the user what should be done."
],
"primary": false,
"metadata": {
"source": {
"provider": "github-agents",
"repository": "https://github.com/ItchyTrack/Voxel-Game-Engine",
"path": "AGENTS.md",
"ref": "5ba06de3746a5a636ac66c39b90b6fd9fdcd2277",
"url": "https://github.com/ItchyTrack/Voxel-Game-Engine/blob/5ba06de3746a5a636ac66c39b90b6fd9fdcd2277/AGENTS.md",
"key": "ItchyTrack/Voxel-Game-Engine/AGENTS.md"
}
},
"instructions": "Do not run `cargo fmt` on the whole codebase or on any file.\nDo not run tests unless asked to or you are fixing bugs. Tests should not be run while reviewing code.\nIf you do run tests or other builds, always use release as debug is not built.\nDo not revert files through git unless explicitly asked to do so. Even if you were told that you did something wrong, it is not a reason to throw everything away without talking first.\nDo not make design choises ever. Always ask the user what should be done.",
"cost": {
"context_tokens": 125
}
}
Fetch it by URL: GET /api/v1/registry/itchytrack-voxel-game-engine-voxel-game-engine/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.
