Name: fluid-pr
Rating: 75.2 (1 reviews)
Author: microsoft

fluid-pr

Use when creating a pull request in the Fluid Framework repo. Composes a PR title and body following Fluid Framework conventions, proposes them to the user, then pushes the branch and creates the PR on GitHub. Triggers on "create a PR", "make a PR", "open a PR", "submit a PR", or "push and create a PR".

Quality

92%

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

Quality

Content

85%

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

The body is highly actionable with a clear, validated multi-step workflow and sensible delegation of conventions to a separate guide skill. Its main weakness is redundancy: the prose section repeats the origin check and AskUserQuestion guidance already specified in the <required> block.

Suggestions

Remove the redundant origin-check re-statement in the 'Pushing and Creating the PR' section — step 2 already mandates it; keep only the command 'git remote get-url origin' with a one-line 'stop if it points to microsoft/FluidFramework' reminder.

Drop the re-description of the AskUserQuestion flow in the prose section ('compose the title and body, print them as text, then use the AskUserQuestion tool with the four options as described in step 5') since step 5 already specifies it verbatim.

Consolidate the push/create command examples so the draft variant is shown as a single --draft flag addition rather than repeating the full gh pr create block, reducing token cost.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and assumes Claude's competence, but the 'Pushing and Creating the PR' section re-states the origin check from step 2 and re-describes the AskUserQuestion flow from step 5, so it could be tightened.	2 / 3
Actionability	Provides fully executable commands — 'git remote get-url origin', 'git push -u origin <feature-branch>', 'gh pr create --title ... --body ...' with the --draft variant — copy-paste ready with clearly marked placeholders.	3 / 3
Workflow Clarity	A clearly sequenced 6-step process with explicit validation checkpoints (stop if on main/release branch; stop if origin points to the main repo), a confirmation gate before 'gh pr create', and an Edit feedback loop returning to step 5.	3 / 3
Progressive Disclosure	Keeps the workflow inline and delegates title conventions, body template, and section guidance to the well-signaled one-level-deep 'fluid-pr-guide' skill ('Load the fluid-pr-guide skill NOW... It contains...'), splitting content appropriately. No bundle files exist to verify against.	3 / 3
	Total	11 / 12 Passed

Description

100%

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, complete, and well-scoped: it states concrete actions, explicit 'Use when' triggers with natural phrasings, and a clear Fluid Framework niche that minimizes conflict risk. It is a strong, concise description.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Composes a PR title and body following Fluid Framework conventions, proposes them to the user, then pushes the branch and creates the PR on GitHub' — matching the top anchor for specific concrete actions.	3 / 3
Completeness	Explicitly answers both what (compose title/body, propose, push, create PR) and when ('Use when creating a pull request in the Fluid Framework repo' plus explicit trigger terms), matching the top anchor.	3 / 3
Trigger Term Quality	Provides good coverage of natural phrases a user would say — 'create a PR', 'make a PR', 'open a PR', 'submit a PR', or 'push and create a PR' — matching the top anchor for natural-term coverage.	3 / 3
Distinctiveness Conflict Risk	Scoped to 'the Fluid Framework repo' with repo-specific conventions and distinct PR-creation triggers, giving it a clear niche unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: microsoft/FluidFramework
Path: .claude/skills/fluid-pr/SKILL.md
Commit: f9f2007

Reviewed: about 8 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.