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 provides explicit trigger guidance. The description is concise yet comprehensive, using natural terminology that practitioners would use. It effectively distinguishes itself from generic Jira or project management 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 is highly actionable with executable code and concrete templates, but suffers significantly from verbosity - particularly the fully expanded ADF JSON structures that Claude doesn't need spelled out. Content is repeated across multiple sections (Next-Gen vs Classic differences appear in at least 4 places), and the entire document should be restructured with a concise overview pointing to separate reference files for templates, API implementation, and field mappings.
Suggestions
Extract ADF templates into a separate TEMPLATES.md file and replace inline with compact descriptions (e.g., 'Create ADF doc with sections: Business Outcome, Success Metrics, Scope') - Claude knows how to construct ADF JSON.
Consolidate the Next-Gen vs Classic differences into a single reference table instead of repeating the distinction in the comparison table, templates, custom fields section, and issue link types section.
Move API implementation functions and bulk operations into a separate API.md reference file, keeping only a brief workflow overview in the main skill file.
Add a validation step after bulk/batch operations (e.g., verify created issues exist and have correct parent links) and add a dry-run or confirmation step to the bulk delete function.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content 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 places (comparison table, templates, custom fields section, issue link types). The bulk delete function and error handling are tangential to the SAFe skill purpose. | 1 / 3 |
Actionability | The skill provides fully executable JavaScript code with proper API endpoints, 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 → create stories → create subtasks) with error handling, but there's no validation checkpoint after creation (e.g., verifying the parent link was established correctly). The bulk delete function lacks any confirmation or dry-run step, which is a destructive operation missing validation. | 2 / 3 |
Progressive Disclosure | Everything is crammed into a single monolithic file with no references to separate files for detailed content. The ADF templates, API implementation, custom field reference tables, and best practices could all be split into separate referenced documents. The file is far too long for a SKILL.md overview. | 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
e437c3c
- 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.