CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

59

Quality

69%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/confluence-automation/SKILL.md

The canonical home for this skill is confluence-automation in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

63%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.

The content is a well-structured, actionable reference for orchestrating Confluence MCP tools, with clear sequences and useful pitfalls. It loses points for redundancy between inline and Known Pitfalls sections, absent feedback loops for destructive operations, and no progressive disclosure into reference files despite its length.

Suggestions

Remove the duplicated "Known Pitfalls" section or convert the inline per-workflow pitfalls into pointers to it, and delete the non-instructive final "When to Use" line.

Add an explicit validation/feedback step for destructive operations (e.g. confirm resolved page ID and version before DELETE_PAGE / UPDATE_PAGE, with a retry on failure).

Move the CQL operator/field reference and the full quick-reference table into a separate reference file (e.g. references/confluence-reference.md) linked from the body to improve progressive disclosure.

DimensionReasoningScore

Conciseness

The body is mostly efficient reference material, but the "Known Pitfalls" section duplicates per-workflow pitfalls and the closing "When to Use" line is filler that could be trimmed.

3 / 5

Actionability

Concrete tool slugs, sequenced calls, named parameters, an example CQL query, and a task-to-tool quick-reference table give mostly executable guidance with only minor gaps.

4 / 5

Workflow Clarity

Numbered tool sequences with several checkpoints (confirm ACTIVE connection, fetch version before update, verify page ID) are clear, though no explicit validate-fix-retry feedback loop exists and DELETE_PAGE lacks a verification step.

4 / 5

Progressive Disclosure

Section structure is good, but with no bundle files the 211-line document inlines reference material (CQL operator reference, quick-reference table, parameter docs) that could be split into separate files, and pitfalls content is repeated.

3 / 5

Total

14

/

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.

The description is specific and distinct, naming concrete Confluence actions scoped to the Rube/Composio MCP. Its main weakness is the missing explicit "Use when..." trigger guidance, which limits the completeness score.

Suggestions

Add an explicit "Use when..." clause naming natural triggers, e.g. "Use when managing Confluence pages, spaces, labels, or searching content with CQL."

Include a couple of synonyms or surface variants users might say (e.g. "wiki", "Atlassian") to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

"Confluence page creation, content search, space management, labels, and hierarchy navigation" lists multiple concrete, comprehensive actions rather than vague language.

5 / 5

Completeness

The description gives a clear "what" but lacks an explicit "Use when..." trigger clause, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

"Confluence", "page creation", "content search", "space management", and "labels" are natural user terms, but synonyms or file-extension variants are missing.

4 / 5

Distinctiveness Conflict Risk

"via Rube MCP (Composio)" scoped to Confluence carves out a clear niche with minimal overlap risk against other skills.

5 / 5

Total

17

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.