jira-automation
Automate Jira tasks via Rube MCP (Composio): issues, projects, sprints, boards, comments, users. Always search tools first for current schemas.
Install with Tessl CLI
npx tessl i github:davepoon/buildwithclaude --skill jira-automation67
Quality
51%
Does it follow best practices?
Impact
95%
1.97xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/all-skills/skills/jira-automation/SKILL.mdDiscovery
40%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 identifies a clear niche (Jira automation via specific tooling) and lists relevant entity types, but lacks concrete action verbs and completely omits explicit trigger guidance. The instruction about searching tools first is helpful for implementation but doesn't help Claude decide when to select this skill.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user asks about Jira tickets, sprint planning, issue tracking, or project management in Jira'
Replace 'Automate Jira tasks' with specific action verbs: 'Create, update, search, and manage Jira issues; plan sprints; assign users to tickets'
Include common user terminology variations like 'tickets', 'backlog', 'story points', 'kanban board' to improve trigger matching
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Jira) and lists several entity types (issues, projects, sprints, boards, comments, users) but doesn't describe concrete actions beyond 'automate tasks'. Missing specific verbs like 'create', 'update', 'search', 'assign'. | 2 / 3 |
Completeness | Describes what it does (automate Jira tasks) but completely lacks a 'Use when...' clause or any explicit trigger guidance. The instruction to 'search tools first' is implementation guidance, not usage triggers. Per rubric, missing explicit trigger guidance caps this at 2, but the 'what' is also weak, warranting a 1. | 1 / 3 |
Trigger Term Quality | Includes good keywords like 'Jira', 'issues', 'projects', 'sprints', 'boards' that users would naturally say. However, missing common variations like 'tickets', 'backlog', 'story points', 'assignee', or action-oriented terms like 'create issue', 'move ticket'. | 2 / 3 |
Distinctiveness Conflict Risk | Clearly specific to Jira via Rube MCP/Composio - this is a distinct niche that wouldn't conflict with other skills. The combination of 'Jira' and 'Rube MCP (Composio)' creates clear boundaries. | 3 / 3 |
Total | 8 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill with excellent workflow clarity and clear tool sequences for Jira automation. The main weaknesses are the lack of executable code examples (only tool names and parameters are listed) and some redundancy across sections. The skill would benefit from concrete payload examples showing actual tool invocations.
Suggestions
Add at least one executable example per core workflow showing the actual tool call with a complete payload/parameters structure
Consolidate repeated pitfalls (custom field IDs, account IDs vs usernames) into a single 'Common Pitfalls' section to reduce redundancy
Consider moving the Quick Reference table to a separate REFERENCE.md file to reduce the main skill length
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundancy (e.g., pitfalls sections repeat similar information about custom fields/account IDs across multiple workflows). The quick reference table at the end duplicates information already covered in the workflows. | 2 / 3 |
Actionability | Provides tool names and parameter lists but lacks executable code examples. The guidance is specific about which tools to call and in what order, but there are no actual code snippets or copy-paste ready examples showing how to construct the tool calls with real payloads. | 2 / 3 |
Workflow Clarity | Excellent workflow structure with clear numbered sequences, explicit prerequisites, and 'When to use' context for each workflow. Tool sequences clearly mark [Required], [Optional], and [Prerequisite] steps. Pitfalls sections provide validation guidance for common failure modes. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but everything is in a single file. The skill is fairly long (~200 lines) and could benefit from splitting detailed workflow sections or the quick reference into separate files. However, the structure within the file is logical and navigable. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%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 | |
- 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.