mflux-pr

Make a clean PR in mflux (inspect diff, quick verification, commit, push, open PR) using repo conventions.

Quality

77%

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

Fix and improve this skill with Tessl

tessl review fix ./.cursor/skills/mflux-pr/SKILL.md

Quality

Content

87%Weight 40%Scale 1-3

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

The body is concise, highly actionable, and well-organized with appropriate one-level cross-skill references, but the primary PR creation workflow is presented as implicit/checklist guidance rather than an explicit ordered sequence with validation checkpoints.

Suggestions

Add a short numbered "Core PR flow" sequence (inspect diff → fast tests → commit → push with permission → open PR) so the primary workflow has explicit checkpoints, not just the pre-merge polish phase.

Make the push permission checkpoint part of that ordered sequence rather than a standalone bullet so the gating step is unmissable.

Clarify which verification step gates the commit vs. the push to strengthen the feedback loop for this outward-facing operation.

Dimension	Reasoning	Score
Conciseness	The body is lean and task-focused — bullet points and short code blocks with no explanation of concepts Claude already knows (what a PR is, how git works); every section earns its place.	3 / 3
Actionability	Provides fully executable commands throughout — `make test-fast`, `make lint`, a parameterized pytest invocation with an env var, and concrete `du -sh` / `mflux-save` measurement commands — copy-paste ready.	3 / 3
Workflow Clarity	The pre-merge checklist is numbered with validation steps, but the core PR creation flow (inspect diff, verify, commit, push, open PR) is not given as an explicit ordered sequence with checkpoints — it is implied via the description and scattered bullet guidance.	2 / 3
Progressive Disclosure	Content is organized into clearly labeled sections and points one level deep to sibling skills by name (e.g. "see `mflux-model-porting` → Integration surfaces checklist") with no nested/deep references; no bundle files exist to audit, and the well-organized structure fits the simple-skill allowance.	3 / 3
	Total	11 / 12 Passed

Description

67%Weight 40%Scale 1-3

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 and well-scoped to a distinct niche, but it omits an explicit "Use when..." trigger clause and leans on a single keyword ("PR") without common variations, limiting trigger coverage.

Suggestions

Add an explicit trigger clause, e.g. "Use when opening a pull request in the mflux repo or when the user asks to create/submit a PR."

Broaden trigger terms to include natural variations such as "pull request" alongside "PR".

Consider signaling the model-porting sub-context in the description so the skill is discoverable for that narrower task as well.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions in sequence — "inspect diff, quick verification, commit, push, open PR" — matching the anchor for enumerating specific actions rather than vague language.	3 / 3
Completeness	Clearly states what the skill does, but there is no "Use when..." clause or equivalent explicit trigger guidance; per the judging guideline, a missing trigger clause caps completeness at 2.	2 / 3
Trigger Term Quality	Includes the natural term "PR" and "clean PR" but relies on a single project name (mflux) without common variations like "pull request" or "create a PR", so coverage is partial.	2 / 3
Distinctiveness Conflict Risk	The mflux project scoping plus the PR-specific actions give it a clear niche with distinct triggers, making conflict with other skills unlikely.	3 / 3
	Total	10 / 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: filipstrand/mflux
Path: .cursor/skills/mflux-pr/SKILL.md
Commit: 4ac641e

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