CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

88%

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

88%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 lean, highly actionable workflow: every operation has an executable command, the sequence is explicitly gated on safety checks and user confirmation, and conventions are delegated to a companion skill. The only real weaknesses are mild duplication of the origin-remote check and a body that is slightly longer than a minimal single-file skill needs.

DimensionReasoningScore

Conciseness

The body is efficient and command-focused with no explanations of concepts Claude already knows, but the origin-remote check and its test/ branch exception are stated twice (required step 2 and again as a full paragraph in 'Pushing and Creating the PR'), and the meta-sentence 'This is the only point where the fluid-pr flow asks the user a question' could be trimmed.

4 / 5

Actionability

Fully executable, copy-paste-ready commands cover the common cases: 'git remote get-url origin', 'git push -u origin <feature-branch>', 'gh pr create' with a heredoc body and --draft variant, and 'gh pr edit' with a temp-file --body-file pattern and --title update, each with only legitimate user-specific placeholders.

5 / 5

Workflow Clarity

A numbered 6-step sequence with explicit validation checkpoints (protected-branch check, origin-remote check, mandatory ask_user confirmation gate before 'gh pr create') and a clear feedback loop (step 6: on 'Edit', apply edits and re-present), matching the top anchor.

5 / 5

Progressive Disclosure

No bundle files exist and the body is organized into a required block plus two clearly scoped sections, with detailed conventions properly delegated to the clearly signaled 'fluid-pr-guide' skill; however, at roughly 75 inline lines it slightly exceeds the lean single-file ideal, keeping it just short of the top anchor.

4 / 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 description that explicitly states both capabilities and trigger conditions with concrete natural-language phrases. The main gaps are minor: it under-represents the skill's draft-PR and PR-update capabilities and uses trigger phrases generic enough to overlap with a general PR skill.

DimensionReasoningScore

Specificity

Lists several 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' — but omits capabilities the skill body covers (draft PRs, updating an existing PR's title/body), leaving minor gaps in coverage.

4 / 5

Completeness

Clearly and explicitly answers both what ('Composes a PR title and body... pushes the branch and creates the PR on GitHub') and when ('Use when creating a pull request in the Fluid Framework repo... Triggers on "create a PR", "make a PR", "open a PR"...') with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

The explicit trigger list 'create a PR, make a PR, open a PR, submit a PR, or push and create a PR' captures the main natural verb variations users say, but misses a few common phrasings such as 'draft PR', 'update a PR', or 'open a pull request' (spelled out).

4 / 5

Distinctiveness Conflict Risk

Scoping to 'the Fluid Framework repo' establishes a clear niche with low conflict risk, but the trigger phrases themselves ('create a PR', 'open a PR') are generic and would also match any general PR-creation skill, giving minor overlap risk.

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

microsoft/FluidFramework

Path

.github/skills/fluid-pr/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.