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 provides explicit trigger guidance. The main weakness is that trigger term coverage could be broader to capture more natural user language variations.
Suggestions
Add common user-facing synonyms like 'wiki', 'knowledge base', or 'workspace' to improve trigger term coverage for users who may not use the exact term 'spaces'.
| 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 terms 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 | 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 code examples and good error documentation, but suffers from being overly comprehensive in a single file without supporting bundle files. The destructive delete operation lacks proper validation workflows, and several referenced helpers and scripts are undefined, reducing true actionability.
Suggestions
Add explicit validation steps for the delete workflow: verify space exists, list content count, require confirmation before proceeding, and check for async completion status.
Either provide the implementations of helper functions (createSpace, createPage, listSpaces) or replace the Common Patterns section with fully self-contained fetch-based examples.
Move the full API reference table, error handling table, and response examples into a separate REFERENCE.md file, keeping SKILL.md as a concise quick-start with links to details.
Remove or trim content Claude already knows (space type descriptions, basic auth explanation, space key character rules) to reduce token usage.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary content like the space types table and space key conventions that Claude would already know or could infer. The response examples are helpful but verbose - showing full JSON responses adds bulk. The API reference table duplicates information that's demonstrated in the code examples below. | 2 / 3 |
Actionability | The TypeScript code examples are concrete and mostly executable, but helper functions like `createSpace`, `createPage`, and `listSpaces` are referenced without definitions, making the 'Common Patterns' section pseudocode-like. The bash usage examples reference `node run.js` scripts that aren't provided or explained. | 2 / 3 |
Workflow Clarity | The deletion operation is flagged with a WARNING but lacks an explicit validation/confirmation workflow (e.g., verify space exists first, check content count, confirm before proceeding). The 'Create Project Documentation Space' pattern shows a sequence but has no error handling or validation checkpoints between steps. For destructive operations like delete, the missing feedback loop caps this at 2. | 2 / 3 |
Progressive Disclosure | The content is reasonably structured with clear headers, but it's monolithic - the full API reference, all code examples, error tables, and usage examples are all inline. No bundle files exist to offload detailed content to, and the references to related skills and scripts suggest structure that isn't actually present. | 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
aa009ea
- 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.