Automate Confluence page creation, content search, space management, labels, and hierarchy navigation via Rube MCP (Composio). Always search tools first for current schemas.
Install with Tessl CLI
npx tessl i github:davepoon/buildwithclaude --skill confluence-automation74
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillEvaluation — 90%
↑ 1.73xAgent success when using this skill
Validation for skill structure
Discovery
50%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 effectively lists specific Confluence capabilities and is clearly distinguishable due to the product-specific focus. However, it critically lacks any 'Use when...' guidance to help Claude know when to select this skill, and could benefit from more natural user trigger terms beyond the technical Confluence terminology.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user mentions Confluence, wiki pages, Atlassian documentation, or needs to manage team knowledge bases'
Include common user variations and synonyms such as 'wiki', 'knowledge base', 'Atlassian', 'team documentation' to improve trigger term coverage
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'page creation, content search, space management, labels, and hierarchy navigation'. These are distinct, actionable capabilities. | 3 / 3 |
Completeness | Describes what the skill does but completely lacks a 'Use when...' clause or equivalent explicit trigger guidance. The rubric states missing 'Use when' should cap completeness at 2, and this has no when guidance at all. | 1 / 3 |
Trigger Term Quality | Includes 'Confluence' which is a strong trigger term, plus domain terms like 'page creation', 'space management', 'labels'. However, missing common user variations like 'wiki', 'documentation', 'Atlassian', or file-type references. | 2 / 3 |
Distinctiveness Conflict Risk | 'Confluence' is a highly specific product name that creates a clear niche. The mention of 'Rube MCP (Composio)' further distinguishes this from generic document management skills. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
77%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, highly actionable skill for Confluence automation with clear workflows and comprehensive parameter documentation. The main weaknesses are some redundancy in pitfall documentation and the monolithic structure that could benefit from progressive disclosure to separate reference material. The concrete tool sequences and validation checkpoints make this immediately usable.
Suggestions
Consolidate duplicate pitfall information - the same warnings appear in workflow sections and the 'Known Pitfalls' section; keep pitfalls inline with workflows and remove the redundant section
Consider extracting the CQL operators/fields reference and content formatting guide into separate reference files to reduce the main skill length
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some redundancy - pitfalls are repeated across sections and in a dedicated 'Known Pitfalls' section. The content is mostly efficient but could be tightened by consolidating duplicate information. | 2 / 3 |
Actionability | Provides concrete tool sequences with specific parameter names, exact CQL syntax examples, and clear step-by-step workflows. The quick reference table and detailed parameter documentation make this highly actionable. | 3 / 3 |
Workflow Clarity | Each workflow has numbered steps with clear prerequisites marked, validation checkpoints (e.g., 'always fetch current version first'), and explicit sequencing. The 'When to use' headers and tool sequence annotations provide excellent clarity. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but everything is in a single file. The skill is quite long (~300 lines) and could benefit from splitting detailed CQL reference, content formatting guide, or pitfalls into separate files with clear navigation. | 2 / 3 |
Total | 10 / 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 | |
Table of Contents
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.