CtrlK
BlogDocsLog inGet started
Tessl Logo

work

Deliver one maintainer-approved EmDash issue, choosing the bug-fix path for a defect and the direct implementation path for an enhancement or task.

64

Quality

75%

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

Fix and improve this skill with Tessl

tessl review fix ./infra/emdash-bot/.flue/skills/work/SKILL.md
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.

The content is a lean, well-structured process skill with concrete gating and validation checkpoints throughout both delivery paths. Its only weakness is minor: it gives specific tool/field names but not exact command signatures, leaving actionability just short of fully executable.

DimensionReasoningScore

Conciseness

The body is lean and directive with no padding and no re-explanation of concepts Claude already knows; every line earns its place, fitting the 'lean and efficient, assumes Claude's competence' anchor.

5 / 5

Actionability

Guidance is concrete and executable, naming specific tools and fields (edit_file, exec, publish_candidate, report_result, fixed, implemented, verdict) with clear gating; it stops short of copy-paste-ready code/signatures, fitting 'mostly executable, minor gaps' rather than the fully executable 5.

4 / 5

Workflow Clarity

Both paths are clearly numbered with explicit validation checkpoints and feedback loops ('Set fixed: true only after publish_candidate succeeds'; 'If reporter-only information prevents a reproduction… report verdict: unclear'; final focused verification pass before publish), fitting the top anchor with explicit validation and error-recovery loops.

5 / 5

Progressive Disclosure

This is a single-purpose skill under 50 lines with no external references needed, and it is cleanly sectioned (Bug path, Enhancement or task path, Shared constraints); per the simple-skills scoring note, well-organized sections alone warrant a 5.

5 / 5

Total

19

/

20

Passed

Description

58%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.

The description clearly conveys the skill's purpose and branching logic but omits an explicit 'Use when…' trigger, which caps its completeness and trigger-term quality. It is specific and reasonably distinct, though it lacks natural user-facing synonyms.

Suggestions

Add an explicit 'Use when…' clause (e.g., 'Use when delivering a maintainer-approved EmDash issue') to raise completeness above the 3 cap.

Include natural user-facing trigger phrases and synonyms (e.g., 'approved issue', 'defect', 'enhancement', 'task', 'publish_candidate') so the skill triggers on how users actually phrase the request.

Name the concrete result fields ('fixed', 'implemented', 'verdict') in the description to push specificity toward comprehensive coverage.

DimensionReasoningScore

Specificity

Names the EmDash-issue domain and several concrete actions ('choosing the bug-fix path for a defect and the direct implementation path for an enhancement or task'), with only minor gaps in coverage; fits the 'several specific actions, minor gaps' anchor and not the fully comprehensive 5.

4 / 5

Completeness

It clearly answers 'what' (deliver an approved issue via two paths) but has no explicit 'Use when…' clause, and per the judging guidelines a missing trigger clause caps completeness at 3; the 'when' is only weakly implied.

3 / 5

Trigger Term Quality

Domain terms like 'maintainer-approved EmDash issue', 'bug-fix', and 'enhancement or task' are relevant but lack the natural user-facing synonyms and phrasings (no 'Use when…' triggers, no common variations); fits the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

The 'maintainer-approved EmDash issue' framing plus the fixed/implemented dichotomy gives it a fairly distinct niche with only minor overlap risk against generic fix/implement skills; fits 'mostly distinct, minor overlap' rather than the fully distinct 5.

4 / 5

Total

14

/

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
emdash-cms/emdash
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.