auto-jira

Autonomously work on Jira backlog tickets, creating PRs and shepherding them to merge

Quality

58%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./.claude/skills/auto-jira/SKILL.md

Quality

Discovery

32%

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 conveys the high-level workflow (Jira tickets → PRs → merge) but lacks specificity about concrete actions and entirely omits explicit trigger guidance. It would benefit from listing specific capabilities and adding a 'Use when...' clause with natural trigger terms users would employ.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to work on Jira tickets, pick up backlog items, create pull requests from issues, or automate ticket-to-PR workflows.'

Include more natural trigger terms and variations such as 'Jira issues', 'stories', 'pull requests', 'sprint backlog', 'code review', and 'GitHub PR'.

List more specific concrete actions, e.g., 'Reads Jira ticket details, creates feature branches, implements changes, opens pull requests, responds to code review feedback, and updates ticket status.'

Dimension	Reasoning	Score
Specificity	Names the domain (Jira backlog tickets) and some actions (creating PRs, shepherding to merge), but lacks detail on specific sub-actions like branch creation, code changes, review handling, or ticket status updates.	2 / 3
Completeness	Describes what the skill does but has no explicit 'Use when...' clause or equivalent trigger guidance. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and since the 'when' is entirely absent (not even implied beyond the what), this scores a 1.	1 / 3
Trigger Term Quality	Includes relevant keywords like 'Jira', 'backlog tickets', and 'PRs', but misses common variations users might say such as 'issues', 'stories', 'pull requests', 'merge requests', 'sprint', or 'code review'.	2 / 3
Distinctiveness Conflict Risk	The combination of Jira + PR creation is somewhat distinctive, but 'creating PRs and shepherding them to merge' could overlap with general Git/GitHub workflow skills or CI/CD skills. The Jira-specific aspect helps but isn't enough to fully distinguish it.	2 / 3
	Total	7 / 12 Passed

Implementation

85%

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

This is a strong, well-architected skill that provides clear autonomous workflow guidance with robust validation checkpoints and progressive disclosure. The actionability is excellent with specific tool names, commands, and formats throughout. Minor verbosity in the Critic Agent prompt templates and some sections could be tightened, but overall the content earns its token budget.

Dimension	Reasoning	Score
Conciseness	The skill is generally well-structured and avoids explaining basic concepts, but includes some redundancy (e.g., the Critic Agent section with full prompt templates is verbose, and the attribution table could be more compact). The ticket selection criteria section is thorough but lengthy.	2 / 3
Actionability	Provides specific MCP tool names, exact CLI commands, concrete branch naming conventions, precise PR title formats, and detailed argument parsing. The workflow steps are copy-paste actionable with specific tool invocations and exact formats for attribution, comments, and commit messages.	3 / 3
Workflow Clarity	The workflow is clearly sequenced with an explicit 8-step per-ticket loop, mandatory PRE-CHECK and POST-CHECK validation via Critic agent for every write action, explicit error recovery (fix and re-validate), and clear completion/failure signals. Human intervention triggers and HOLD transitions provide robust feedback loops for risky operations.	3 / 3
Progressive Disclosure	Excellent use of a supporting documents table that clearly signals when to read each referenced file (ticket-workflow.md, pr-workflow.md, ci-validation.md, troubleshooting.md) with an explicit instruction to not load all docs at once. The main SKILL.md serves as a clear overview with one-level-deep references.	3 / 3
	Total	11 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: DataDog/datadog-agent
Commit: a41685a

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.