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

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

67%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.

A competent, well-structured API skill with executable REST examples and proper destructive-operation confirmation. The main weaknesses are redundancy across sections, helper functions and scripts referenced but not provided, and minor over-explanation that could be trimmed.

Suggestions

Provide the referenced scripts in ./scripts/ (create-space, delete-space, list-spaces) or remove the Scripts table and `node run.js` usage examples so commands are actually runnable.

Either define or remove the undefined helpers in Common Patterns (createSpace, createPage, listSpaces) so the patterns are executable rather than pseudocode.

Consolidate the redundant create/list/delete coverage (Scripts table, Usage Examples, and Common Patterns) into a single section to reduce token overhead.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete request/response examples, but it repeats create/list/delete across the Scripts table, Usage Examples, and a Common Patterns section that uses undefined helper functions, so it could be tightened.	3 / 5
Actionability	Full fetch-based REST calls with headers, bodies, and response payloads are copy-paste ready, but the referenced scripts (create-space, list-spaces, delete-space) do not exist as bundle files and Common Patterns invokes undefined helpers like createSpace/createPage.	4 / 5
Workflow Clarity	Each operation has a clear request/response sequence and the destructive DELETE is gated by a WARNING plus interactive confirmation / --confirm flag, so the destructive-operation validation cap is not triggered; minor gaps are no verify-contents-before-delete or post-delete verification.	4 / 5
Progressive Disclosure	The single SKILL.md is well organized into clear sections (When to Use, API Reference, Error Handling, etc.) appropriate for its scope, though the detailed API request/response blocks could optionally be split into a reference file and the referenced scripts are absent from the bundle.	4 / 5
	Total	15 / 20 Passed

Description

83%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-structured description that clearly states both capabilities and trigger conditions in third person. Minor weaknesses are the unbacked "with templates" claim, a missing update action, and the misleading Jira-prefixed skill name.

Dimension	Reasoning	Score
Specificity	"Create, list, and delete spaces with templates" names several concrete actions on a clearly identified domain (Confluence spaces), but the coverage has a minor gap (no update/rename) and the "with templates" claim is not reflected in the body's create example.	4 / 5
Completeness	It explicitly states what ("Manage Confluence spaces... Create, list, and delete spaces with templates") and when ("Use when setting up project documentation structure or managing Confluence content areas") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural terms like "Confluence spaces", "project documentation", and "Confluence content areas" are present, but common synonyms such as "wiki" are missing and no file-extension-style tokens apply to this web service.	4 / 5
Distinctiveness Conflict Risk	The "Confluence spaces" niche is mostly distinct from sibling jira/confluence skills, but the skill name "jira-spaces" (Jira vs Confluence) and overlap with related documentation skills introduce minor conflict risk.	4 / 5
	Total	17 / 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/learn-skills.dev
Path: data/skills-md/01000001-01001110/agent-jira-skills/jira-spaces/SKILL.md
Commit: d725a6d

Reviewed: ~16 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.