Skip to main content
ZICQ

Skills ZICQ category:Agent Workflows fusion-skills

Fusion Skills

Entrypoint for all Fusion skill lifecycle operations. USE FOR: finding, installing, updating, syncing, or greenkeeping skills; setting up skill automation; creating or authoring a new skill; reporting a bug with a skill. DO NOT USE FOR: resolving GitHub issues, reviewing PRs, planning task breakdowns, or authoring GitHub issues — those are handled by other Fusion skills.

1422 installs

Official URL:skills.sh

What this skill does

Intro in this page language first. The official description stays in its original wording; we do not rewrite SKILL.md.

What it does

Entrypoint for all Fusion skill lifecycle operations. USE FOR: finding, installing, updating, syncing, or greenkeeping skills; setting up skill automation; creating or authoring a new skill; reporting a bug with a skill. DO NOT USE FOR: resolving GitHub issues, reviewing PRs, planning task breakdowns, or authoring GitHub issues — those are handled by other Fusion skills.

When to use it

The official description does not include a separate “Use when”. Per the spec, agents activate this skill when the task matches keywords in that description.

How agents load it

Per Agent Skills progressive disclosure: name and description load at startup (~100 tokens); the full SKILL.md body loads when the skill activates; scripts/, references/, and assets/ load only as needed. This file's sections: Fusion Skills; Loading behavior; MCP tools; Routing; Migration from deprecated skills; Safety.

File analysis

File analysis: instruction-only skill (SKILL.md). The agent loads the full body when activated.

Fusion SkillsLoading behaviorMCP toolsRoutingMigration from deprecated skillsSafety

Compatibility:Assumes Fusion MCP is available (`mcp_fusion_skills`). Falls back to `references/skill-catalog.md` and promotes Fusion MCP when unavailable. · License:MIT

Source category:skills.sh agent-skill

SKILL.md & Agent activation

Official spec ↗
name
fusion-skills
description
Entrypoint for all Fusion skill lifecycle operations. USE FOR: finding, installing, updating, syncing, or greenkeeping skills; setting up skill automation; creating or authoring a new skill; reporting a bug with a skill. DO NOT USE FOR: resolving GitHub issues, reviewing PRs, planning task breakdowns, or authoring GitHub issues — those are handled by other Fusion skills.
compatibility
Assumes Fusion MCP is available (`mcp_fusion_skills`). Falls back to `references/skill-catalog.md` and promotes Fusion MCP when unavailable.
License
MIT
  1. DiscoverThe client exposes names and descriptions to the agent.
  2. ActivateYour request or the task context selects the skill and loads its instructions.
  3. Load resourcesReferenced scripts, documentation and assets are used when needed.

Invocation syntax and available tools depend on your Agent client. Client integration guide ↗

Install this skill

Skills CLI ↗

Choose the target agent and installation scope, keep referenced package files, then verify the skill appears in the client's catalog.

Ask your Agent to install

Copy these instructions to a compatible agent and confirm the target directory matches your client.

Install the agent skill "fusion-skills" into my project. The full SKILL.md and official description are at https://zicq.com/en/skills/skl-35997a8cbb538e16-Fusion-Skills.html
Save it as .cursor/skills/fusion-skills/SKILL.md or .claude/skills/fusion-skills/SKILL.md and keep the frontmatter name and description exactly as-is.

Full package on GitHub ↗

Install from the terminal · Skills CLI

Requires Node.js and npx. First inspect the repository's skill list to confirm the name.

npx skills add 'https://github.com/equinor/fusion-skills' --list

npx skills add 'https://github.com/equinor/fusion-skills' --skill 'fusion-skills'

The CLI lets you choose the agent interactively. The default scope is the project; use -g for user scope. Confirm package availability with the discovery command, then use npx skills list to inspect installed skills.

Readable layout

