CtrlK
BlogDocsLog inGet started
Tessl Logo

fast-bug-report

Generate a bug report issue for the FAST repository using the provided template.

63

Quality

75%

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

Fix and improve this skill with Tessl

tessl review fix ./.github/skills/fast-bug-report/SKILL.md
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 body is a tight, well-organized instruction set for a single task with concrete per-section guidance and a clear output contract. It appropriately trusts Claude's competence and avoids padding.

DimensionReasoningScore

Conciseness

The body is lean with no concept explanations Claude already knows (e.g. it never explains what a bug report is) and each section instruction earns its place, matching the score-3 anchor ('Lean and efficient; assumes Claude's competence; every token earns its place').

3 / 3

Actionability

Concrete, specific guidance is given per template section plus an explicit title format "fix: [what is the issue?] in [where is the issue?]" and the directive "Provide the markdown code block only, without any additional commentary or explanation"; per scoring_notes, instruction-only skills are not penalized for lacking code when guidance is this actionable.

3 / 3

Workflow Clarity

This is a simple single-purpose skill (under 50 lines) with an unambiguous sequence (gather context, fill template sections, search for dupes, suggest title, emit markdown only) and no destructive/batch operation, so per scoring_notes workflow clarity scores 3 when the single action is clear.

3 / 3

Progressive Disclosure

The skill is under 50 lines with no need for external references beyond one clearly signaled, one-level-deep template link ([../../ISSUE_TEMPLATE/bug-report.md]) and well-organized flat sections, which per scoring_notes earns a 3 for simple skills.

3 / 3

Total

12

/

12

Passed

Description

50%

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 clearly conveys the skill's single purpose but is a single sentence with no explicit use-when trigger and limited keyword coverage. It is competent yet leaves the 'when to use it' implicit.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when the user asks to report a bug or file an issue against the FAST repository.'

Broaden trigger terms to natural variations users might say: 'report a bug', 'file a bug report', 'open an issue', 'FAST bug'.

Mention the concrete output (a filled bug-report markdown block) to sharpen the 'what' and reduce overlap with generic issue skills.

DimensionReasoningScore

Specificity

Quotes "Generate a bug report issue for the FAST repository using the provided template" name a single concrete action and domain, matching the score-2 anchor ('Names domain and some actions, but not comprehensive') rather than score 3 which requires multiple specific actions.

2 / 3

Completeness

The description states a clear 'what' (generate a bug report issue) but lacks any explicit 'Use when...' trigger, so per the judging guideline a missing trigger clause caps completeness at 2 rather than 3.

2 / 3

Trigger Term Quality

Phrases like "bug report issue" and "FAST repository" are natural, but coverage is thin with no common variations such as 'report a bug' or 'file an issue', matching score 2 ('Some relevant keywords but missing common variations') rather than the broad coverage of score 3.

2 / 3

Distinctiveness Conflict Risk

Scoping to "bug report" plus "FAST repository" gives a recognizable niche, but without distinct trigger phrasing it could still overlap with other issue-generation skills, matching score 2 ('Somewhat specific but could still overlap with similar skills').

2 / 3

Total

8

/

12

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

relative_links

Relative link issues: 1 suspicious

Warning

Total

15

/

16

Passed

Repository
microsoft/fast
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.