publish-to-confluence

Publish any markdown file from the vault to Confluence with format conversion and approval gate

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/publish-to-confluence/SKILL.md

Quality

Content

77%

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

The body is highly actionable with a clear, well-validated multi-phase workflow and concrete API/conversion details. Its weaker spots are minor internal redundancy and a monolithic structure that keeps reference-grade detail inline rather than in separate files.

Suggestions

Move the detailed conversion table and REST API request bodies into a reference file (e.g., references/confluence-api.md) and link to it from the main flow to improve progressive disclosure.

Remove duplicated guidance such as the repeated strip-YAML-frontmatter note and trim the low-value "Agent Mode Awareness" section to tighten conciseness.

Dimension	Reasoning	Score
Conciseness	The body is mostly operational and free of concepts Claude already knows, but it includes some redundancy (e.g., strip-YAML-frontmatter stated in both the table and the notes) and marginal sections like "Agent Mode Awareness" that could be tightened.	2 / 3
Actionability	Guidance is concrete and copy-paste ready: a markdown-to-XHTML conversion table, full REST API request bodies with headers, and exact shell commands like `date '+%Y-%m-%d %H:%M'`.	3 / 3
Workflow Clarity	Phases 1–6 are clearly sequenced with an explicit approval-gate checkpoint ("Wait for explicit yes") and error-recovery feedback loops (e.g., HTTP 409 → fetch latest version and retry).	3 / 3
Progressive Disclosure	The file is well-organized into phases, but it is monolithic — the conversion table, API reference, and error handling are all inline with no bundle files or one-level-deep references to split out detail.	2 / 3
	Total	10 / 12 Passed

Description

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 specific and clearly distinct, naming concrete actions and a precise Confluence-publishing niche. Its main weakness is the missing explicit "Use when..." trigger guidance and absent common variation terms like "wiki".

Suggestions

Add a "Use when..." clause listing natural triggers (e.g., "Use when the user wants to publish or push a markdown document to Confluence or the team wiki").

Include common variation terms such as "wiki" or "push to wiki" alongside "Confluence" to improve trigger coverage.

Dimension	Reasoning	Score
Specificity	"Publish any markdown file from the vault to Confluence with format conversion and approval gate" lists multiple concrete actions (publish, format conversion, approval gate) rather than vague language.	3 / 3
Completeness	The "what" is clearly stated, but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 2 per the guidelines.	2 / 3
Trigger Term Quality	Core natural terms ("publish", "Confluence", "markdown file") are present, but common variations a user might say ("wiki", "push to wiki", "share with team") are missing from the description.	2 / 3
Distinctiveness Conflict Risk	"Publish any markdown file from the vault to Confluence" carves a clear niche (Confluence publishing) with distinct triggers unlikely to fire for unrelated skills.	3 / 3
	Total	10 / 12 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 1 missing	Warning

	Total	14 / 16 Passed

Repository: huytieu/COG-second-brain
Path: .claude/skills/publish-to-confluence/SKILL.md
Commit: dfbf9e9

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