Name: confluence
Rating: 55.2 (1 reviews)
Author: membranedev

confluence

Confluence integration. Manage document management data, records, and workflows. Use when the user wants to interact with Confluence data.

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/confluence/SKILL.md

Quality

Content

68%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 highly actionable with concrete, copy-paste Membrane CLI commands and a well-structured connection-state workflow. Its main weaknesses are a padded introductory paragraph explaining Confluence and the absence of validation guidance for destructive delete operations, which caps workflow clarity.

Suggestions

Remove or condense the opening 'Confluence is a team collaboration...' paragraph; Claude already knows what Confluence is.

Add a validation/verification checkpoint around destructive actions, e.g. 'Before delete-page, run get-page to confirm the ID; after deleting, list-pages to verify removal.'

Resolve the dangling 'Step 2' reference (referenced but never labeled) so the connection → action workflow is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient CLI commands and a useful action table, but the opening paragraph ('Confluence is a team collaboration and document management tool... Think of it as a central hub...') explains what Confluence is — something Claude already knows — fitting 'mostly efficient but includes some unnecessary explanation or could be tightened'.	3 / 5
Actionability	It provides copy-paste-ready commands for every common case (install, login, connection ensure, action list/run, request proxy) plus a concrete 20-row action table with keys, matching 'fully executable; copy-paste ready code or commands; specific examples cover the common cases'.	5 / 5
Workflow Clarity	The connection setup has a strong state machine with an explicit poll-after-action feedback loop, but destructive operations (delete-page, delete-blog-post) are listed with no validation/verification step, triggering the rubric cap that workflow clarity cannot exceed 3 for destructive/batch skills missing validation.	3 / 5
Progressive Disclosure	No bundle files exist and the single SKILL.md is organized into clear, well-labeled sections (Overview, Working with Confluence, Popular actions, Proxy, Best practices) with no nested references, fitting 'good structure; most content appropriately placed; minor organization gaps' — the 20-row action table is reasonable inline but borders on reference material.	4 / 5
	Total	15 / 20 Passed

Description

57%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 correctly uses third person and includes an explicit 'Use when...' trigger, but its actions are generic ('Manage ...') and its trigger keywords lack the natural variations (pages, spaces, blog posts) users actually say. It is distinct because it names Confluence specifically, yet under-specific on capabilities.

Suggestions

Replace the generic verb 'Manage' with concrete actions, e.g. 'Create, list, update, and delete Confluence pages, blog posts, spaces, comments, and attachments.'

Expand the trigger phrase to surface natural keywords: 'Use when the user wants to work with Confluence pages, spaces, blog posts, comments, or attachments.'

Tighten 'document management data, records, and workflows' to Confluence-specific nouns so the niche reads as unambiguously Confluence rather than generic document management.

Dimension	Reasoning	Score
Specificity	It names the domain ('Confluence integration', 'document management data, records, and workflows') but the only verb is the generic 'Manage', with no concrete actions like create/list/update pages or spaces, matching the 'names domain but actions are minimal or generic' anchor rather than the 3-anchor which requires 1-2 concrete actions.	2 / 5
Completeness	It explicitly answers both what ('Manage document management data, records, and workflows') and when ('Use when the user wants to interact with Confluence data'), but the trigger phrase is generic rather than concrete, matching 'has both what and when; when could be more explicit or specific'.	4 / 5
Trigger Term Quality	The natural keyword 'Confluence' appears twice, but common variations a user would actually say (pages, spaces, blog posts, wiki) are absent, fitting 'some relevant keywords but missing common variations or synonyms'.	3 / 5
Distinctiveness Conflict Risk	'Confluence integration' names a specific product giving it a clear niche with minimal conflict risk, but the generic 'interact with Confluence data' trigger leaves minor overlap risk with closely related wiki/document skills, fitting 'mostly distinct; minor overlap risk'.	4 / 5
	Total	13 / 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: membranedev/application-skills
Path: skills/confluence/SKILL.md
Commit: f484c82

Reviewed: 4 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.