CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

fusion-devtools

Use Fusion DevTools CLI (fdev) for API testing, token acquisition, service discovery, and person lookup during development. USE FOR: calling Fusion REST APIs, getting access tokens as JSON, discovering services and environments, resolving persons, PIM role activation. DO NOT USE FOR: modifying backend service code, deploying services, infrastructure changes, CI/CD pipeline configuration, or Service Bus operations.

72

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

86%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.

A strong, executable skill body: concrete commands throughout, a clear step sequence, and a well-signaled two-file reference bundle. The only meaningful weaknesses are minor redundancy with the frontmatter description and the absence of response-validation guidance for mutating POST calls.

Suggestions

Add a checkpoint after mutating calls (e.g. 'After -m post, inspect the response body/status with --verbose before assuming success') to close the workflow_clarity validation gap for the mutation-capable POST workflows.

Trim the 'When to use' trigger lists and 'When not to use' section — they substantially duplicate the frontmatter description's USE FOR / DO NOT USE clauses — and drop noise like '(existing command)'.

De-duplicate content shared with references/command-reference.md (environments table, --verbose/--no-cache notes, PIM safety note) so each fact lives in exactly one place.

DimensionReasoningScore

Conciseness

The body is command-first and dense — e.g. 'fdev rest <serviceKey> \'<path>\'' with concrete examples — with almost no explanation of concepts Claude already knows. Minor over-trimming candidates remain: the 12-bullet typical/implicit trigger lists and the 'When not to use' section largely duplicate the frontmatter description, and the aside '(existing command)' adds noise.

4 / 5

Actionability

Every workflow gives copy-paste-ready commands with concrete service keys, paths, and api-versions (e.g. "fdev rest people '/persons/me?api-version=3.0' -e ci"), plus the token JSON output format, the options line, and a need→command decision table. This covers the common cases fully.

5 / 5

Workflow Clarity

The Instructions section is clearly sequenced (Step 1 'fdev --version' install check with fallback guidance, Step 2 command-choice table, Step 3 --verbose debugging, Step 4 --no-cache bypass). Minor validation gap: POST/mutating examples like "fdev rest context '/contexts?api-version=1.0' -m post -b '{\"query\":\"test\"}'" include no response-verification checkpoint despite the skill stating 'This skill is mutation-capable.'

4 / 5

Progressive Disclosure

Clean split: SKILL.md holds overview workflows and safety, while 'command-reference.md — compact command cheat sheet with all options' and 'agentic-patterns.md — common agentic workflow recipes' are both verified to exist, one level deep, with descriptive one-liners and no nested references inside them.

5 / 5

Total

18

/

20

Passed

Description

92%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.

An exemplary description: concrete capabilities, an explicit USE FOR trigger list, and a DO NOT USE boundary that makes it highly distinguishable. The single weakness is trigger-term breadth — a few natural synonyms (bearer token, JWT, endpoint) would make matching even more robust.

DimensionReasoningScore

Specificity

Names the tool ('Use Fusion DevTools CLI (fdev)') and five concrete actions: 'API testing, token acquisition, service discovery, and person lookup' plus 'PIM role activation'. Every command family in the body is represented, so this matches the comprehensive-coverage anchor rather than the minor-gaps anchor below it.

5 / 5

Completeness

Explicitly answers what ('Use Fusion DevTools CLI (fdev) for API testing, token acquisition, service discovery, and person lookup') and when ('USE FOR: calling Fusion REST APIs, getting access tokens as JSON, ... PIM role activation') with concrete trigger phrases, matching the anchor for both what AND when with concrete triggers.

5 / 5

Trigger Term Quality

Contains natural phrases users would say — 'calling Fusion REST APIs', 'getting access tokens as JSON', 'discovering services and environments', 'resolving persons' — but misses common synonyms and variations like 'bearer token', 'JWT', 'endpoint testing', or a plain-language alternative to the jargon-leaning 'PIM role activation'. Good coverage, a few natural terms missing.

4 / 5

Distinctiveness Conflict Risk

Clear niche — the Fusion DevTools CLI — with distinct triggers, and an explicit exclusion list ('DO NOT USE FOR: modifying backend service code, deploying services, infrastructure changes, CI/CD pipeline configuration, or Service Bus operations') that sharply reduces the risk of triggering for adjacent CI/CD or infrastructure skills.

5 / 5

Total

19

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

Total

15

/

16

Passed

Repository

equinor/fusion-framework

Path

.agents/skills/fusion-devtools/SKILL.md

Reviewed

Table of Contents

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.