CtrlK
BlogDocsLog inGet started
Tessl Logo

fluid-pr-guide

Use when composing, writing, drafting, or reviewing a PR title, PR description, or PR body in Fluid Framework — provides title style, body template, and section guidance.

69

Quality

85%

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

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 tight, highly actionable PR-writing reference with concrete templates, an explicit CI validation hook, and well-organized sections. The only nit is a slightly long list of title examples and the lack of an explicitly numbered workflow.

DimensionReasoningScore

Conciseness

Lean and assumes Claude's competence (no explanation of what a PR is), with concrete rules and templates, but the eight title examples plus three plain examples could be trimmed somewhat without losing the style distinction.

4 / 5

Actionability

Copy-paste-ready title format templates, exact section names, explicit file paths (.github/pull_request_template.md, pr-validation.yml), and a concrete AB#<item-id> rule give fully actionable, instruction-only guidance whose examples cover the common cases.

5 / 5

Workflow Clarity

A clear implied sequence (pick title style -> fill body template -> delete unused sections -> satisfy CI) with an explicit validation checkpoint (pr-validation.yml fails if the preamble remains), though steps are not presented as a numbered workflow.

4 / 5

Progressive Disclosure

Under 50 lines with well-organized sections and no bundle files needed; references to repo files (.github/pull_request_template.md, pr-validation.yml) are one level deep and clearly signaled, matching the simple-skill top anchor.

5 / 5

Total

18

/

20

Passed

Description

83%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-scoped description with an explicit 'Use when...' trigger and concrete deliverables. It clearly answers both what and when; the only slack is slightly abstract capability verbs and a missing spelled-out 'pull request' synonym.

DimensionReasoningScore

Specificity

Lists several concrete deliverables — 'title style, body template, and section guidance' — but the actions are somewhat abstract (style/template/guidance) rather than the crisp verbs of a 5, leaving minor coverage gaps.

4 / 5

Completeness

Explicitly answers both what ('provides title style, body template, and section guidance') and when ('Use when composing, writing, drafting, or reviewing a PR title, PR description, or PR body') with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Natural phrases users would say appear — 'PR title', 'PR description', 'PR body', 'composing, writing, drafting, or reviewing' — but the spelled-out synonym 'pull request' and a few variants are missing.

4 / 5

Distinctiveness Conflict Risk

Scoping to 'Fluid Framework' gives a clear niche with specific deliverables, but PR-writing trigger terms retain minor overlap risk with a generic PR/commit skill.

4 / 5

Total

17

/

20

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
microsoft/FluidFramework
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.