CtrlK
BlogDocsLog inGet started
Tessl Logo

fusion-issue-authoring

Classify issue type, activate the matching agent mode for type-specific drafting, and enforce shared safety gates before GitHub mutation.

68

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

The skill body is a well-structured, lean, and highly actionable workflow with explicit sequencing, validation checkpoints, and clean one-level-deep references to verified bundle files.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — it never explains what GitHub, issues, or MCP are — and uses terse directive bullets where every token largely earns its place, matching the lean-and-efficient anchor.

3 / 3

Actionability

Concrete MCP tool names, an ordered mutation sequence, specific payload fields, and explicit cache paths are given; per the rubric's instruction-only note, absence of code blocks is not penalized when guidance is this actionable.

3 / 3

Workflow Clarity

An explicit 8-step sequenced workflow (classify → resolve repo → dedupe → draft → review → gates → mutate → validate) includes confirmation checkpoints, rate-limit handling, and retry-after feedback loops matching the clear-sequence-with-validation anchor.

3 / 3

Progressive Disclosure

The body is an overview pointing one level deep to real, verified files (references/questions.md, instructions.md, mcp-server.md, and issue-template assets) with clear 'Use detailed ... in references/...' signals and no nested references.

3 / 3

Total

12

/

12

Passed

Description

67%

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 is specific and well-scoped to a distinct GitHub issue-authoring niche, but it omits any explicit 'when to use' trigger guidance and lacks natural user-facing trigger terms, which cap completeness and trigger-term quality.

Suggestions

Append a 'Use when ...' clause with natural triggers such as 'create an issue', 'draft a ticket', or 'turn this into a GitHub issue' to lift completeness and trigger-term quality.

Add a couple of common user phrasings (e.g. 'GitHub issue', 'draft a ticket') directly in the description so it matches language users actually say.

DimensionReasoningScore

Specificity

Three concrete actions are named: 'Classify issue type', 'activate the matching agent mode for type-specific drafting', and 'enforce shared safety gates before GitHub mutation', matching the multiple-specific-actions anchor rather than the domain-only level 2.

3 / 3

Completeness

It clearly answers 'what' (classify, activate, enforce gates) but provides no 'Use when...' or equivalent trigger guidance, which per the rubric caps completeness at 2 rather than 1 because the 'what' is strong.

2 / 3

Trigger Term Quality

The domain keywords 'GitHub' and 'issue type' are present, but there are no natural user-facing trigger phrases (e.g. 'create an issue', 'draft a ticket') in the description field; those live only in the body, so it is not level 3.

2 / 3

Distinctiveness Conflict Risk

The niche is specific and unlikely to misfire ('GitHub mutation', 'issue type', 'agent mode', 'safety gates'), giving it a clear distinct trigger space compared to the overlap-prone level-2 anchor.

3 / 3

Total

10

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

referenced_paths_exist

Referenced path issues: 1 missing, 4 deeper-than-1-level

Warning

Total

14

/

16

Passed

Repository
equinor/fusion-framework
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.