CtrlK
BlogDocsLog inGet started
Tessl Logo

fast-pull-request

Generate a pull request description for the FAST repository using the provided template.

49

Quality

53%

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-pull-request/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%

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

This simple instruction-only skill gives clear, specific per-section guidance and avoids padding, but it lacks a sequenced workflow with a validation checkpoint, section organization, and its referenced template file is absent from the bundle. Tightening repetition and adding the template file would materially improve it.

Suggestions

Include the referenced pull_request_template.md in the skill bundle (e.g., under references/) so the link resolves and the guidance is fully actionable.

Add section headers (e.g., '## Template sections', '## Checklist rules', '## Output') to organize the monolithic prose and improve navigation.

Add a final validation step such as 'confirm the generated markdown code block mirrors the template structure before emitting it' to lift workflow clarity to 3.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence without explaining concepts Claude already knows, but the per-section optional-section guidance and 'markdown code block' restatements repeat enough that it could be tightened.

2 / 3

Actionability

Guidance is concrete with exact quoted checkbox labels and a template link, but the referenced template at ../../pull_request_template.md is not present in the skill bundle, leaving a gap in copy-paste-ready completeness.

2 / 3

Workflow Clarity

Per-section rules are clear, but the steps are presented as a list of rules rather than a sequenced workflow, and no validation checkpoint confirms the generated code block matches the template before output.

2 / 3

Progressive Disclosure

No bundle files exist and the body is under 50 lines, but it has no section headers (monolithic prose) and its sole reference target (../../pull_request_template.md) is missing from the bundle.

2 / 3

Total

8

/

12

Passed

Description

57%

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 concrete and clearly scoped to the FAST repository, but it omits any explicit trigger guidance and only names a single action, limiting specificity and completeness. Adding a 'Use when...' clause and more action terms would raise it.

Suggestions

Add an explicit 'Use when...' clause (e.g., 'Use when generating a pull request description for the FAST repository') so the trigger condition is unambiguous.

List multiple concrete actions (e.g., summarize branch changes, link related issues, fill the checklist) to lift specificity from 2 to 3.

Include common keyword variations such as 'PR' alongside 'pull request' to improve trigger term coverage.

DimensionReasoningScore

Specificity

Quotes 'Generate a pull request description' and 'for the FAST repository using the provided template' name a concrete action and domain, but only a single action is listed rather than multiple specific actions, so it falls short of 3.

2 / 3

Completeness

It states what the skill does (generate a PR description) but provides no 'Use when...' clause or equivalent trigger guidance, which per the rubric caps completeness at 2.

2 / 3

Trigger Term Quality

Includes relevant keywords like 'pull request description' and 'FAST repository', but lacks common variations (e.g., 'PR') and any natural trigger phrasing, so coverage is partial rather than complete.

2 / 3

Distinctiveness Conflict Risk

The scope is tightly bound to 'the FAST repository' with a specific provided template, giving it a clear niche unlikely to trigger for unrelated skills.

3 / 3

Total

9

/

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.