tessl install https://github.com/softaworks/agent-toolkit --skill jiragithub.com/softaworks/agent-toolkit
Use when the user mentions Jira issues (e.g., "PROJ-123"), asks about tickets, wants to create/view/update issues, check sprint status, or manage their Jira workflow. Triggers on keywords like "jira", "issue", "ticket", "sprint", "backlog", or issue key patterns.
Average Score
95%
Content
100%
Description
90%
Generated
Validations
Total score
13/16| Criteria | Score |
|---|---|
skill_md_line_count SKILL.md line count is 196 (<= 500) | |
frontmatter_valid YAML frontmatter is valid | |
name_field 'name' field is valid: 'jira' | |
description_field 'description' field is valid (263 chars) | |
description_voice 'description' uses third person voice | |
description_trigger_hint Description includes an explicit trigger hint | |
compatibility_field 'compatibility' field not present (optional) | |
allowed_tools_field 'allowed-tools' field not present (optional) | |
metadata_version 'metadata' field is not a dictionary | |
metadata_field 'metadata' field not present (optional) | |
license_field 'license' field is missing | |
frontmatter_unknown_keys No unknown frontmatter keys found | |
body_present SKILL.md body is present | |
body_examples Examples detected (code fence or 'Example' wording) | |
body_output_format No obvious output/return/format terms detected; consider specifying expected outputs | |
body_steps Step-by-step structure detected (ordered list) |
Content
Total score
12/12| Dimension | Score |
|---|---|
conciseness The skill is lean and efficient, using tables for quick reference, avoiding explanations of what Jira is or how APIs work. Every section serves a clear purpose with no padding or unnecessary context. | 3/3 |
actionability Provides concrete, copy-paste ready commands for CLI and specific MCP tool names. The quick reference tables give exact syntax for common operations, and the backend detection steps are explicit and executable. | 3/3 |
workflow_clarity Multi-step workflows (creating/updating tickets) include explicit validation checkpoints like 'fetch issue first', 'show current vs proposed changes', 'get approval before updating', and 'verify updates after applying'. The 'NEVER' section provides clear guardrails for risky operations. | 3/3 |
progressive_disclosure Excellent structure with quick reference tables for common operations upfront, clear signaling of when to load detailed references, and a helpful table showing which tasks need reference files. References are one level deep and clearly organized. | 3/3 |
Overall Assessment
This is an exemplary skill file that demonstrates excellent token efficiency through tables and structured sections, provides fully actionable commands for both backends, includes robust safety guardrails with explicit validation steps, and uses progressive disclosure effectively by keeping the main file scannable while pointing to detailed references only when needed.
Description
Suggestions 1
Total score
11/12| Dimension | Score |
|---|---|
specificity Names the domain (Jira) and mentions actions like 'create/view/update issues, check sprint status, manage workflow', but these are somewhat general rather than listing multiple specific concrete actions like 'assign issues, add comments, transition status, link issues'. | 2/3 |
completeness Clearly answers both what (create/view/update issues, check sprint status, manage Jira workflow) AND when (explicit 'Use when' clause with specific triggers including keywords and patterns). The description leads with the 'when' guidance. | 3/3 |
trigger_term_quality Excellent coverage of natural terms users would say: 'jira', 'issue', 'ticket', 'sprint', 'backlog', issue key patterns like 'PROJ-123'. These are exactly what users would naturally mention when needing Jira help. | 3/3 |
distinctiveness_conflict_risk Very distinct niche with Jira-specific triggers including the unique issue key pattern 'PROJ-123'. Unlikely to conflict with other skills due to specific product name and terminology like 'sprint', 'backlog'. | 3/3 |
Suggestions
Expand the capability list with more specific actions like 'assign issues, add comments, transition workflow states, search with JQL, view issue details' to improve specificity.
Overall Assessment
This is a well-structured description that excels at trigger term coverage and completeness, with explicit 'Use when' guidance and natural keywords users would say. The main weakness is that the capability description could be more specific about concrete actions beyond the general 'create/view/update' verbs. Uses appropriate third-person voice throughout.