fast-feature-request

Generate a feature request issue for the FAST repository using the provided template.

Quality

62%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.github/skills/fast-feature-request/SKILL.md

Quality

Content

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

The content is concise, actionable, and clearly scoped as a non-destructive single-task skill, scoring well on conciseness, actionability, and workflow clarity. Its main gap is structural: the body lacks section headers that would aid navigation, and the referenced template file does not exist in the bundle.

Suggestions

Add section headers (e.g. ## Template, ## Field guidance, ## Output) so the flat instruction list is easier to scan and navigate.

Verify the referenced template path ../../ISSUE_TEMPLATE/feature-request.md resolves from the skill location, or bundle the template inside the skill so the reference is real.

Reorder the steps into an explicit numbered sequence (locate template -> search for duplicates -> fill fields -> suggest title -> emit markdown block only) to make the workflow sequence unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence with no concept padding; the only redundancy is between the first two paragraphs ("only applies to..." and "only for generating..."), keeping it just below anchor 5.	4 / 5
Actionability	Guidance is concrete and executable for an instruction-only skill — explicit template path, the title format `feat: add [what] to/in [where]`, per-section field instructions, and a search-existing-issues step — but lacks a worked example of a completed request, fitting anchor 4.	4 / 5
Workflow Clarity	The skill is single-task and explicitly non-destructive ("Do not create or modify any existing Github issues"), so no validation cap applies; requirements are clear but not numbered and the search step is ordered after the section guidance, fitting anchor 4.	4 / 5
Progressive Disclosure	There is one clearly signaled one-level reference (the template markdown link) but no header/section structure — the body is a flat paragraph list — so it sits below the well-organized-with-headers bar of anchor 4.	3 / 5
	Total	15 / 20 Passed

Description

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

The description is specific and clearly conveys what the skill does for a well-bounded niche, but it lacks an explicit "Use when..." trigger clause and has limited keyword variation. Adding trigger guidance and a few natural synonyms would lift the completeness and trigger-term dimensions.

Suggestions

Append an explicit trigger clause, e.g. "Use when the user wants to file a feature request or suggest a new feature for the FAST repository."

Add natural synonyms users might say such as "suggest a feature", "propose an enhancement", or "open a feature request".

Optionally name a second concrete action (e.g. "draft and format a feature request issue") to move specificity from one action toward several.

Dimension	Reasoning	Score
Specificity	"Generate a feature request issue" names the domain and one concrete action; not several actions, so it fits anchor 3 rather than 4, and the action is concrete rather than generic so it stays above 2.	3 / 5
Completeness	It clearly states the what ("Generate a feature request issue for the FAST repository using the provided template") but has no "Use when..." trigger clause, so completeness is capped at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	"feature request issue", "template", and "FAST repository" are natural terms but coverage is limited with no synonyms or variations, matching anchor 3.	3 / 5
Distinctiveness Conflict Risk	It targets a clear niche (FAST repository feature requests) with distinct triggers, with only minor overlap risk against general issue-generation skills, fitting anchor 4.	4 / 5
	Total	13 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 1 suspicious	Warning

	Total	15 / 16 Passed

Repository: microsoft/fast
Path: .github/skills/fast-feature-request/SKILL.md
Commit: a909e87

Reviewed: about 18 hours ago

Table of Contents

Discovery Implementation Validation

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.