CtrlK
BlogDocsLog inGet started
Tessl Logo

012-agile-epic

Guides the creation of agile epics with comprehensive definition including business value, success criteria, and breakdown into user stories. Use when the user wants to create an agile epic, define large bodies of work, break down features into user stories, or document strategic initiatives. This should trigger for requests such as Create an agile epic; Write an epic; I need to create an epic; Define an epic; Epic definition. Part of Plinth Toolkit

68

Quality

81%

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

71%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 well-organized interactive skill body with a clear sequenced workflow and excellent progressive disclosure into a single reference file. The main weakness is redundancy between the description, the "When to use" section, and the duplicated constraints versus workflow step constraints.

Suggestions

Remove or condense the "When to use this skill" section since those trigger phrases already appear verbatim in the frontmatter description, avoiding duplication.

Merge the "Constraints" MANDATORY/MUST list into the corresponding Workflow steps (or reference them once) to eliminate the near-duplication with the Step 1 step-constraints.

Inline the core question template (or its first few questions) in the body so the agent has copy-paste-ready guidance without needing to open the reference before the first interaction.

DimensionReasoningScore

Conciseness

Mostly efficient, but the "When to use this skill" section duplicates trigger phrases already in the description, and the "Constraints" MANDATORY/MUST list largely repeats the Workflow step constraints, so it could be tightened; not a 2 because the body itself is reasonably lean and does not over-explain concepts Claude already knows.

3 / 5

Actionability

Concrete, executable guidance is given (run `date`, ask template questions in strict order, generate Markdown with an explicit required-sections list), but the actual question template lives in the reference file rather than inline, leaving a minor gap; not a 5 because copy-paste-ready detail is delegated to the reference.

4 / 5

Workflow Clarity

A clearly numbered 0–3 sequence with interaction checkpoints ("wait for user response before proceeding," strict ordering, sanitized-summary gating); not a 5 because there is no explicit validate-and-retry feedback loop, though the interactive nature makes that less critical here.

4 / 5

Progressive Disclosure

The body is a concise overview that points to a single, real, one-level-deep reference ("see references/012-agile-epic.md") that exists in the bundle, with content appropriately split and easy navigation, matching the top anchor.

5 / 5

Total

16

/

20

Passed

Description

91%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 strong, well-structured description that clearly states capability and provides rich, natural trigger phrases. It is comprehensive on both the what and the when, with only minor overlap risk against related agile-planning skills.

DimensionReasoningScore

Specificity

Names the domain and multiple concrete capabilities ("business value, success criteria, and breakdown into user stories"), giving several specific actions with only minor coverage gaps; not a 5 because the lead verb "Guides the creation" bundles actions rather than enumerating distinct ones.

4 / 5

Completeness

Explicitly answers both what ("Guides the creation of agile epics with comprehensive definition...") and when ("Use when the user wants to create an agile epic...") with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Comprehensive natural trigger phrases users would actually say ("Create an agile epic; Write an epic; I need to create an epic; Define an epic; Epic definition") plus "Use when the user wants to..." variations cover synonyms and natural phrasings.

5 / 5

Distinctiveness Conflict Risk

The agile-epic niche with distinct epic-specific triggers has minimal conflict risk; not a 5 because adjacent agile/story-planning skills could share some overlap on "break down features into user stories."

4 / 5

Total

18

/

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
jabrena/plinth
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.