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.

1.73x

Quality

72%

Does it follow best practices?

Impact

90%

1.73x

Average score across 3 eval scenarios

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/all-skills/skills/confluence-automation/SKILL.md

Quality

Content

57%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-organized, highly actionable API reference for Confluence operations with useful pitfalls. Its weaknesses are duplicated pitfall content, missing verification steps for destructive operations, and no use of separate reference files to keep SKILL.md lean.

Suggestions

Remove the duplicated 'Known Pitfalls' section (or the per-workflow Pitfalls blocks) so each pitfall appears once.

Add verification checkpoints after destructive operations, e.g. re-fetch the page with GET_PAGE_BY_ID to confirm the update applied, and a confirmation step before DELETE_PAGE.

Move the Quick Reference table and the CQL field/operator reference into a references/ file (e.g., references/tool-reference.md) and link to it from SKILL.md.

Dimension	Reasoning	Score
Conciseness	The guidance is dense and factual, but the 'Known Pitfalls' section repeats items already stated in each workflow's Pitfalls (version+1, storage format, numeric IDs, CREATE/UPDATE body nesting, rate limits) and the Quick Reference table re-lists tools, so it could be meaningfully tightened.	3 / 5
Actionability	Concrete tool slugs, exact parameters with example values, and example CQL strings make the workflows mostly executable, but no example request payloads (e.g., a full CREATE_PAGE body) are given, leaving minor gaps.	4 / 5
Workflow Clarity	Sequences are clearly ordered with prerequisite markers, but destructive operations (UPDATE_PAGE, DELETE_PAGE) lack post-operation verification steps, which caps workflow clarity at 3 per the rubric's destructive/batch-operations rule.	3 / 5
Progressive Disclosure	The body is well-sectioned but is ~200 lines of tool reference kept entirely inline; the Quick Reference table and CQL field/operator details would naturally live in a separate reference file, matching the 'content that should be separate is inline' anchor.	3 / 5
	Total	13 / 20 Passed

Description

75%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A specific, distinct, third-person description that enumerates concrete capabilities. Its main weakness is the absence of any 'Use when...' trigger guidance and limited synonym coverage.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the user mentions Confluence, Atlassian, wiki pages, or wants to create/search/update Confluence documentation.'

Add natural synonym terms users might say (Atlassian, wiki, documentation, space) to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	"page creation, content search, space management, labels, and hierarchy navigation" lists multiple specific concrete actions covering the full Confluence domain, matching the comprehensive-coverage anchor.	5 / 5
Completeness	The description has a clear 'what' but no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric guidelines.	3 / 5
Trigger Term Quality	"Confluence", "page creation", "content search", "labels" are natural user phrases, but common synonyms like "Atlassian", "wiki", or "documentation" are missing, so coverage is good rather than comprehensive.	4 / 5
Distinctiveness Conflict Risk	"via Rube MCP (Composio)" plus Confluence-specific operations carve out a clear niche with distinct triggers and minimal conflict risk with other skills.	5 / 5
	Total	17 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: davepoon/buildwithclaude
Path: plugins/all-skills/skills/confluence-automation/SKILL.md
Commit: 10bfc43

Reviewed: 7 days ago

Table of Contents

Discovery Implementation Validation

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.