CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

87%

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

The canonical home for this skill is fluid-pr-guide in microsoft/FluidFramework

SKILL.md
Quality
Evals
Security

Quality

Content

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

An efficient, highly actionable skill body covering both title and body guidance with concrete examples and real CI constraints. Minor gaps — unspecified wiki links, no final pre-submit checklist, and slightly inconsistent section headers — keep several dimensions at 4 rather than 5.

Suggestions

Specify the wiki URL (or state that it is found in the PR template) in the '## Breaking Changes' and '## Reviewer Guidance' notes so the 'Link the wiki page' instruction is fully executable.

Add a '## PR Title Style' header to the opening section and use a single heading level consistently (the body currently starts unlabeled and uses an H1 mid-document).

End with a short pre-submit checklist (title style matches package rules, template preamble removed, empty sections deleted, AB# items referenced) as an explicit validation checkpoint.

DimensionReasoningScore

Conciseness

Lean and efficient: rules and examples only ('Do not mix the two styles', 'Never use the `[bump]` prefix — that is reserved for automated bot PRs'), with no explanation of concepts Claude already knows and every line carrying project-specific information.

5 / 5

Actionability

Highly concrete — exact title formats, eight real example titles, exact file paths ('.github/pull_request_template.md', '.github/workflows/pr-validation.yml'), and the quoted preamble line to remove — but 'Link the wiki page' and 'Always include the wiki link line' never specify which wiki page or URL, a minor gap that keeps it below fully executable.

4 / 5

Workflow Clarity

The sequence (choose title style per package rules → write title → fill template → delete inapplicable sections → remove preamble) is clear, and the CI requirement ('Leaving it in will cause the .github/workflows/pr-validation.yml check to fail') acts as a checkpoint, but there is no explicit final pre-submit verification step — a minor validation gap.

4 / 5

Progressive Disclosure

Good structure with content appropriately inline for an under-50-line skill and clearly signaled repo references (build-tools README, PR template, pr-validation workflow), but the opening title-style section has no header and heading levels are inconsistent ('# PR Body Template' vs '## Notes on body sections') — minor organization gaps.

4 / 5

Total

17

/

20

Passed

Description

87%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 description: it explicitly states what the skill provides and when to use it, with natural trigger phrases and project-specific scoping that keeps conflict risk low. The only notable gap is that 'pull request' is never spelled out alongside 'PR'.

DimensionReasoningScore

Specificity

Names the domain (PR title/description/body in Fluid Framework) and lists several concrete deliverables — 'provides title style, body template, and section guidance' — with minor gaps in coverage, fitting the 'several specific actions' anchor better than the comprehensive level above.

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 in Fluid Framework') with concrete trigger phrases, matching the anchor-5 structure.

5 / 5

Trigger Term Quality

Good keyword coverage with synonyms for the action ('composing, writing, drafting, or reviewing') and the artifact ('PR title, PR description, or PR body'), but 'pull request' is never spelled out, so a few natural terms are missing.

4 / 5

Distinctiveness Conflict Risk

The 'in Fluid Framework' qualifier establishes a clear niche with distinct triggers (PR title/description/body in that project), giving minimal conflict risk with generic or unrelated skills.

5 / 5

Total

18

/

20

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 suspicious

Warning

Total

15

/

16

Passed

Repository

microsoft/FluidFramework

Path

.github/skills/fluid-pr-guide/SKILL.md

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.