CtrlK
BlogDocsLog inGet started
Tessl Logo

fusion-github-review-resolution

Resolves unresolved GitHub PR review threads end-to-end: evaluates whether each review comment is correct, applies a targeted fix when valid, replies with rationale when not, commits, and resolves the thread. USE FOR: unresolved review threads, PR review feedback, changes requested PRs, PR review URLs (#pullrequestreview-...), fix the review comments, close the open threads, address PR feedback. DO NOT USE FOR: summarizing feedback without code changes, creating new PRs, or read-only branches.

78

Quality

99%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

98%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 thorough, well-sequenced mutation workflow with strong validation checkpoints and real, correctly-referenced bundle files. Its main weakness is conciseness — several sections over-explain principles Claude already knows and could be trimmed or moved to a reference.

Suggestions

Trim the Safety & constraints and reply/resolve-ordering sections to only non-obvious rules; remove restatements like 'Never resolve a thread without a reply' that already appear verbatim earlier in step 6.

Move the GraphQL cost-awareness and token-budget guidance into a separate assets/ reference file and link to it, reducing the SKILL.md body length while keeping the detail one click away.

Collapse the long 'When to use' trigger list (which duplicates the description's USE FOR terms) into a brief pointer, since the frontmatter already carries that activation guidance.

DimensionReasoningScore

Conciseness

The body is accurate and well-structured but runs long with some padded guidance that Claude could infer (e.g. 'do not assume review feedback is correct', 'never expose secrets', repeated restatements of reply/resolve ordering), so it is mostly efficient but could be tightened.

3 / 5

Actionability

Provides concrete executable commands (real script invocations with flags, GraphQL file paths, `gh api graphql -f query=@assets/...`) with copy-paste-ready examples, but a few steps remain procedural guidance rather than runnable commands.

4 / 5

Workflow Clarity

Clear phased sequence (fetch → analyze → fix → validate → push → reply → resolve → verify) with explicit validation checkpoints, re-fetch-on-error feedback loops, a working checklist document, and a destructive/batch-aware dry-run-first guard for mutations.

5 / 5

Progressive Disclosure

Good structure: SKILL.md overview points one level deep to real bundle files (scripts/*.sh, assets/*.graphql, assets/review-resolution-checklist.md) with a tooling map table; minor gaps such as several large inline sections (cost awareness, token budget) that could live in a reference file.

4 / 5

Total

16

/

20

Passed

Description

100%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 multi-step capabilities, dense natural trigger terms, explicit use/don't-use guidance, and a tight niche that minimizes conflict risk. Voice is correctly third person throughout.

DimensionReasoningScore

Specificity

Lists multiple concrete end-to-end actions — 'evaluates whether each review comment is correct, applies a targeted fix when valid, replies with rationale when not, commits, and resolves the thread' — giving comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

Explicitly answers both 'what' (resolve unresolved PR review threads end-to-end with enumerated actions) and 'when' (USE FOR triggers) and adds a DO NOT USE FOR negative boundary, matching the top anchor.

5 / 5

Trigger Term Quality

The USE FOR clause packs in natural phrases users actually say ('fix the review comments', 'close the open threads', 'address PR feedback', 'changes requested PRs') plus the technical URL anchor '#pullrequestreview-...', covering synonyms and variants comprehensively.

5 / 5

Distinctiveness Conflict Risk

The niche is narrow and specific (mutating/resolving unresolved PR review threads) with distinct trigger phrasing and explicit DO NOT USE FOR exclusions, minimizing overlap with adjacent skills.

5 / 5

Total

20

/

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.

Validation15 / 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
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.