jira-safe
Implement SAFe methodology in Jira. Use when creating Epics, Features, Stories with proper hierarchy, acceptance criteria, and parent-child linking.
61
71%
Does it follow best practices?
Impact
—
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, 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') and when ('Use when creating Epics, Features, Stories with proper hierarchy, acceptance criteria, and parent-child linking'). Has an explicit 'Use when' clause with specific triggers. | 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 a user working with SAFe in Jira would naturally use. | 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 is highly actionable with executable, copy-paste-ready code for Jira SAFe implementation, and the Next-Gen vs Classic distinction is genuinely useful project-specific knowledge. However, it is severely bloated—the verbose ADF JSON templates, repeated comparison tables, and inlined reference material make it a poor use of context window. The lack of validation on destructive operations (bulk delete) and missing verification steps for created hierarchies weaken workflow safety.
Suggestions
Extract the verbose ADF JSON templates into a separate TEMPLATES.md file and reference it from the main skill, keeping only a compact example or helper function inline.
Consolidate the repeated Next-Gen vs Classic comparison tables into a single reference table, removing the duplicated information across 'Custom Fields by Project Type' and 'Issue Link Types' sections.
Add a confirmation/dry-run step to the bulk delete function and a verification step after batch creation to confirm parent-child links were established correctly.
Move SAFe best practices (INVEST criteria, naming conventions, acceptance criteria format) to a separate SAFE_PRACTICES.md since Claude already understands these concepts and they are not Jira-API-specific.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~300+ lines. The ADF (Atlassian Document Format) JSON templates are massively bloated and could be abstracted into a helper function or referenced file. The Classic vs Next-Gen comparison tables are repeated multiple times with overlapping information. Claude already understands REST APIs, JSON structures, and basic JavaScript patterns. | 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. The project type detection code is immediately usable. | 3 / 3 |
Workflow Clarity | The create functions show clear sequential steps (create Epic → create Stories → create Subtasks), but the bulk delete function lacks any confirmation or validation checkpoint before destructive operations. There's no verification step to confirm created issues are properly linked, and no feedback loop for handling partial failures in batch creation beyond a simple console.error and continue. | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of content with no references to supporting files. The ADF templates, API implementation details, custom field reference tables, and best practices are all inlined when they could easily be split into separate reference files. With no bundle files provided, the entire skill dumps everything into one massive document. | 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
df877a9
- 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.