fusion
Skill2 starsChanged 2 months agoMITView on GitHub
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.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- TheOnlyFusionCube/devin-plugin-cctheir own version, first seen Oct 23, 2026
- krisrice/oracle-db-skillstheir own version, first seen Oct 8, 2026
- Zhh9126/oracle-skillstheir own version, first seen Aug 10, 2026
- noahcalibuso/herdr-fusiontheir own version, first seen Jul 23, 2026
- oracle/skillstheir own version, first seen Mar 9, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- krisrice/oracle-db-skills★ 918same name
- oracle/skills★ 918same name
- Zhh9126/oracle-skills★ 4same name
- TheOnlyFusionCube/devin-plugin-cc★ 2same name
- noahcalibuso/herdr-fusion★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository31 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .github/copilot-instructions.mdCopilot instructions
- caveman-compressSkill
- fusion-core-servicesSkill
- fusion-dependency-reviewSkill
- fusion-designSkill
- fusion-framework-mockingSkill
- fusion-framework-testingSkill
- fusion-github-review-resolutionSkill
- fusion-issue-solvingSkill
- fusion-issue-task-planningSkill
- fusion-mcpSkill
- fusion-package-scribeSkill
- fusion-pm-mcpSkill
- fusion-backend-devSkill
- fusion-developer-appSkill
- fusion-developer-portalSkill
- fusion-devtoolsSkill
- fusion-help-apiSkill
- fusion-help-docsSkill
- fusion-help-integrationSkill
- fusion-infra-cliSkill
- fusion-issue-authoringSkill
- fusion-roles-cliSkill
- fusion-rulesSkill
- fusion-skill-authoringSkill
- fusion-skillsSkill
- equinor-design-systemSkill
- fusion-code-conventionsSkill
- fusion-researchSkill
- fusion-rule-authorSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 8 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 30
If the user asks "what can you do?" or is clearly exploring for the first time, respond with a brief overview before asking clarifying …
- Very specific: line 59
Call mcp_fusion_skills to confirm which skill handles it and whether it is installed.
- Distinctive: line 60
If MCP is unavailable: use the routing table above as the sole source of truth.
- Distinctive: line 66
If the skill is experimental: add a note: "This skill is experimental and may change.
- Distinctive: line 68
If intent is still unclear after reading the request, ask one conversational question:
- Distinctive: line 73
No secrets or credentials.
- Distinctive: line 74
No GitHub mutations without confirmation.
- Distinctive: line 75
No remote script execution.
- Distinctive: line 76
No invented skill names.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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
| 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
- Identify intent from the user's request.
- Call
mcp_fusion_skillsto 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.
- If installed: redirect the user to invoke that skill directly.
- 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 - If the skill is experimental: add a note: "This skill is experimental and may change. Install at your own risk."
- If intent doesn't match any routing entry: say so and suggest the user describe their goal differently, or use
fusion-skillsdiscovery to search for a matching skill. - 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.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.