CtrlK
BlogDocsLog inGet started
Tessl Logo

humanize-refine-plan

Refine an annotated implementation plan into a comment-free plan and a QA ledger while preserving the gen-plan schema.

60

Quality

71%

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 ./skills/humanize-refine-plan/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

81%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 body is a well-structured, actionable flow specification with an explicit validation-gated workflow and feedback loops; its main gaps are minor verbosity and the lack of a complete runnable end-to-end example.

DimensionReasoningScore

Conciseness

The body is mostly efficient reference material (argument spec, exit-code table, alt-language table) with no padding about concepts Claude already knows; only minor trimmable redundancy such as the Usage section keeps it off 5.

4 / 5

Actionability

Concrete guidance is present — exact validate command with flags, argument signatures, classification values, and template path — but no full end-to-end runnable example with real values, leaving minor gaps versus the 5 anchor.

4 / 5

Workflow Clarity

The mermaid flowchart gives a clear sequence with explicit validation checkpoints (VALIDATE, PLAN_CHECK), a feedback loop (FIX -> PLAN_CHECK), and error-reporting branches, matching the 5 anchor for validation with error recovery.

5 / 5

Progressive Disclosure

Content is well organized into clear sections with no nested references and all material appropriately inline; with no bundle files present and the file over 50 lines, structure is good but not the ideal one-level-deep split of a 5.

4 / 5

Total

17

/

20

Passed

Description

62%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 is specific and clearly distinguishable, but it omits any explicit 'when to use' trigger guidance, which caps completeness and leaves trigger-term quality at a moderate level.

Suggestions

Add a 'Use when...' clause naming concrete triggers, e.g. 'Use when refining an annotated gen-plan that contains CMT:/ENDCMT blocks into a clean plan and QA ledger.'

Include natural user phrasings or synonyms (e.g. 'annotated plan', 'plan comments', 'QA ledger') so the description matches how users actually request the skill.

Consider mentioning the input signal explicitly (plans containing CMT:/ENDCMT blocks) to sharpen the trigger.

DimensionReasoningScore

Specificity

Names the domain (annotated implementation plan) and several concrete actions — 'Refine... into a comment-free plan and a QA ledger' plus 'preserving the gen-plan schema' — with only minor coverage gaps, fitting the 4 anchor better than the 1-2-action 3 anchor.

4 / 5

Completeness

The 'what' is clearly stated (refine into comment-free plan + QA ledger preserving schema) but there is no 'Use when...' or equivalent trigger guidance, so per the cap it cannot exceed 3.

3 / 5

Trigger Term Quality

Terms like 'annotated implementation plan', 'QA ledger', and 'gen-plan schema' are domain-relevant but niche/system-internal, lacking the natural user phrasings, synonyms, or file extensions that would lift it to 4-5.

3 / 5

Distinctiveness Conflict Risk

The 'gen-plan schema', 'CMT/ENDCMT', and 'QA ledger' niche is highly specific with distinct triggers and minimal overlap risk with other skills, matching the 5 anchor.

5 / 5

Total

15

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
PolyArch/humanize
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.