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.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/humanize-gen-plan/SKILL.md

Quality

Content

92%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 highly actionable and clearly sequenced with strong validation feedback loops, making it effective as a flow skill. The only soft spot is progressive disclosure, since all content lives inline with no external reference structure.

Dimension	Reasoning	Score
Conciseness	The body is lean and structured — a mermaid flow, an input-args list, a copy-paste plan template, an exit-code table, and usage — with no padding explaining concepts Claude already knows, fitting the 'every token earns its place' anchor.	3 / 3
Actionability	It provides an executable validation command, a complete copy-paste-ready plan.md template with AC-X positive/negative tests, and concrete usage commands, matching the fully-executable anchor rather than the pseudocode level 2.	3 / 3
Workflow Clarity	The mermaid flow shows an explicit sequence with validation checkpoints and feedback loops (RESOLVE→ANALYZE, FIX→REVIEW), plus a validation-gate exit-code table, matching the clear-sequence-with-feedback-loops anchor.	3 / 3
Progressive Disclosure	The skill is a single well-organized self-contained file with no nested or broken references, but everything is inline with no content split or progressive references, and at over 50 lines it does not cleanly qualify for the simple-skill automatic 3.	2 / 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 distinctive about the skill's actions, but it omits any explicit 'when to use it' trigger guidance, which limits its activation quality. Adding a 'Use when…' clause would raise both completeness and trigger-term quality.

Suggestions

Append a 'Use when…' clause naming natural triggers, e.g. 'Use when converting a rough draft into a structured implementation plan, or when the user asks for acceptance criteria and path boundaries for a draft document.'

Add common-noun variations users might actually say ('draft doc', 'implementation plan', 'acceptance criteria', 'AC-X', 'plan.md') so trigger matching is broader.

Keep the concrete action list but front-load the most common user phrasing so the trigger reads naturally before the mechanism.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Validates input, checks relevance, analyzes for issues, and generates a complete plan.md with acceptance criteria' — matching the top anchor of several specific concrete actions rather than vague language.	3 / 3
Completeness	It clearly states what the skill does, but never says when to use it; the missing 'Use when…' clause caps completeness at 2 per the rubric guideline, and it is not level 1 because the 'what' is strong.	2 / 3
Trigger Term Quality	Terms like 'draft document', 'implementation plan', and 'acceptance criteria' are domain-relevant, but common variations and a natural 'Use when…' phrasing are absent, so it is not the full coverage of level 3.	2 / 3
Distinctiveness Conflict Risk	The niche of turning a draft document into a plan.md with acceptance criteria is specific and unlikely to trigger for unrelated skills, fitting the clear-niche anchor rather than the overlapping level 2.	3 / 3
	Total	10 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: PolyArch/humanize
Path: skills/humanize-gen-plan/SKILL.md
Commit: 0ec921a

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.