name: fusion-skills description: 'Entrypoint for all Fusion skill lifecycle operations. USE FOR: finding, installing, updating, syncing, or greenkeeping skills; setting up skill automation; creating or authoring a new skill; reporting a bug with a skill. DO NOT USE FOR: resolving GitHub issues, reviewing PRs, planning task breakdowns, or authoring GitHub issues — those are handled by other Fusion skills.' license: MIT compatibility: Assumes Fusion MCP is available (mcp_fusion_skills). Falls back to references/skill-catalog.md and promotes Fusion MCP when unavailable. metadata: version: "0.0.0" status: active owner: "@equinor/fusion-core" role: orchestrator skills: - agents/discovery.agent.md - agents/greenkeeper.agent.md - agents/author.agent.md - agents/warden.agent.md tags: - fusion - skills - discovery - install - sync - authoring - mcp - workflow - automation - triage - entrypoint mcp: suggested: - mcp_fusion_skills

Fusion Skills

Skill lifecycle entrypoint. Resolve intent, engage the right agent.

Loading behavior

Load ONLY the routed agent file. References are loaded on-demand by the agent when it needs them (e.g., skill-catalog.md only on MCP failure, sync-workflows.md only in setup mode). Do not preload all agents or all references.

MCP tools

This skill uses mcp_fusion_skills — the Fusion MCP tool that handles both skill discovery and lifecycle operations:

  • Discovery (intent: query): semantic search over the skills index by description or task.
  • Inventory (intent: inventory): list installed skills.
  • Lifecycle (intent: install | update | remove): advisory commands for managing skills.

Routing

| Intent | Agent | |--------|-------| | Find or discover the right skill; list installed skills | agents/discovery.agent.md | | Install, update, remove, or check skills; set up automation | agents/greenkeeper.agent.md | | Create, author, or improve a skill | agents/author.agent.md | | Inspect a skill for quality issues, or report a skill failure | agents/warden.agent.md |

If the user was routed here from the fusion main gate with a partially-resolved intent (e.g., "skills"), proceed directly to the most likely agent without re-asking the top-level question.

If intent is genuinely unclear and the user was not already asked a clarifying question, ask one question: "Are you looking to find a skill, install or update one, create your own, or report a problem with one?"

Compound intents: If the request spans multiple agents (e.g., "inspect this skill and fix the issues"), run agents sequentially. Pass the output of the first agent as context to the second.

Loop prevention: If you were activated from the fusion main gate, do not redirect back to fusion. Handle the request within your agents or state that it is out of scope.

Out of scope: Resolving GitHub issues, reviewing PRs, planning task breakdowns, or authoring GitHub issues. Direct the user to the relevant installed skill or the fusion main gate — but never re-route back to fusion if you were activated from there.

Migration from deprecated skills

If fusion-discover-skills or fusion-skill-self-report-bug is installed alongside this skill, tell the user:

"You have a deprecated skill installed that's now part of fusion-skills. Remove its dependency from apm.yml, then run apm prune to reconcile the lockfile and deployed files."

Safety

  • No secrets or credentials.
  • No GitHub mutations without confirmation.
  • No remote script execution.
  • No invented skill names or catalog results.
  • Installed skill files are copies (use apm.yml and apm.lock.yaml to inspect dependency provenance and deployed-file ownership) — never edit them in place directly; route content fixes through agents/author.agent.md (which redirects to fusion-skill-authoring, source repo) and failures through agents/warden.agent.md (report mode).

Related skills

Agent Workflows

Skill Creator

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that exte…

Agent Workflows

Clawdhub

Use the ClawdHub CLI to search, install, update, and publish agent skills from clawdhub.com. Use when you need to fetch new skills on the fl…

Agent Workflows

Agent Team Orchestration

Orchestrate multi-agent teams with defined roles, task lifecycles, handoff protocols, and review workflows. Use when: (1) Setting up a team …

Agent Workflows

Superpowers

Spec-first, TDD, subagent-driven software development workflow. Use when: (1) building any new feature or app — triggers brainstorm → plan →…