jira-task

Create a Jira task in the LPD project through the REST API. Use when the user asks to create a Jira task or LPD task ticket.

Quality

73%

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

Quality

Content

72%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is lean, well-organized, and offers concrete field-level guidance, but it stops short of giving the executable REST API call and omits any success-validation or error-handling step.

Suggestions

Add an executable example of the create-issue REST call (endpoint, curl command with headers, and a sample JSON/ADF payload) so the core action is copy-paste ready.

Include a validation step after creation (e.g., confirm the response returns an issue key, handle non-2xx responses) to close the workflow feedback loop.

Dimension	Reasoning	Score
Conciseness	Lean ~30-line body with no concept explanations or padding; assumes Claude knows ADF and REST APIs and every section is actionable.	3 / 3
Actionability	Provides concrete specifics (Issue Type ID 10002, browse URL, ADF section order, component inference, git show), but for an API skill never gives the actual endpoint, curl command, or request payload for the core "create the issue" action.	2 / 3
Workflow Clarity	Steps are clearly sequenced as sections (Input, Gather Information, Required Fields, Create the Ticket, Output), but there is no validation checkpoint or error-handling/feedback loop for the API call.	2 / 3
Progressive Disclosure	Under 50 lines with clean, well-organized sections and no need for external references (no bundle files present), satisfying the simple-skill guideline for a full score.	3 / 3
	Total	10 / 12 Passed

Description

75%

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 clear and complete with an explicit trigger clause and a well-defined niche, though it names only one concrete action and a somewhat narrow set of trigger terms.

Suggestions

Broaden trigger terms to include common variations such as "Jira issue", "create a ticket", or "log a task".

Consider mentioning additional concrete actions (e.g., set required fields, post the ADF description) to reach full specificity.

Dimension	Reasoning	Score
Specificity	Names the domain and one concrete action ("Create a Jira task in the LPD project through the REST API"), but lists only a single action rather than multiple specific concrete actions.	2 / 3
Completeness	Clearly answers both "what" (create a Jira task in LPD via REST API) and "when" with an explicit "Use when..." trigger clause.	3 / 3
Trigger Term Quality	Provides natural trigger terms ("create a Jira task", "LPD task ticket") but coverage is narrow, missing common variations like "issue", "ticket" alone, or "log a task".	2 / 3
Distinctiveness Conflict Risk	Targets a clear narrow niche (LPD project, task type, REST API) with distinct triggers, making it unlikely to fire for unrelated skills.	3 / 3
	Total	10 / 12 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: liferay/liferay-portal
Path: .claude/skills/jira-task/SKILL.md
Commit: ce5402e

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