jira-spaces

Manage Confluence spaces for project documentation. Create, list, and delete spaces with templates. Use when setting up project documentation structure or managing Confluence content areas.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

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 body is highly actionable with executable code and clear error guidance, but it is padded with redundant examples, lacks verification steps around the destructive delete, and references scripts that are absent from the bundle.

Suggestions

Add an explicit validation/verification loop to the delete workflow: confirm the space exists, optionally check it has no critical content, and verify the async (202) deletion actually completed.

Move the bulk API reference (endpoints, response shapes, space-key rules) into a separate reference file and keep SKILL.md as a lean overview with one-level-deep links.

Trim concepts Claude already knows and consolidate the near-identical fetch snippets into a single reusable pattern rather than repeating the full auth/header boilerplate per operation.

Dimension	Reasoning	Score
Conciseness	Mostly reference-style and efficient, but it pads with concepts Claude already knows ("Spaces are the top-level containers for organizing project documentation, wikis, and knowledge bases") and near-identical boilerplate fetch snippets.	2 / 3
Actionability	Provides executable fetch snippets with concrete headers and bodies, a space-key validation ruleset, an error-to-resolution table, and copy-paste `node run.js` usage examples.	3 / 3
Workflow Clarity	Operations are shown as isolated calls with a WARNING on the destructive delete, but there is no verification checkpoint (e.g., confirm existence, verify async 202 deletion completed), which caps destructive-operation workflows at 2.	2 / 3
Progressive Disclosure	Sections are organized, but the ~215-line body is a monolithic mix of API reference, types, patterns, and errors that could be split into reference files, and it lists scripts (create-space, delete-space, list-spaces) that do not exist on disk.	2 / 3
	Total	9 / 12 Passed

Description

75%

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 solid description with explicit what-and-when guidance and a distinct Confluence-space niche. Its main weakness is trigger-term breadth and an action list that under-represents the skill's documented capabilities.

Suggestions

Broaden trigger terms to include natural phrasings users would say, e.g. "Confluence", "wiki", or "set up Confluence documentation".

Expand the action list to reflect more of the skill's actual capabilities (e.g., space types, content listing) without padding.

Dimension	Reasoning	Score
Specificity	"Create, list, and delete spaces with templates" names several concrete actions on a clear domain, but stops short of the broader action catalog (no archive, permissions, or page handling) seen in the level-3 example.	2 / 3
Completeness	It explicitly answers both what ("Manage Confluence spaces... Create, list, and delete") and when ("Use when setting up project documentation structure or managing Confluence content areas").	3 / 3
Trigger Term Quality	"Confluence spaces", "project documentation", and "Confluence content areas" are natural, relevant terms, but coverage omits common user phrasings like "Confluence", "wiki", or "set up documentation".	2 / 3
Distinctiveness Conflict Risk	Scoping to "Confluence spaces" with explicit Confluence triggers gives it a clear niche unlikely to fire for unrelated skills.	3 / 3
	Total	10 / 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.