jira-epic

Creates Jira epics for large features following Prowler's standard format. Trigger: When user asks to create an epic, large feature, or multi-task initiative.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./curated/jira-epic/SKILL.md

Quality

Content

76%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 highly actionable with exact, copy-paste-ready MCP integration details and a clear command sequence. Its main weaknesses are the missing runtime validation checkpoints in the issue-creation workflow (capping workflow clarity) and a monolithic structure that could split detailed references into separate files.

Suggestions

Add explicit validation checkpoints to the MCP Commands Sequence (e.g., verify the epic key was returned before creating child tasks, confirm Team/customfield values were accepted) to lift workflow clarity above the batch-operation cap of 3.

Externalize the Mermaid diagram gallery and/or the Jira MCP field reference into one-level-deep reference files (e.g., references/diagrams.md, references/mcp-fields.md) and link to them from SKILL.md to improve progressive disclosure.

Remove redundancy between Formatting Rules, Required Sections, and Checklist Before Submitting to tighten conciseness.

Dimension	Reasoning	Score
Conciseness	The body is mostly concrete templates and executable examples without explaining concepts Claude already knows, but a few redundant sections (Formatting Rules restate the template; Checklist Before Submitting duplicates Required Sections) could be trimmed, matching anchor 4.	4 / 5
Actionability	Provides copy-paste-ready MCP JSON with exact field names (customfield_10359, customfield_10363), workflow transition IDs, and the exact MCP command sequence, fully covering the common cases per anchor 5.	5 / 5
Workflow Clarity	The MCP Commands Sequence gives a clear ordered workflow, but this batch/issue-creation operation lacks runtime validation checkpoints (e.g., confirm the epic was created before spawning child tasks), so workflow clarity is capped at 3 per the destructive/batch guideline.	3 / 5
Progressive Disclosure	Well-organized with clear section headers and no nested external references, but it is a ~300-line monolithic file where the Mermaid diagram gallery and MCP field reference could be externalized into one-level-deep reference files, keeping it at 4 rather than 5.	4 / 5
	Total	16 / 20 Passed

Description

73%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 a distinct niche (Jira epics in Prowler) with an explicit trigger clause, strong on distinctiveness and trigger quality. It is held back mainly by a thin single-action 'what' that limits specificity and completeness from reaching the top anchor.

Dimension	Reasoning	Score
Specificity	Names the domain ('Jira epics for large features') and one concrete action ('Creates') following a standard format, matching anchor 3 for 1-2 concrete actions without comprehensive coverage.	3 / 5
Completeness	Both 'what' (Creates Jira epics...) and 'when' (Trigger: When user asks...) are explicitly present with concrete trigger phrases; the 'what' side is a single concise action rather than a fuller description, keeping it at 4 instead of 5.	4 / 5
Trigger Term Quality	The explicit 'Trigger:' clause lists natural user phrases ('epic, large feature, multi-task initiative') with good keyword coverage, falling just short of comprehensive synonym/extension coverage for a 5.	4 / 5
Distinctiveness Conflict Risk	Tied to a specific artifact type (Jira epics) and a named project context (Prowler) with distinct triggers, giving a clear niche and minimal conflict risk with other skills.	5 / 5
	Total	16 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: Gentleman-Programming/Gentleman-Skills
Path: curated/jira-epic/SKILL.md
Commit: c8036a3

Reviewed: 5 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.