fusion-mcp

Explain what Fusion MCP is and guide users through setting it up when they need Fusion-aware MCP capabilities in Copilot workflows.

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/fusion-mcp/SKILL.md

Quality

Content

81%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is well-structured, actionable, and assumes Claude's competence, with a clear sequenced workflow that includes explicit validation and a troubleshooting feedback loop. Progressive disclosure is strong, with a README index and one-level-deep references; the only gap is one bundle file not directly signaled from the body.

Dimension	Reasoning	Score
Conciseness	Lean, terse bullets that assume Claude knows MCP/VS Code/OAuth; minor redundancy where the validation checklist appears in both step 4 and the Expected output section. Anchor 4; not 5 because that repetition means not every token earns its place.	4 / 5
Actionability	Concrete commands (initialize, tools/list, tools/call), named retrieval tools, and error-to-fix maps; copy-paste config and install links live in the verified reference files rather than inline. Anchor 4; not 5 because the body itself defers the executable config/JSON to references.	4 / 5
Workflow Clarity	Clear numbered 1–7 sequence with an explicit validation step (smell test with pass criteria), a troubleshooting feedback loop mapped to symptoms, and a verification checklist. Not a destructive/batch workflow, so the cap does not apply; fits anchor 5.	5 / 5
Progressive Disclosure	Clear overview with a README index and one-level-deep references, well-signaled inline ("see references/vscode-mcp-config.md"). Not 5 because mcp-call-snippets.md is not named or linked from the body — it is only discoverable via the README.	4 / 5
	Total	17 / 20 Passed

Description

62%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description answers what and when and targets a distinct niche, but relies on abstract phrasing and jargon ("Fusion-aware MCP capabilities") rather than concrete, natural trigger terms. Specificity is moderate — it names the domain and a couple of actions but omits the install/configure/verify verbs the body actually covers.

Suggestions

Rewrite the when clause as concrete trigger phrases, e.g. "Use when the user asks what Fusion MCP is, wants to set up or install Fusion MCP in VS Code/Copilot, or needs to verify or troubleshoot a Fusion MCP connection."

Replace jargon ("Fusion-aware MCP capabilities") with natural user language and add the verbs install/configure/verify to raise specificity.

Include the bare keyword "fusion mcp" and product-context terms ("VS Code", "Copilot") as explicit triggers to improve keyword coverage.

Dimension	Reasoning	Score
Specificity	Names the domain and two concrete actions ("Explain what Fusion MCP is", "guide users through setting it up") but is not comprehensive — install/configure/verify are absent. Anchor 3 fits; not 4 because fewer than several specific actions, not 2 because actions are concrete rather than minimal.	3 / 5
Completeness	Explicitly answers both what (explain Fusion MCP, guide setup) and when ("when they need Fusion-aware MCP capabilities in Copilot workflows"), so it clears the missing-trigger cap. Not 5 because the when clause is abstract rather than concrete trigger phrases.	4 / 5
Trigger Term Quality	Contains some natural terms ("what Fusion MCP is", "Copilot workflows") but misses common variations like "install", "configure", and "set up fusion mcp", and "Fusion-aware MCP capabilities" is jargon rather than user speech. Anchor 3; not 4 due to missing common synonyms and jargon.	3 / 5
Distinctiveness Conflict Risk	"Fusion MCP" is a clear, specific niche with minimal conflict risk, but "Copilot workflows" plus generic "MCP capabilities" leaves minor overlap with general Copilot/MCP setup skills. Anchor 4; not 5 because of that residual overlap.	4 / 5
	Total	14 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_field	'metadata' should map string keys to string values	Warning

	Total	15 / 16 Passed

Repository: equinor/fusion-framework
Path: .agents/skills/fusion-mcp/SKILL.md
Commit: 5b70066

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.