jira-task

Creates Jira tasks following Prowler's standard format. Trigger: When user asks to create a Jira task, ticket, or issue.

Quality

76%

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-task/SKILL.md

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.

The body is highly actionable with concrete templates and exact MCP integration details, and the workflow is clearly sequenced. Its weaknesses are length/redundancy and the absence of progressive disclosure, since everything is inlined rather than split into reference files.

Suggestions

Move the Parent/Child templates, Jira MCP integration reference (field mappings, epic table, workflow transitions) into a separate references/jira-mcp.md and link to it from SKILL.md to improve progressive disclosure and reduce inline length.

Consolidate the overlapping Task Template, Parent Task Template, and Child Task Template sections into a single parameterized template, and fold the Checklist Before Submitting and Formatting Rules into the relevant sections to remove redundancy.

Add an explicit validation step to the MCP command sequence (e.g., verify each created issue key, confirm parent/child and blocked-by links resolve) to strengthen workflow clarity for multi-task creation.

Dimension	Reasoning	Score
Conciseness	The ~377-line body is mostly concrete but includes redundant sections (overlapping Task/Parent/Child templates, a Checklist Before Submitting that restates earlier rules, and Formatting Rules), so it could be tightened despite avoiding explanations of concepts Claude already knows.	3 / 5
Actionability	It provides copy-paste-ready Markdown templates with placeholders, exact MCP JSON with real field names (customfield_10359, customfield_10363), epic keys, workflow transition IDs, and a command sequence, fully covering the common cases.	5 / 5
Workflow Clarity	The MCP Commands Sequence (create issue → update Work Item Description → assign and transition) plus the Checklist Before Submitting give a clear sequence with most checkpoints, though explicit validation that issues were created and linked correctly is only implicit.	4 / 5
Progressive Disclosure	Content is well-organized with section headers, but with no bundle files all ~377 lines (templates, MCP reference, epic table, workflow transitions) are inlined in SKILL.md rather than split into one-level-deep references, fitting the "content that should be separate is inline" anchor.	3 / 5
	Total	15 / 20 Passed

Description

82%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 cleanly states both capability and trigger with natural synonyms and a distinct Prowler-specific niche. Its main limitation is specificity, listing only the headline action rather than the full range of supported task types.

Dimension	Reasoning	Score
Specificity	"Creates Jira tasks following Prowler's standard format" names the domain and one concrete action but does not enumerate the multiple task types or structures it supports, matching the anchor for 1-2 concrete actions without comprehensive coverage.	3 / 5
Completeness	It explicitly answers both what ("Creates Jira tasks following Prowler's standard format") and when ("Trigger: When user asks to create a Jira task, ticket, or issue") with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	"Jira task, ticket, or issue" provides good natural synonyms a user would say, though a few common variations (e.g. "bug report", "feature request") that appear in the body are absent from the description.	4 / 5
Distinctiveness Conflict Risk	The Prowler-specific Jira task creation niche has distinct triggers and minimal overlap with other skills, fitting the clear-niche anchor.	5 / 5
	Total	17 / 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-task/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.