publish-to-confluence

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

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

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, validated multi-phase workflow, but it is a monolithic single file that could benefit from progressive disclosure, and some sections add minor verbosity.

Suggestions

Split the full conversion table and the API request bodies into referenced files (e.g. CONVERSION.md and API.md) and point to them from the body for better progressive disclosure.

Tighten or remove the "Agent Mode Awareness" section, which adds length without actionable value for this single sequential operation.

Dimension	Reasoning	Score
Conciseness	The body is mostly task-oriented and avoids re-explaining concepts Claude knows, but it has some tightening opportunities such as the low-value "Agent Mode Awareness" section and restated conversion notes that partly duplicate the table.	2 / 3
Actionability	It provides copy-paste-ready API calls (exact REST endpoints, HTTP methods, full JSON request bodies) and an exact markdown-to-XHTML conversion table, giving fully executable guidance.	3 / 3
Workflow Clarity	A clear six-phase sequence with an explicit approval-gate checkpoint ("NEVER publish without explicit user approval"; "Wait for explicit yes") and feedback loops such as the 409 conflict retry (fetch latest version and retry).	3 / 3
Progressive Disclosure	All content lives inline in a single ~260-line file with no bundle files or one-level-deep references; the conversion table and API request bodies could be split into referenced files for better navigation.	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 distinct but misses an explicit "Use when..." trigger clause and broader natural keyword coverage, which caps its completeness and trigger-term scores.

Suggestions

Add an explicit "Use when..." clause with natural triggers such as "Use when the user wants to publish markdown to Confluence, push to the wiki, or send a document to Confluence."

Expand trigger-term coverage in the description itself to include user phrases like "push to wiki" and "send to Confluence" rather than only in the body.

Dimension	Reasoning	Score
Specificity	"Publish any markdown file from the vault to Confluence with format conversion and approval gate" names multiple specific concrete actions (publish, format conversion, approval gate) rather than vague language.	3 / 3
Completeness	It clearly states what the skill does but lacks an explicit "Use when..." trigger clause; per the judging guidelines a missing explicit when-clause caps completeness at 2.	2 / 3
Trigger Term Quality	It includes some natural terms ("publish", "Confluence", "markdown") but misses common user variations like "push to wiki" or "send to Confluence" that only appear in the body, not the description.	2 / 3
Distinctiveness Conflict Risk	The Confluence-publishing niche with format conversion and an approval gate is clearly distinguishable and unlikely to trigger 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
Commit: 5e9851c

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