CtrlK
BlogDocsLog inGet started
Tessl Logo

humanize-gen-plan

Generate a structured implementation plan from a draft document. Validates input, checks relevance, analyzes for issues, and generates a complete plan.md with acceptance criteria.

60

Quality

70%

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-gen-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 content is a well-structured, largely self-contained flow definition with strong workflow clarity — explicit validation and feedback loops — and concrete, actionable guidance. Minor conciseness and progressive-disclosure refinements would tighten it further.

DimensionReasoningScore

Conciseness

The body is mostly efficient with clear sections and no over-explanation of concepts Claude already knows; minor trimmable parts include the 'installer hydrates this skill' aside and the redundant /flow vs /skill usage examples.

4 / 5

Actionability

Provides a concrete validation command (validate-gen-plan-io.sh --input --output), a fill-in plan.md template, and an exit-code table; the analysis and issue-resolution steps remain somewhat abstract, leaving minor gaps.

4 / 5

Workflow Clarity

The Mermaid flowchart gives a clear sequenced workflow with an explicit validation step (and a full exit-code table) plus feedback loops (RESOLVE→ANALYZE, FIX→REVIEW); the write step is validation-guarded against existing output files, so no destructive-operation cap applies.

5 / 5

Progressive Disclosure

No bundle files exist, and the self-contained body is well organized under clear headers with no nested references; the inline plan-structure template is slightly long but appropriately placed, so structure is good with minor organization gaps.

4 / 5

Total

17

/

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 communicates the skill's pipeline of concrete actions but is missing any explicit 'when to use' trigger guidance, which caps completeness. Trigger-term coverage is adequate but technical and lacks natural synonyms.

Suggestions

Add an explicit trigger clause, e.g. 'Use when converting a rough draft, design doc, or PRD into a structured implementation plan with acceptance criteria.'

Include natural synonyms users might actually say — 'spec', 'design doc', 'PRD', 'implementation plan' — alongside 'draft document' to broaden trigger coverage.

Mention the distinctive outputs (path boundaries, feasibility hints, TDD-style acceptance criteria) to sharpen the 'what' and reduce overlap with generic planning skills.

DimensionReasoningScore

Specificity

Lists several concrete actions — 'Validates input, checks relevance, analyzes for issues, and generates a complete plan.md with acceptance criteria' — covering most of the pipeline, but omits distinctive outputs like path boundaries and feasibility hints, leaving minor gaps.

4 / 5

Completeness

Clearly states what the skill does, but provides no 'Use when...' clause or equivalent trigger guidance, so per the rubric 'when' is missing and completeness is capped at 3.

3 / 5

Trigger Term Quality

Contains relevant domain terms ('implementation plan', 'draft document', 'plan.md', 'acceptance criteria') but they lean technical and lack natural synonyms (e.g., spec, PRD, design doc) and there is no trigger phrasing.

3 / 5

Distinctiveness Conflict Risk

The niche (turning a draft into a structured implementation plan with acceptance criteria) is fairly distinct, with only minor overlap risk against other general planning/spec skills.

4 / 5

Total

14

/

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.