confluence-automation
Automate Confluence page creation, content search, space management, labels, and hierarchy navigation via Rube MCP (Composio). Always search tools first for current schemas.
74
65%
Does it follow best practices?
Impact
90%
1.73xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/all-skills/skills/confluence-automation/SKILL.mdQuality
Discovery
67%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description is strong in specificity and distinctiveness, clearly identifying Confluence-related operations and the integration mechanism. Its main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill. Trigger terms could also be expanded to include common user language variations.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Confluence pages, wiki content, Atlassian knowledge bases, or managing Confluence spaces.'
Include natural user-facing trigger terms like 'wiki', 'Atlassian', 'knowledge base', 'Confluence page', or 'wiki page' to improve matching against common user phrasing.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'page creation, content search, space management, labels, and hierarchy navigation'. Also specifies the integration method (Rube MCP / Composio) and includes a procedural note about searching tools first. | 3 / 3 |
Completeness | Clearly answers 'what does this do' with specific Confluence operations, but lacks an explicit 'Use when...' clause or equivalent trigger guidance. The when is only implied by the capabilities listed, which caps this at 2 per the rubric guidelines. | 2 / 3 |
Trigger Term Quality | Includes relevant keywords like 'Confluence', 'page creation', 'content search', 'space management', 'labels', and 'hierarchy navigation'. However, it misses common user variations like 'wiki', 'Atlassian', 'knowledge base', or 'Confluence page' as a phrase users might naturally say. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific mention of 'Confluence', 'Rube MCP (Composio)', and Confluence-specific operations like space management and hierarchy navigation. Unlikely to conflict with other skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
62%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 Confluence automation skill with clear workflow sequences and good pitfall documentation, but it suffers from redundancy (pitfalls repeated in multiple sections) and lacks concrete executable examples showing actual tool invocation payloads. The content would benefit from deduplication and splitting detailed reference material into separate files.
Suggestions
Add at least one concrete tool invocation example per workflow showing the exact parameter structure/JSON payload passed to the tool (e.g., a complete CONFLUENCE_CREATE_PAGE call with all required params filled in).
Deduplicate the pitfalls — consolidate the per-workflow pitfalls and the 'Known Pitfalls' section into a single location to reduce redundancy and save ~40 lines.
Split the CQL reference (operators, fields, functions), content formatting guide, and quick reference table into separate bundle files, keeping SKILL.md as a concise overview with links.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably well-organized but contains significant redundancy — the 'Known Pitfalls' section largely repeats pitfalls already listed under each workflow section. The Quick Reference table adds value but the overall document could be tightened by ~30% without losing information. Some explanations (e.g., pagination styles, content formatting basics) are things Claude already knows. | 2 / 3 |
Actionability | The skill provides clear tool sequences and parameter names, which is good. However, there are no executable code examples or concrete tool invocation examples showing exact parameter structures/JSON payloads. The guidance is specific about tool names and parameters but stops short of copy-paste ready invocations. The CQL examples are a bright spot but most workflows remain at the 'list of steps' level. | 2 / 3 |
Workflow Clarity | Workflows are clearly sequenced with numbered steps, each tool annotated with its role (Prerequisite, Required, Optional, Fallback). The update workflow explicitly includes a validation checkpoint (fetch current version before updating, version conflict handling). The pitfalls sections serve as error recovery guidance. The setup section has a clear prerequisite verification flow. | 3 / 3 |
Progressive Disclosure | The content is a monolithic single file with no bundle files to reference. While internally well-structured with clear sections and a quick reference table, the document is quite long (~200+ lines) and could benefit from splitting detailed CQL reference, content formatting guide, and pitfalls into separate files. The external link to Composio docs is helpful but doesn't compensate for the inline bulk. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- davepoon/buildwithclaude
- Commit
d065ead
- 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.