Search and manage Confluence pages and spaces using CQL, read/create/update pages with Markdown support. Use when working with Confluence documentation.
83
83%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
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-crafted skill description that clearly identifies the Confluence platform, lists specific capabilities (search, manage, CRUD operations), and includes an explicit 'Use when' clause. The main weakness is limited trigger term coverage - users might describe their need using terms like 'wiki' or 'knowledge base' that aren't captured.
Suggestions
Expand trigger terms to include common synonyms like 'wiki', 'knowledge base', 'Atlassian', or 'company documentation'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Search and manage', 'read/create/update pages', 'Markdown support', and mentions CQL for searching. These are concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('Search and manage Confluence pages and spaces using CQL, read/create/update pages with Markdown support') and when ('Use when working with Confluence documentation') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes 'Confluence', 'pages', 'spaces', 'CQL', and 'documentation' but misses common variations users might say like 'wiki', 'knowledge base', 'Atlassian', or 'company docs'. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with 'Confluence' and 'CQL' as unique identifiers. Unlikely to conflict with other documentation skills due to the specific platform mention. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill with excellent actionability and progressive disclosure. Commands are concrete and executable with clear examples. The main weaknesses are some verbosity in explanations and missing explicit validation workflows for write operations, though the check command provides good initial setup validation.
Suggestions
Tighten the authentication section by removing redundant explanations - the config file example already shows the structure clearly
Add explicit validation steps for page create/update workflows (e.g., 'verify page exists after creation' or 'check version number incremented')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary verbosity, such as explaining what the check command validates in multiple places and repeating authentication setup details. Some sections could be tightened. | 2 / 3 |
Actionability | Provides fully executable commands throughout with specific examples, copy-paste ready bash commands, and concrete configuration file examples. Every command includes clear syntax and arguments. | 3 / 3 |
Workflow Clarity | Setup workflow is clear with check command for validation, but the skill lacks explicit validation checkpoints for content creation/update operations. The troubleshooting section helps but feedback loops for error recovery are implicit rather than explicit. | 2 / 3 |
Progressive Disclosure | Excellent structure with clear overview, well-signaled one-level-deep references to creating-content.md and permissions.md, and logical organization. Content is appropriately split between main skill and reference files. | 3 / 3 |
Total | 10 / 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