CtrlK
BlogDocsLog inGet started
Tessl Logo

fuzzlyn-triage

Triage Fuzzlyn CI runs.

59

Quality

67%

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

Fix and improve this skill with Tessl

tessl review fix ./.github/skills/fuzzlyn-triage/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%Weight 40%Scale 1-3

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

The content is a highly actionable, well-sequenced triage procedure with concrete commands and explicit validation checkpoints, scoring high on actionability and workflow clarity. Its main weakness is progressive disclosure: everything lives inline in one file with no quick-start overview or offloaded reference material.

Suggestions

Add a brief overview or quick-start section at the top that summarizes the end-to-end flow before the detailed steps.

Consider moving the lengthy per-example recipe (jitdump analysis, issue.md template) into a reference file to reduce the inline footprint and aid navigation.

Tighten the repeated payload-host-selection guidance into a single statement to improve conciseness.

DimensionReasoningScore

Conciseness

The body is dense, instruction-focused, and avoids explaining known concepts, but repeats some guidance (e.g., payload-host selection stated twice) and could be tightened further.

2 / 3

Actionability

It provides concrete, largely copy-paste-ready commands (runfo, superpmi.exe, mcs.exe) with explicit argument placeholders, exact file-naming conventions, and named output artifacts.

3 / 3

Workflow Clarity

A clearly ordered two-level sequence with emphatic ordering constraints ("Do NOT parallelize", "must be completed in order"), an explicit validation checkpoint ("reproduces the assertion failure instantly"), and a replay-until-reproduction feedback loop.

3 / 3

Progressive Disclosure

The single ~80-line SKILL.md is well-organized into clear numbered sections with no nested references, but it is monolithic with no overview/reference split and no external bundle files to offload detail into.

2 / 3

Total

10

/

12

Passed

Description

57%Weight 40%Scale 1-3

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 to a named project and clearly distinguishable, but it is minimal: it names one action and omits any explicit "when to use" trigger guidance. It reads more as a terse label than a complete trigger-rich description.

Suggestions

Add an explicit "Use when..." clause, e.g. "Use when triaging Fuzzlyn CI runs with JIT assertion failures."

List multiple concrete actions (e.g., reproduce failures with superpmi, extract repro contexts, analyze jitdumps, draft GitHub issues) to raise specificity.

Broaden trigger terms to natural variations a user might say, such as "JIT assertion failures," "reduced examples," or "CI failures."

DimensionReasoningScore

Specificity

"Triage Fuzzlyn CI runs." names a concrete domain and a single action (triage), but lists only one action rather than multiple specific concrete actions.

2 / 3

Completeness

The description states what to do (triage Fuzzlyn CI runs) but provides no "Use when..." or equivalent explicit trigger guidance, which caps completeness at 2 per the rubric guidelines.

2 / 3

Trigger Term Quality

"Triage Fuzzlyn CI runs." includes genuine domain keywords (Fuzzlyn, CI runs, triage) but lacks common variations or broader trigger phrasings a user might say.

2 / 3

Distinctiveness Conflict Risk

"Fuzzlyn" is a specific named project, giving the skill a clear niche with distinct triggers that are unlikely to conflict with other skills.

3 / 3

Total

9

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
dotnet/runtime
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.