CtrlK
BlogDocsLog inGet started
Tessl Logo

mflux-pr

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

70

Quality

85%

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

96%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 tight, highly actionable PR workflow with concrete commands, clear validation gates, and well-structured sections pointing to sibling skills for deeper detail.

DimensionReasoningScore

Conciseness

Lean and efficient — assumes Claude's competence, uses concrete commands with no padding or explanation of concepts Claude already knows.

5 / 5

Actionability

Fully executable guidance throughout: specific commands like 'just test-fast', 'just lint', the pytest invocation with env var, and du-measurement commands are copy-paste ready.

5 / 5

Workflow Clarity

Clear sequenced sections with explicit validation checkpoints — 'Always ask for permission before pushing', the pre-merge checklist, and disk-claim verification via measurement provide strong feedback loops.

5 / 5

Progressive Disclosure

Well-organized sections with clear navigation to sibling skills (e.g. 'mflux-model-porting → Integration surfaces checklist'), one level deep; minor gaps as there are no local bundle files to confirm reference targets.

4 / 5

Total

19

/

20

Passed

Description

75%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 concrete, well-scoped description with good action specificity and trigger terms, but it lacks an explicit 'Use when' trigger clause, capping completeness at 3.

Suggestions

Add an explicit trigger clause such as 'Use when opening a PR in the mflux repo' to answer both 'what' and 'when' clearly.

Include synonyms like 'pull request' alongside 'PR' for broader natural-term coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'inspect diff, quick verification, commit, push, open PR' — giving comprehensive coverage of the PR workflow rather than vague language.

5 / 5

Completeness

The 'what' is clear (the listed PR steps), but there is no 'Use when...' or equivalent explicit trigger guidance, which the rubric caps at 3.

3 / 5

Trigger Term Quality

Natural phrases like 'Make a clean PR', 'open PR', 'commit, push' match what users say, but it misses synonyms like 'pull request' and 'submit PR' for full coverage.

4 / 5

Distinctiveness Conflict Risk

Scoped specifically to 'mflux' with repo conventions, giving it a clear niche with minimal risk of triggering for unrelated skills.

5 / 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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
filipstrand/mflux
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.