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 title repeated with boilerplate framing ('Auto-activating skill', 'Part of the Enterprise Workflows skill category') and no substantive content. It fails to describe what the skill does, when it should be used, or provide natural trigger terms a user would employ. It would be nearly impossible for Claude to make an informed selection decision based on this description.
Suggestions
Add concrete actions describing what the skill does, e.g., 'Generates governance checklists for regulatory compliance, audit preparation, and policy review processes, covering frameworks like SOX, GDPR, and ISO 27001.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks for a governance checklist, compliance review template, audit preparation list, regulatory framework checklist, or policy assessment.'
Remove the duplicate trigger term and the generic category framing ('Auto-activating skill for Enterprise Workflows') which add no selection value.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the skill ('Governance Checklist Generator') but provides no concrete actions—it doesn't explain what it actually does (e.g., generates checklists for compliance reviews, audits, regulatory frameworks). 'Auto-activating skill for Enterprise Workflows' is vague filler. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond restating the skill name, and the 'when' clause is just a duplicate trigger phrase with no explicit guidance on when Claude should select this skill. Both dimensions are very weak. | 1 / 3 |
Trigger Term Quality | The only trigger term listed is 'governance checklist generator' repeated twice. There are no natural keyword variations a user might say, such as 'compliance checklist', 'audit checklist', 'regulatory review', 'governance framework', or 'policy checklist'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'governance checklist' is somewhat specific and unlikely to conflict with many other skills, but the lack of detail about what kind of governance (IT, corporate, regulatory, data) and what the output looks like means it could 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 an empty placeholder with no actionable content whatsoever. It repeatedly references 'governance checklist generator' without ever defining what a governance checklist contains, how to generate one, what frameworks or standards to follow, or what the output should look like. It fails on every dimension of the rubric.
Suggestions
Add concrete governance checklist templates or schemas (e.g., SOX compliance, data governance, project gate reviews) with specific fields and validation criteria.
Provide an executable workflow: define inputs (project type, regulatory domain), processing steps (select applicable controls, generate checklist items), and expected output format (markdown checklist, JSON, etc.).
Include at least one complete example showing input parameters and the resulting generated checklist so Claude knows exactly what to produce.
Remove all generic filler sections ('When to Use', 'Example Triggers', 'Capabilities') that describe the skill abstractly and replace them with actual instructional content.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, provides no domain-specific information, and every section restates the same vague concept ('governance checklist generator') without adding substance. | 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 what it could do rather than instructing how to do it. | 1 / 3 |
Workflow Clarity | No workflow steps are defined at all. For a 'checklist generator' skill, there should be a clear process (e.g., gather inputs, select framework, generate checklist, validate), but none is provided. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no references to supporting files, no structured navigation, and no bundle files to support it. There is nothing to progressively disclose because there is no substantive content. | 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
3a2d27d
- 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.