jira-safe

Implement SAFe methodology in Jira. Use when creating Epics, Features, Stories with proper hierarchy, acceptance criteria, and parent-child linking.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./data/skills-md/01000001-01001110/agent-jira-skills/jira-safe/SKILL.md

Quality

Content

65%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

Highly actionable with strong executable code, but weakened by redundancy (repeated Next-Gen caveats, re-explained SAFe basics) and a destructive bulk-delete workflow lacking validation checkpoints. Splitting templates/reference into bundle files would improve progressive disclosure.

Suggestions

Add a confirmation/validation checkpoint before bulkDeleteIssues runs (e.g., require an explicit dry-run count and user confirmation) so the destructive workflow clears the workflow_clarity cap.

De-duplicate the Next-Gen vs Classic caveats: state the parent-field and 'Subtask' naming rules once in the comparison table and reference it from the templates instead of repeating inline.

Move the Epic/Story/Subtask templates and the custom-field tables into separate reference files (e.g., references/templates.md) and summarize them in SKILL.md to reduce the monolithic footprint.

Dimension	Reasoning	Score
Conciseness	Mostly efficient code-focused content, but the Next-Gen caveat ('NOT customfield_10014', 'Subtask not Sub-task') is repeated across 3+ locations, and the SAFe Best Practices section re-explains INVEST and Given-When-Then that Claude already knows.	3 / 5
Actionability	Fully executable, copy-paste-ready JavaScript covering the common cases (create epic with stories, story with subtasks, bulk delete, find epic-link field) with complete fetch payloads and ADF structures.	5 / 5
Workflow Clarity	Sequences are clearly numbered, but the destructive/batch bulkDeleteIssues operation has no validation or confirmation checkpoint, capping this dimension at 3 per the rubric.	3 / 5
Progressive Disclosure	Section headers and tables provide some structure, but the ~450-line file is monolithic with no bundle files; templates and API reference that could live in separate files are inlined, and only external URLs are referenced.	3 / 5
	Total	14 / 20 Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, well-scoped description that clearly states both capability and trigger conditions with concrete SAFe/Jira terminology. Minor improvements would come from mentioning subtasks/tasks to round out coverage.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions — 'creating Epics, Features, Stories with proper hierarchy, acceptance criteria, and parent-child linking' — but omits subtasks/tasks, leaving minor coverage gaps.	4 / 5
Completeness	Explicitly answers both what ('Implement SAFe methodology in Jira') and when ('Use when creating Epics, Features, Stories...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural terms users would say ('Epics', 'Features', 'Stories', 'SAFe', 'Jira', 'acceptance criteria') are present, though a few common synonyms ('subtasks', 'tasks') are missing.	4 / 5
Distinctiveness Conflict Risk	'SAFe methodology in Jira' is a clear niche with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	18 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: NeverSight/skills_feed
Path: data/skills-md/01000001-01001110/agent-jira-skills/jira-safe/SKILL.md
Commit: 2f57aec

Reviewed: about 23 hours ago

Table of Contents

Discovery Implementation Validation

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.