CtrlK
BlogDocsLog inGet started
Tessl Logo

custom-code-review

Routes Fusion Framework pull request reviews through the repository canonical review policy. USE FOR: review this PR, review these changes, Copilot code review, inspect a pull request diff. DO NOT USE FOR: dependency update PRs, resolving existing review comments, implementing fixes, or repository-wide audits.

70

Quality

86%

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

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 focused, efficient instruction skill with clear sequencing, routing gates, and appropriate safety constraints. It could add an explicit validation/recovery checkpoint and slightly more concrete command guidance to reach full marks.

Suggestions

Add an explicit validation/recovery checkpoint (e.g., how to confirm the canonical policy was correctly applied) to strengthen the workflow feedback loop.

Specify one or two concrete commands or tool invocations for loading the canonical instruction files to make the guidance more copy-paste ready.

Consider folding the 'Typical requests' examples into the description's USE FOR list to reduce slight redundancy with the frontmatter.

DimensionReasoningScore

Conciseness

Lean, well-organized body with no concept padding and no over-explanation of PR review basics; nearly every token earns its place.

5 / 5

Actionability

Provides concrete, executable routing to specific instruction files and classification gates; appropriate for an instruction-only skill, with minor gaps in specifying exact commands.

4 / 5

Workflow Clarity

Clear sequenced instructions with a classification gate and explicit no-findings handling; lacks explicit validation/recovery checkpoints, but the skill is read-only so the destructive cap does not apply.

4 / 5

Progressive Disclosure

Well-organized sections under 50 lines with clearly signaled, one-level-deep references to canonical instruction files; no bundle files exist, and the simple-skill exception supports a high score.

5 / 5

Total

18

/

20

Passed

Description

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

A strong, well-structured description that clearly communicates purpose, triggers, and boundaries in a domain-specific niche. Minor room for additional action and synonym coverage, but it is concise and highly actionable.

DimensionReasoningScore

Specificity

Names the Fusion Framework PR-review domain and lists several concrete USE FOR / DO NOT USE FOR actions, with minor gaps in coverage versus a fully comprehensive action list.

4 / 5

Completeness

Explicitly states what it does ('Routes ... through the repository canonical review policy') and when to use it via concrete USE FOR trigger phrases, satisfying both halves.

5 / 5

Trigger Term Quality

Includes natural phrases a user would say ('review this PR', 'review these changes', 'Copilot code review', 'inspect a pull request diff') with synonyms, missing only a few common variants.

4 / 5

Distinctiveness Conflict Risk

Scoped to a niche (Fusion Framework) with explicit DO NOT USE FOR boundaries that route adjacent cases to sibling skills, giving minimal conflict risk.

5 / 5

Total

18

/

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.