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.
74
67%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./data/skills-md/01000001-01001110/agent-jira-skills/jira-spaces/SKILL.mdQuality
Discovery
85%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 well-structured skill description that clearly communicates what the skill does and when to use it. It names specific actions (create, list, delete) and includes an explicit 'Use when' clause. The main weakness is that trigger term coverage could be broader to capture more natural user language variations.
Suggestions
Add more natural trigger term variations users might say, such as 'wiki', 'knowledge base', 'workspace', or 'Confluence site' to improve discoverability.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Create, list, and delete spaces with templates.' Also specifies the domain clearly as Confluence spaces for project documentation. | 3 / 3 |
Completeness | Clearly answers both 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 explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes relevant keywords like 'Confluence', 'spaces', 'project documentation', and 'templates', but misses common variations users might say such as 'wiki', 'knowledge base', 'workspace', or 'content management'. Coverage is decent but not comprehensive. | 2 / 3 |
Distinctiveness Conflict Risk | The description is clearly scoped to Confluence spaces specifically, which is a distinct niche. The mention of 'spaces', 'templates', and 'Confluence' makes it unlikely to conflict with general documentation or other wiki/CMS skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a solid reference for Confluence space management with concrete API examples and good error handling documentation. However, it lacks validation workflows for destructive operations (deletion), references undefined helper functions in common patterns, and could be more concise by trimming response bodies and obvious content. The structure would benefit from splitting the detailed API reference into a separate file.
Suggestions
Add an explicit validation workflow for space deletion: list space contents first, require confirmation, verify deletion completed (check for 404 on the space key after async deletion).
Either define the helper functions (createSpace, createPage, listSpaces) inline or point to a specific file where they are implemented, so the 'Common Patterns' section is truly executable.
Move the full API reference (endpoints table, request/response examples) to a separate REFERENCE.md file and keep SKILL.md as a concise overview with quick-start examples.
Remove the 'When to Use' and 'Space Types' sections—Claude can infer these—to reduce token usage.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary content like the 'When to Use' section and the space types table which Claude could infer, but overall is reasonably focused. The full request/response examples for listing and creating are useful but the response JSON bodies could be trimmed. | 2 / 3 |
Actionability | The TypeScript code examples are concrete and near-executable, but helper functions like `createSpace`, `createPage`, and `listSpaces` are referenced without definitions, making the 'Common Patterns' section pseudocode-like. The bash scripts reference `node run.js` without explaining where these scripts live or how they're set up. | 2 / 3 |
Workflow Clarity | The deletion operation is destructive and only has a WARNING label but no explicit validation/confirmation workflow (e.g., list contents first, confirm, then delete, then verify). The 'Common Patterns' section shows a multi-step create-and-populate flow but lacks validation checkpoints. Per rubric, missing feedback loops for destructive operations caps this at 2. | 2 / 3 |
Progressive Disclosure | The content is reasonably structured with clear sections and tables, but it's a long monolithic file (~150 lines of substantive content) that could benefit from splitting the API reference and common patterns into separate files. The 'Related Skills' section provides cross-references, but the inline API reference table and full request/response examples could be externalized. | 2 / 3 |
Total | 8 / 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.