CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

mflux-pr-docs

Write the PR body for the current mflux branch and show it to the developer for approval. Fills the What section, the release-note block and the Verification section of the PR template. Use when the developer asks to write, fill or update a PR description or a release note.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

92%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 excellent single-purpose workflow skill: fully executable commands, explicit validation feedback loops, an approval gate, and disciplined conciseness. The only material weakness is progressive disclosure — the core writing guidance is delegated to two prompt files that are not present in the bundle.

Suggestions

Add the referenced pr-what-prompt.md and release-note-prompt.md to the bundle (e.g. in references/) so the 'Obey ... in this folder' instructions resolve to real files.

If the two prompt files cannot be bundled, inline their essential rules into SKILL.md and drop the dangling references.

State the expected location of the referenced files precisely (e.g. references/pr-what-prompt.md instead of 'in this folder') so discovery does not depend on folder layout.

DimensionReasoningScore

Conciseness

Lean and imperative throughout — every step is an instruction ("Copy .github/pull_request_template.md to tmp-PR-content.md", "Do not tick the boxes") with zero explanation of concepts Claude already knows. The few rationale lines ("Backticks and `$` in a typed title run as shell code") are safety-critical, not padding, matching the 5 anchor exactly.

5 / 5

Actionability

Fully executable: exact git/gh commands, a runnable Python heredoc CI check, and a copy-paste shell block for title extraction and PR creation, covering both open and not-open PR branches. Matches the 5 anchor — specific commands cover the common cases with no gaps.

5 / 5

Workflow Clarity

Twelve clearly sequenced steps with explicit validation checkpoints and feedback loops: "Fix tmp-PR-content.md until the check passes" (step 8), re-running the check after developer edits (step 10), and the approval gate "Do not continue until the developer writes `approve`". This is a GitHub-publishing operation with permission asked before pushing and validation before submit, matching the 5 anchor.

5 / 5

Progressive Disclosure

The body itself is well organized (Inputs / Steps / Rules) and references are one level deep and clearly signaled ("Obey pr-what-prompt.md in this folder", "Obey release-note-prompt.md in this folder"), but no references/, scripts/, or assets/ directories exist in the bundle, so both referenced prompt files are missing — the disclosed content cannot actually be loaded. Not 4 because the reference structure is incomplete/unverifiable rather than having only minor gaps; not 2 because the in-body structure is good and references are clearly signaled rather than buried.

3 / 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: concrete third-person actions, an explicit 'Use when' trigger clause, and a distinctive mflux-scoped niche. The only weaknesses are minor — slightly thin trigger synonym coverage and a few unmentioned capabilities (title handling, the approval gate).

DimensionReasoningScore

Specificity

Lists several concrete third-person actions — "Write the PR body for the current mflux branch", "Fills the What section, the release-note block and the Verification section of the PR template" — with specific template targets. Not 5 because coverage has gaps (the PR title handling, the developer approval gate, and the create/edit step are unmentioned); not 3 because it goes beyond 1-2 generic actions with named template sections.

4 / 5

Completeness

Explicitly answers both: what ("Write the PR body... Fills the What section, the release-note block and the Verification section of the PR template") and when ("Use when the developer asks to write, fill or update a PR description or a release note") with concrete trigger phrases. Clearly matches the 5 anchor, not 4, since the 'when' clause is explicit and specific.

5 / 5

Trigger Term Quality

Natural phrases users would say are present: "PR body", "PR description", "release note", "write, fill or update". Not 5 because common variations like "pull request", "PR summary", or "changelog" are missing; not 3 because the included terms are the ones a developer would naturally use rather than jargon.

4 / 5

Distinctiveness Conflict Risk

Scoped to "the current mflux branch" and project-specific template sections, giving a clear niche with distinct triggers. Not 5 because it could still overlap with a generic PR-description skill when the user just says "write the PR description"; not 3 because the mflux and template-section qualifiers keep it mostly distinct.

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

mflux-community/mflux

Path

.cursor/skills/mflux-pr-docs/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.