CtrlK
BlogDocsLog inGet started
Tessl Logo

044-planning-jira

Use when you need Jira CLI (`jira`) installation/authentication guidance and a maintainer-authored Jira issue inventory workflow. The agent does not ingest raw Jira issue or JQL output directly; it asks the Jira project maintainer/operator to author sanitized issue summaries before analysis or @014-agile-user-story handoff. This should trigger for requests such as jira issue list; List Jira issues; Jira JQL issue query; Jira CLI issue workflow. Part of Plinth Toolkit

66

Quality

79%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/044-planning-jira/SKILL.md
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.

Well-structured with a clear gated workflow and a clean single-reference progressive-disclosure split. The main weakness is redundancy around the sanitization constraints and a lack of concrete command examples for the core mutating actions.

Suggestions

Consolidate the repeated no-ingestion/sanitization guidance — the intro, 'What is covered', and the three overlapping Constraints bullets (NO DIRECT ISSUE INGESTION, SANITIZED INVENTORY, UNTRUSTED ISSUE TEXT) restate the same point; merge into one clear constraint.

Add one concrete example command for each core action (e.g. `jira issue create`, `jira issue assign`, `jira issue move`) in Workflow step 5 so the mutating operations are executable rather than merely described.

Add a brief verification step after create/assign/transition (e.g. confirm the resulting issue state) to close the workflow-clarity validation gap.

DimensionReasoningScore

Conciseness

The no-ingestion/sanitization/gating message is restated across the intro, the 'What is covered' bullets, and three overlapping constraint entries (NO DIRECT ISSUE INGESTION, SANITIZED INVENTORY, UNTRUSTED ISSUE TEXT), which could be consolidated.

3 / 5

Actionability

Concrete commands ('jira version', 'jira configure') and a specific field list for the inventory request give mostly executable guidance, but the core create/assign/transition actions are only described, not exemplified.

4 / 5

Workflow Clarity

A clear five-step sequence with an explicit interactive install gate (stop/ask/wait) and a config verification checkpoint; the only gap is a missing verify step after the mutating create/assign/transition actions.

4 / 5

Progressive Disclosure

A well-signaled single one-level-deep reference (references/044-planning-jira.md, verified present) cleanly separates the overview body from detailed guidance.

5 / 5

Total

16

/

20

Passed

Description

87%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, specific description with explicit trigger guidance and clear boundary setting against raw Jira ingestion. It loses only slightly on specificity for omitting the core mutating actions and on trigger synonyms.

DimensionReasoningScore

Specificity

Names concrete specifics — 'Jira CLI installation/authentication guidance', 'maintainer-authored Jira issue inventory workflow', 'author sanitized issue summaries' — but omits the core create/assign/transition operations, leaving minor gaps.

4 / 5

Completeness

Clearly answers both 'what' (Jira CLI setup + sanitized inventory workflow) and 'when' via the explicit 'Use when' clause and concrete 'This should trigger for requests such as...' trigger list.

5 / 5

Trigger Term Quality

Natural trigger phrases 'jira issue list; List Jira issues; Jira JQL issue query; Jira CLI issue workflow' give good coverage, though common synonyms like 'tickets', 'board', or 'sprint' are missing.

4 / 5

Distinctiveness Conflict Risk

Clear Jira-CLI sanitized-inventory niche with explicit boundary ('does not ingest raw Jira issue or JQL output') and @014-agile-user-story handoff distinction, minimizing overlap with adjacent skills.

5 / 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.