confluence-page-generator
Confluence Page Generator - Auto-activating skill for Enterprise Workflows. Triggers on: confluence page generator, confluence page generator Part of the Enterprise Workflows skill category.
35
3%
Does it follow best practices?
Impact
94%
1.02xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/20-enterprise-workflows/confluence-page-generator/SKILL.mdQuality
Discovery
7%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is extremely sparse and template-like, providing almost no useful information for skill selection. It merely names the skill and repeats the same trigger term twice without describing any concrete capabilities, use cases, or natural trigger conditions. It reads like auto-generated boilerplate rather than a thoughtful skill description.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates Confluence wiki pages with proper formatting, templates, macros, and page hierarchies for enterprise documentation.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to create a Confluence page, wiki article, knowledge base entry, or Atlassian documentation.'
Include natural keyword variations users might say, such as 'wiki page', 'Confluence', 'Atlassian', 'knowledge base', 'documentation page', 'team wiki', '.confluence'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names 'Confluence Page Generator' but does not describe any concrete actions. There are no specific capabilities listed such as creating pages, formatting content, adding templates, or managing spaces. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no explanation of capabilities and no explicit 'Use when...' clause with meaningful trigger guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'confluence page generator' repeated twice. It lacks natural user language variations like 'create confluence page', 'wiki page', 'Atlassian', 'knowledge base article', or 'documentation page'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Confluence' provides some domain specificity that distinguishes it from generic document or page creation skills, but the lack of detail about what it actually does could still cause confusion with other documentation or wiki-related skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is a hollow template with no actual content. It repeatedly names the skill ('confluence page generator') without ever explaining what it does, how to do it, or providing any actionable guidance. It fails on every dimension because it contains zero technical substance — no code, no commands, no workflows, no examples, and no references to detailed materials.
Suggestions
Add concrete, executable examples showing how to generate Confluence pages (e.g., API calls to the Confluence REST API with actual request/response examples)
Define a clear workflow with steps: authenticate, create page payload, POST to API, validate response, handle errors
Remove all meta-description sections ('When to Use', 'Example Triggers', 'Capabilities') that describe the skill abstractly and replace with actual instructions
Include specific code snippets for common Confluence page generation patterns (e.g., creating pages with templates, setting permissions, adding content formatting)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats 'confluence page generator' excessively, and provides zero actual technical content or instructions. | 1 / 3 |
Actionability | There are no concrete steps, code examples, commands, or executable guidance whatsoever. Every section is vague and abstract — 'Provides step-by-step guidance' without actually providing any. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints — just generic claims about capabilities without any actual process. | 1 / 3 |
Progressive Disclosure | No structure beyond superficial headings. No references to detailed files, no navigation, and no meaningful content organization. The sections are empty shells with no substance to disclose progressively. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
4dee593
- 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.