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.
container-test - Skill - OpenSmartRoute
Skillv1.0.0
container-test
container-test.yaml rules: follow the JSON schema in testhelpers/container-test-schema.json, prefer real port/HTTP/file assertions, never weaken tests to make them pass.
MUST follow the schema at testhelpers/container-test-schema.json.
Keep the # yaml-language-server: $schema=... header used by sibling apps so editors validate live.
Real assertions
Tests MUST exercise actual runtime behavior: open TCP ports declared in settings.yaml, HTTP probes where applicable, file/process existence.
Do NOT weaken or remove assertions to make a failing build pass. Fix the real defect (Dockerfile, start.sh, defaults) instead.
Timeouts
Use a timeoutSeconds value reasonable for the app's startup (look at sibling apps of the same family).
Coverage minimum
Every port listed in settings.yaml SHOULD have a corresponding tcp (or higher-level) probe here.
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/trueforge-org-containerforge-container-test-instructions/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": "trueforge-org-containerforge-container-test-instructions",
"kind": "skill",
"name": "container-test",
"description": "container-test.yaml rules: follow the JSON schema in testhelpers/container-test-schema.json, prefer real port/HTTP/file assertions, never weaken tests to make them pass.",
"publisher": "trueforge-org",
"version": "1.0.0",
"capabilities": {
"domains": [
"coding"
],
"tags": [
"skill-md",
"github-instructions"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"container-test.yaml rules: follow the JSON schema in testhelpers/container-test-schema.json, prefer real port/HTTP/file assertions, never weaken tests to make them pass."
],
"primary": false,
"metadata": {
"source": {
"provider": "github-instructions",
"repository": "https://github.com/trueforge-org/containerforge",
"path": ".github/instructions/container-test.instructions.md",
"ref": "3c28cd1fac27667e9bf96dede62d9a74b111df0b",
"url": "https://github.com/trueforge-org/containerforge/blob/3c28cd1fac27667e9bf96dede62d9a74b111df0b/.github/instructions/container-test.instructions.md",
"key": "trueforge-org/containerforge/.github/instructions/container-test.instructions.md"
},
"applies_to": "apps/**/container-test.yaml"
},
"instructions": "# container-test.yaml Rules (apps/**/container-test.yaml)\n\n## Schema\n\n- MUST follow the schema at `testhelpers/container-test-schema.json`.\n- Keep the `# yaml-language-server: $schema=...` header used by sibling apps so editors validate live.\n\n## Real assertions\n\n- Tests MUST exercise actual runtime behavior: open TCP ports declared in `settings.yaml`, HTTP probes where applicable, file/process existence.\n- Do NOT weaken or remove assertions to make a failing build pass. Fix the real defect (Dockerfile, start.sh, defaults) instead.\n\n## Timeouts\n\n- Use a `timeoutSeconds` value reasonable for th",
"cost": {
"context_tokens": 195
}
}
Fetch it by URL: GET /api/v1/registry/trueforge-org-containerforge-container-test-instructions/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.