Login
equinor/fusion-skillsMIT2 files

Fusion

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.

Use this skillView repositoryView on skills.sh
Specification
Skill ID
equinor/fusion-skills/fusion
Publisher
equinor
Repository
fusion-skills
Installs
0
Files
2
License
MIT
Requires
Assumes Fusion MCP is available (`mcp_fusion_skills`). Falls back to inline install commands when unavailable.
Synced
Sep 23, 2026
How to use it

Open any RiverX project, open the Skills panel in the chat, and search for this identifier. The files are fetched from the source repository at install time.

equinor/fusion-skills/fusionInstalls these files
  • CHANGELOG.md
  • SKILL.md

What this skill tells the agent

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: apm install equinor/fusion-skills/skills/fusion-skills#^1.6.1 --target copilot

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

IntentSkillStatus
Find, install, update, remove, sync, or greenkeep skillsfusion-skillsactive
Create, author, or improve a skillfusion-skillsactive
Inspect a skill for quality issues or report a skill failurefusion-skillsactive
Create or update a GitHub issuefusion-issue-authoringactive
Solve / implement a GitHub issuefusion-issue-solvingexperimental
Plan or break down an issue into sub-tasksfusion-issue-task-planningexperimental
Address PR review commentsfusion-github-review-resolutionexperimental
Review a dependency update PRfusion-dependency-reviewexperimental

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: `` apm install equinor/fusion-skills/skills/<skill-name>#^1.6.1 --target copilot ``
  3. If the skill is experimental: add a note: "This skill is experimental and may change. Install at your own risk."
  4. 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.
  5. 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.

More from equinor

equinor/fusion-skills

Fusion Backend Dev

Guides consumption and understanding of Fusion backend services, APIs, and patterns for frontend/client developers, integrators, and architects. Shows reference implementations, explains architectural decisions, and clarifies contracts. USE FOR: understanding Fusion backend APIs, learning implementation patterns, exploring reference code, choosing the right integration point, and understanding authorization/validation/async patterns. DO NOT USE FOR: modifying backend services, creating new endpoints, database changes, or backend-specific development (use the fusion-services-developer agent or the target backend service repo instead).

equinor/fusion-skills

Fusion Code Conventions

Applies and explains code conventions across TypeScript, React, C#, and Markdown. Enforces naming rules, file naming patterns, TSDoc and XML doc standards, inline comment intent (the *why*, not the *what*), code structure, error handling, async patterns, and dead code policy. Also enforces ADR and contributor doc decisions, and flags decisions that appear stale or misaligned with current tooling. USE FOR: convention questions, code review against project standards, applying naming rules, auditing intent comments, checking TSDoc completeness, enforcing recorded ADR decisions, and flagging stale architectural decisions. DO NOT USE FOR: security vulnerability scanning, performance profiling, runtime debugging, or generating net-new code without a review target.

equinor/fusion-skills

Fusion Core Services

Guides integrations across Fusion Core service APIs from a single installable skill. USE FOR: service discovery across apps, people, context, roles, notifications, reports, tasks, and other Fusion Core APIs; cross-service integration planning; choosing the right endpoint/model guidance for a workflow. DO NOT USE FOR: modifying Fusion backend source code, non-Fusion APIs, or generic cloud architecture work without a Fusion service integration target.

Use this skill in a project

Open any RiverX project, search the Skills panel for equinor/fusion-skills/fusion, and install it in one click.

Use this skill