equinor/fusion-skills

fusion

Main Copilot skill gate for the Fusion ecosystem — cross-domain router.

Trending #6700 First seen Mar 23, 2026

Installation

$ npx skills add equinor/fusion-skills --skill fusion

Summary

  • 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.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from equinor/fusion-skills · top by installs.

npx skills add equinor/fusion-skills

Browse all from equinor/fusion-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 1
License LICENSE
Default branch main
Open issues 2
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Version0.1.1
LicenseMIT
CompatibilityAssumes Fusion MCP is available (`mcp_fusion_skills`). Falls back to inline install commands when unavailable.
Declared agents github-copilot
More metadata
version
0.1.1
status
active
owner
@equinor/fusion-core
role
orchestrator
tags
["fusion","entrypoint","gateway","orchestrator","triage"]
mcp
{"suggested":["mcp_fusion_skills"]}

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 3,741 B
  • docs SUMMARY.md 378 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 979 installs

SKILL.md

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 skillsfusion-skills
- Create GitHub issuesfusion-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

Intent Skill Status
Find, install, update, remove, sync, or greenkeep skills fusion-skills active
Create, author, or improve a skill fusion-skills active
Inspect a skill for quality issues or report a skill failure fusion-skills active
Create or update a GitHub issue fusion-issue-authoring active
Solve / implement a GitHub issue fusion-issue-solving experimental
Plan or break down an issue into sub-tasks fusion-issue-task-planning experimental
Address PR review comments fusion-github-review-resolution experimental
Review a dependency update PR fusion-dependency-review experimental

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 mcpfusionskills 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 ``

  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.