jira-safe
Implement SAFe methodology in Jira. Use when creating Epics, Features, Stories with proper hierarchy, acceptance criteria, and parent-child linking.
77
71%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./data/skills-md/01000001-01001110/agent-jira-skills/jira-safe/SKILL.mdQuality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong, well-crafted description that clearly identifies its domain (SAFe in Jira), lists specific actions (creating Epics, Features, Stories with hierarchy and acceptance criteria), and includes an explicit 'Use when' clause with natural trigger terms. It is concise, uses third-person voice, and is highly distinguishable from other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: creating Epics, Features, Stories, establishing proper hierarchy, writing acceptance criteria, and parent-child linking. These are all concrete, actionable tasks. | 3 / 3 |
Completeness | Clearly answers both 'what' (implement SAFe methodology in Jira with Epics, Features, Stories, hierarchy, acceptance criteria, linking) and 'when' (explicit 'Use when creating Epics, Features, Stories with proper hierarchy, acceptance criteria, and parent-child linking'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'SAFe', 'Jira', 'Epics', 'Features', 'Stories', 'hierarchy', 'acceptance criteria', 'parent-child linking'. These are terms practitioners naturally use when working with SAFe in Jira. | 3 / 3 |
Distinctiveness Conflict Risk | The combination of SAFe methodology + Jira + specific artifact types (Epics, Features, Stories) creates a very clear niche. Unlikely to conflict with generic project management or other Jira skills due to the SAFe-specific framing. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides highly actionable, executable code for Jira SAFe implementation with good coverage of Next-Gen vs Classic differences. However, it is severely bloated - the verbose ADF JSON templates, repeated Next-Gen/Classic comparisons across multiple sections, and tangential utilities (bulk delete, field finder) make it far too long. The content would benefit greatly from splitting into overview + reference files and trimming the ADF templates to minimal examples.
Suggestions
Extract the full ADF JSON templates into a separate TEMPLATES.md file and keep only a minimal example in the main skill showing the structure pattern, since Claude can construct ADF from a brief example.
Remove or relocate the bulk delete function and epic link field finder to a separate UTILITIES.md - they are not core to SAFe methodology implementation.
Consolidate the repeated Next-Gen vs Classic comparison tables into a single reference table instead of repeating the information in 3-4 different sections.
Add a verification step after hierarchy creation (e.g., fetch the created epic and confirm child issues are linked) and add a dry-run or confirmation step before bulk delete.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~300+ lines. The ADF (Atlassian Document Format) JSON templates are massively bloated - Claude already knows ADF structure and doesn't need every heading/paragraph/bulletList node spelled out in full. The same information about Next-Gen vs Classic is repeated in multiple tables and inline comments throughout. The bulk delete function and epic link field finder are tangential to the SAFe methodology focus. | 1 / 3 |
Actionability | The skill provides fully executable JavaScript code with complete API calls, proper authentication headers, error handling, and rate limiting. Templates are copy-paste ready with clear placeholder values, and the project type detection code is immediately usable. | 3 / 3 |
Workflow Clarity | The create functions show sequential steps (create epic, then stories, then subtasks) with error handling, but there's no validation checkpoint after creation to verify the hierarchy was correctly established. The bulk delete function lacks any confirmation or dry-run step before destructive operations, which should cap this at 2. | 2 / 3 |
Progressive Disclosure | Everything is in a single monolithic file with no references to separate files for detailed content. The ADF templates, API implementation, custom field tables, and best practices are all inline. The ADF templates alone could be in a separate reference file, and the Classic vs Next-Gen differences could be split out. | 1 / 3 |
Total | 7 / 12 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- NeverSight/skills_feed
- Commit
f772de4
- 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.