governance-checklist-generator
Governance Checklist Generator - Auto-activating skill for Enterprise Workflows. Triggers on: governance checklist generator, governance checklist generator Part of the Enterprise Workflows skill category.
36
3%
Does it follow best practices?
Impact
100%
1.00xAverage 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/governance-checklist-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 essentially a placeholder that restates the skill name without providing any meaningful detail about capabilities, use cases, or trigger scenarios. It lacks concrete actions, natural trigger terms, and explicit guidance on when Claude should select this skill. It would be nearly useless for skill selection in a multi-skill environment.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates governance checklists for enterprise projects, covering compliance requirements, approval workflows, risk assessments, and regulatory standards.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about governance reviews, compliance checklists, audit preparation, regulatory requirements, or enterprise approval processes.'
Include varied natural keywords users might say, such as 'compliance', 'audit', 'regulatory', 'approval workflow', 'risk assessment', 'enterprise governance', rather than repeating the skill name.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the skill ('Governance Checklist Generator') but provides no concrete actions. There is no explanation of what it actually does—no mention of specific capabilities like generating checklists, defining governance criteria, compliance checks, etc. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and the 'when' clause is essentially just the skill name repeated. There is no explicit 'Use when...' guidance with meaningful triggers. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'governance checklist generator' repeated twice. There are no natural keyword variations a user might say, such as 'compliance checklist', 'governance review', 'audit checklist', 'regulatory requirements', or similar terms. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'governance checklist generator' is somewhat specific and unlikely to conflict with many other skills, but the lack of detail about what kind of governance (IT, corporate, regulatory) and what the output looks like means it could still overlap with other compliance or checklist-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 essentially an empty shell—a placeholder that describes what a governance checklist generator skill might do without providing any actual content, instructions, templates, or examples. It contains no actionable guidance whatsoever: no governance frameworks, no checklist templates, no code, no concrete steps. Every section restates the skill name in slightly different wrappers without adding value.
Suggestions
Add actual governance checklist templates or generation logic—e.g., a concrete checklist for project governance covering risk assessment, stakeholder approval, compliance verification, with specific items and acceptance criteria.
Include executable code or a structured workflow for generating checklists, such as a step-by-step process: 1) Identify governance domain, 2) Select applicable framework (SOX, GDPR, etc.), 3) Generate checklist from template, 4) Validate completeness.
Provide at least one concrete input/output example showing what a user request looks like and what the generated checklist contains.
Remove all generic filler sections (Purpose, When to Use, Capabilities, Example Triggers) that merely restate the skill name and replace them with actionable content.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic filler that tells Claude nothing actionable. Phrases like 'provides automated assistance' and 'follows industry best practices' are vacuous. The entire body explains what the skill supposedly does without ever actually doing it. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no checklist templates, no specific governance frameworks, no examples of actual output. The skill describes rather than instructs, offering only vague platitudes like 'generates production-ready code and configurations' without any evidence or implementation. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequencing, no validation checkpoints. For a 'checklist generator' skill, the complete absence of an actual checklist generation process is a critical failure. | 1 / 3 |
Progressive Disclosure | The content is a flat, monolithic block of generic marketing-style text with no meaningful structure. There are no references to detailed files, no layered content, and the sections that exist (Purpose, When to Use, Capabilities, Example Triggers, Related Skills) contain no substantive information. | 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
dc559db
- 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.