jira-safe
Implement SAFe methodology in Jira. Use when creating Epics, Features, Stories with proper hierarchy, acceptance criteria, and parent-child linking.
86
Quality
82%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Optimize this skill with Tessl
npx tessl skill review --optimize ./data/skills-md/01000001-01001110/agent-jira-skills/jira-safe/SKILL.mdDiscovery
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 skill description that clearly defines its scope (SAFe in Jira), lists specific capabilities (Epics, Features, Stories, hierarchy, acceptance criteria, linking), and provides explicit trigger guidance. The description uses proper third-person voice and includes domain-specific terminology that users would naturally use when needing this skill.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'creating Epics, Features, Stories with proper hierarchy, acceptance criteria, and parent-child linking' - these are concrete, actionable capabilities. | 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') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'SAFe', 'Jira', 'Epics', 'Features', 'Stories', 'hierarchy', 'acceptance criteria', 'parent-child linking' - good coverage of domain-specific terms users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche combining SAFe methodology specifically with Jira, plus specific artifact types (Epics, Features, Stories). Unlikely to conflict with generic Jira skills or other agile methodology skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides highly actionable, executable code for Jira SAFe implementation with excellent coverage of Next-Gen vs Classic project differences. However, it's overly verbose with redundant information and large inline templates that inflate token usage. The workflow guidance could benefit from explicit validation steps, especially for bulk operations.
Suggestions
Extract the full ADF templates into a separate TEMPLATES.md file and reference them from the main skill, keeping only minimal examples inline
Remove the duplicate Classic/Next-Gen comparison tables and consolidate into a single reference section
Add explicit validation steps after issue creation (e.g., verify the created issue has expected parent link, check response for warnings)
Add a confirmation/dry-run pattern for the bulk delete operation to prevent accidental data loss
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some redundancy (e.g., the Classic vs Next-Gen comparison table appears twice, and some concepts are over-explained). The templates are verbose with full ADF structure that could be condensed or referenced externally. | 2 / 3 |
Actionability | Provides fully executable JavaScript code examples with complete API calls, proper authentication headers, error handling, and rate limiting. Templates are copy-paste ready with clear field mappings for both project types. | 3 / 3 |
Workflow Clarity | Multi-step processes like createEpicWithStories show clear sequencing, but validation checkpoints are minimal. The bulk delete operation lacks confirmation steps, and there's no explicit validation that created issues match expected structure. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but the skill is monolithic (~400 lines) with detailed templates inline that could be split into separate reference files. External references are only to documentation sites, not to companion skill files. | 2 / 3 |
Total | 9 / 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.
- 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.