jira-safe

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

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

65%

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

The content is highly actionable with executable code and concrete SAFe templates, but it is monolithic with redundant Next-Gen/Classic information repeated across sections and a destructive bulk-delete operation lacking validation safeguards.

Suggestions

Consolidate the Next-Gen vs Classic differences into a single canonical table and reference it from the template and link sections instead of restating the distinctions four times.

Add a validation/confirmation step to bulkDeleteIssues (e.g., dry-run count, explicit confirmation, or scoped JQL preview) before performing the destructive delete loop.

Move the full API implementation functions and ADF template blobs into reference files (e.g., references/templates.md, references/api.md) and keep SKILL.md as a concise overview with one-level-deep links.

Dimension	Reasoning	Score
Conciseness	The body is lean and avoids explaining concepts Claude knows, but the Next-Gen vs Classic distinction is restated across four sections (comparison table, templates, issue link types, and custom fields), adding redundancy that could be tightened.	2 / 3
Actionability	Provides fully executable JavaScript with real endpoints (/rest/api/3/issue), concrete field names, and copy-paste-ready ADF description structures rather than pseudocode.	3 / 3
Workflow Clarity	Create functions have numbered steps and inline error handling, but bulkDeleteIssues is a destructive batch operation with no validation checkpoint, preview, or confirmation, which caps workflow clarity at 2 per the rubric guideline.	2 / 3
Progressive Disclosure	The ~440-line SKILL.md is a single monolithic file with no bundle files; full API implementations and verbose ADF templates that should be split into reference files are inline, though sections are clearly organized.	2 / 3
	Total	9 / 12 Passed

Description

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.

The description is concise, third-person, and explicitly covers both capabilities and use triggers with SAFe-specific vocabulary. It is a strong example with no notable weaknesses.

Dimension	Reasoning	Score
Specificity	Names the domain ('Implement SAFe methodology in Jira') and lists multiple concrete actions ('creating Epics, Features, Stories with proper hierarchy, acceptance criteria, and parent-child linking'), matching the anchor for listing multiple specific concrete actions.	3 / 3
Completeness	Explicitly answers both 'what' (Implement SAFe methodology in Jira) and 'when' ('Use when creating Epics, Features, Stories...'), with an explicit trigger clause rather than implied timing.	3 / 3
Trigger Term Quality	Uses natural SAFe/Jira vocabulary a user would say ('Epics, Features, Stories', 'hierarchy', 'acceptance criteria', 'parent-child linking') with good coverage and no common variations missing.	3 / 3
Distinctiveness Conflict Risk	'SAFe methodology in Jira' with Epic/Feature/Story triggers carves a clear niche unlikely to overlap with or trigger unrelated skills.	3 / 3
	Total	12 / 12 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
Commit: ff6a653

Reviewed: 5 days 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.