version: "1.0.0" name: fusion description: 'Main Copilot skill gate for the Fusion ecosystem — cross-domain router. USE FOR: routing between different Fusion domains (skills, issues, PRs, reviews) when the right domain skill is unclear; getting install guidance for missing skills. DO NOT USE FOR: skill lifecycle operations (use fusion-skills directly), tasks where a specific Fusion skill is already active.' license: MIT compatibility: Assumes Fusion MCP is available (mcp_fusion_skills). Falls back to inline install commands when unavailable. metadata: version: "0.1.0" status: active owner: "@equinor/fusion-core" role: orchestrator tags:

• fusion
• entrypoint
• gateway
• orchestrator
• triage

mcp: suggested:

• mcp_fusion_skills

Fusion

Main gate. Identify intent, route to the right Fusion skill.

Requires `fusion-skills` for skill lifecycle operations. If fusion-skills is not installed, suggest: npx -y skills add equinor/fusion-skills fusion-skills

First-contact response

If the user asks "what can you do?" or is clearly exploring for the first time, respond with a brief overview before asking clarifying questions:

"I route you to the right Fusion skill. Currently available:

- Find, install, or manage skills → fusion-skills

- Create GitHub issues → fusion-issue-authoring

- Solve issues, review PRs, plan tasks → experimental skills (ask me to check availability)

Try: 'find me a skill for...' or 'create an issue for...'"

Routing

Loop prevention

This skill is a top-level router. It must never re-route back to itself. If you arrived here from another Fusion skill, do not redirect back to that skill — answer directly or state that the intent is out of scope.

Workflow

1. Identify intent from the user's request.
2. Call mcp_fusion_skills to confirm which skill handles it and whether it is installed.

• If MCP is unavailable: use the routing table above as the sole source of truth. Do not guess or hallucinate skill names.

1. If installed: redirect the user to invoke that skill directly.
2. If not installed but available (active or experimental): name the skill, state what it does in one sentence, note if experimental, and give the install command:

`` npx -y skills add equinor/fusion-skills <skill-name> ``

1. If the skill is experimental: add a note: "This skill is experimental and may change. Install at your own risk."
2. If intent doesn't match any routing entry: say so and suggest the user describe their goal differently, or use fusion-skills discovery to search for a matching skill.
3. If intent is still unclear after reading the request, ask one conversational question:

> "Are you looking to manage skills, create an issue, work on an issue, or review a PR?"

Safety

• No secrets or credentials.
• No GitHub mutations without confirmation.
• No remote script execution.
• No invented skill names.