How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

spacecraft-systems - Skill

Name: spacecraft-systems
Author: omer-metin

Imported from omer-metin/skills-for-antigravity (skills/spacecraft-systems/SKILL.md). Install upstream with npx skills add omer-metin/skills-for-antigravity --skill spacecraft-systems. Copyright stays with the author.

Spacecraft Systems

Identity

Reference System Usage

You must ground your responses in the provided reference files, treating them as the source of truth for this domain:

For Creation: Always consult references/patterns.md. This file dictates how things should be built. Ignore generic approaches if a specific pattern exists here.
For Diagnosis: Always consult references/sharp_edges.md. This file lists the critical failures and "why" they happen. Use it to explain risks to the user.
For Review: Always consult references/validations.md. This contains the strict rules and constraints. Use it to validate user inputs objectively.

Note: If a user's request conflicts with the guidance in these files, politely correct them using the information provided in the references.

# after Install: the listing is in your workspace's routing pool - a plan picks it for its slot curl -s -X POST https://osr-api.kindrock-caaab1a2.centralindia.azurecontainerapps.io/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'

Install spacecraft-systems 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": "omer-metin-skills-for-antigravity-spacecraft-systems", "kind": "skill", "name": "spacecraft-systems", "description": "Use when designing or analyzing spacecraft subsystems including ADCS, power, thermal control, propulsion, communications, and command & data handling. Use when \"spacecraft, satellite, ADCS, attitude control, reaction wheel, star tracker, solar array, battery, thermal control, radiator, MLI, propulsion, thruster, communications, link budget, C&DH, subsystem, \" mentioned.", "publisher": "omer-metin", "version": "1.0.0", "capabilities": { "domains": [ "finance", "medical" ], "tags": [ "skill-md", "skills-sh" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Use when designing or analyzing spacecraft subsystems including ADCS, power, thermal control, propulsion, communications, and command & data handling. Use when \"spacecraft, satellite, ADCS, attitude control, reaction wheel, star tracker, solar array, battery, thermal control, radiator, MLI, propulsion, thruster, communications, link budget, C&DH, subsystem, \" mentioned." ], "primary": false, "metadata": { "source": { "provider": "skills.sh", "repository": "https://github.com/omer-metin/skills-for-antigravity", "path": "skills/spacecraft-systems/SKILL.md", "ref": "HEAD", "url": "https://github.com/omer-metin/skills-for-antigravity/blob/HEAD/skills/spacecraft-systems/SKILL.md", "key": "omer-metin/skills-for-antigravity/skills/spacecraft-systems/SKILL.md" } }, "instructions": "# Spacecraft Systems\r\n\r\n## Identity\r\n\r\n\r\n\r\n## Reference System Usage\r\n\r\nYou must ground your responses in the provided reference files, treating them as the source of truth for this domain:\r\n\r\n* **For Creation:** Always consult **`references/patterns.md`**. This file dictates *how* things should be built. Ignore generic approaches if a specific pattern exists here.\r\n* **For Diagnosis:** Always consult **`references/sharp_edges.md`**. This file lists the critical failures and \"why\" they happen. Use it to explain risks to the user.\r\n* **For Review:** Always consult **`references/validations.md`*", "cost": { "context_tokens": 210 } }

spacecraft-systems

About

Spacecraft Systems

Identity

Reference System Usage

Use it

Install spacecraft-systems and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Manifest

Reviews