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.
80
Quality
75%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Optimize this skill with Tessl
npx tessl skill review --optimize ./data/skills-md/01000001-01001110/agent-jira-skills/jira-spaces/SKILL.mdDiscovery
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-crafted skill description that clearly defines its scope around Confluence space management with specific actions and explicit usage triggers. The main weakness is limited trigger term coverage - users might search for related terms like 'wiki', 'Atlassian', or 'knowledge base' that aren't captured.
Suggestions
Add common alternative terms users might use: 'wiki', 'knowledge base', 'Atlassian', or 'content organization'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Create, list, and delete spaces with templates' - these are clear, actionable operations on a specific platform (Confluence). | 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 missing common variations users might say like 'wiki', 'knowledge base', 'content management', or 'Atlassian'. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with 'Confluence spaces' as a clear niche - unlikely to conflict with general documentation skills or other wiki tools due to specific platform and operation mentions. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides solid, actionable API documentation with executable code examples and clear endpoint references. However, it could be more concise by removing sections Claude can infer, and the workflow for destructive operations (delete) lacks explicit validation/verification steps. The monolithic structure would benefit from splitting detailed API reference into a separate file.
Suggestions
Add explicit verification step after space deletion to check async completion status (poll for 404 or check long-running task)
Remove or condense the 'When to Use' section - Claude can infer appropriate usage from the skill description
Split the detailed API reference table and error handling into a separate REFERENCE.md file, keeping SKILL.md as a quick-start overview
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary content like the 'When to Use' section (Claude can infer this) and verbose tables that could be condensed. The space types and conventions sections add value but could be tighter. | 2 / 3 |
Actionability | Provides fully executable TypeScript code examples with complete request/response pairs. The bash usage examples are copy-paste ready, and the API endpoints are clearly documented with methods and descriptions. | 3 / 3 |
Workflow Clarity | The 'Common Patterns' section shows a sequence for creating project documentation, but lacks explicit validation checkpoints. The delete operation has a warning but no verification step to confirm deletion succeeded or handle async completion. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but everything is inline in one file. The 'Related Skills' section provides cross-references, but the API reference and common patterns could be split into separate files for a skill of this length (~150 lines). | 2 / 3 |
Total | 9 / 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.
- 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.