Governance Checklist Generator - Auto-activating skill for Enterprise Workflows. Triggers on: governance checklist generator, governance checklist generator Part of the Enterprise Workflows skill category.
Overall
score
19%
Does it follow best practices?
Validation for skill structure
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill governance-checklist-generatorActivation
7%This description is severely underdeveloped, essentially serving as a placeholder rather than a functional skill description. It provides no information about what the skill actually does, what outputs it produces, or when Claude should select it. The repeated trigger term suggests auto-generated content without human refinement.
Suggestions
Add specific actions the skill performs, e.g., 'Generates compliance checklists for regulatory frameworks, creates audit trails, produces governance documentation for enterprise policies'
Include a 'Use when...' clause with natural trigger terms like 'compliance audit', 'regulatory checklist', 'governance framework', 'policy compliance', 'audit preparation'
Specify the type of governance (IT governance, corporate governance, data governance, regulatory compliance) to reduce ambiguity and improve skill selection accuracy
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Governance Checklist Generator') without describing any concrete actions. There are no specific capabilities listed - no verbs describing what the skill actually does with governance checklists. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and provides no 'when should Claude use it' guidance. There is no 'Use when...' clause or equivalent explicit trigger guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('governance checklist generator, governance checklist generator'). This is redundant and lacks natural variations users might say like 'compliance checklist', 'audit checklist', 'regulatory requirements', or 'governance framework'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'governance checklist' is somewhat specific to a domain, the lack of detail about what kind of governance (IT, corporate, regulatory, data) or what actions are performed means it could overlap with other compliance or checklist-related skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is essentially a placeholder with no substantive content. It describes a capability ('governance checklist generator') without providing any actual guidance, examples, templates, or workflows for generating governance checklists. The content consists entirely of generic marketing-style language that could apply to any skill.
Suggestions
Add a concrete example of a governance checklist output, showing the actual structure and items that would be generated
Provide a workflow with specific steps: gather requirements → select checklist template → customize items → validate completeness → output format
Include at least one executable code snippet or template that demonstrates checklist generation
Define what 'governance' means in this context (IT governance, corporate governance, data governance) and provide domain-specific checklist items
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler that waste tokens without adding value. | 1 / 3 |
Actionability | No concrete guidance, code, commands, or specific examples are provided. The skill describes what it claims to do in abstract terms but never shows how to actually generate a governance checklist or what one looks like. | 1 / 3 |
Workflow Clarity | No workflow is defined. Despite claiming to provide 'step-by-step guidance,' the content contains zero actual steps, no process sequence, and no validation checkpoints for generating governance checklists. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative document with no meaningful structure. There are no references to detailed materials, examples, or templates that would help with actual governance checklist generation. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
Reviewed
Table of Contents
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.