change-request-generator
Change Request Generator - Auto-activating skill for Enterprise Workflows. Triggers on: change request generator, change request generator Part of the Enterprise Workflows skill category.
33
0%
Does it follow best practices?
Impact
96%
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/change-request-generator/SKILL.mdQuality
Discovery
0%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 and category label with no substantive content. It lacks any concrete actions, meaningful trigger terms, or explicit usage guidance. It would be nearly impossible for Claude to reliably select this skill from a pool of available skills based on this description alone.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates structured change request documents including risk assessment, rollback plans, approval workflows, and implementation schedules for IT infrastructure or software changes.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to create a change request, CR, RFC, change ticket, change management form, or needs to document a planned infrastructure or application change.'
Expand trigger terms to include common variations and synonyms users would naturally say, such as 'change ticket', 'RFC', 'request for change', 'change management', 'ITIL change', 'CR form', etc.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Change Request Generator') without describing any concrete actions. There are no specific capabilities listed—no mention of what it generates, what inputs it takes, or what outputs it produces. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it.' There is no explanation of functionality and no explicit 'Use when...' clause or equivalent guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'change request generator' repeated twice. There are no natural variations a user might say, such as 'CR', 'change ticket', 'RFC', 'request for change', 'ITSM', or other common synonyms. | 1 / 3 |
Distinctiveness Conflict Risk | The description is too vague to distinguish this skill from other enterprise workflow or document generation skills. 'Enterprise Workflows' is a broad category, and without specific actions or triggers, it could easily conflict with other skills. | 1 / 3 |
Total | 4 / 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 placeholder that contains no actual instructional content. It repeatedly describes itself in abstract terms ('provides automated assistance,' 'follows industry best practices') without ever delivering concrete guidance, code, templates, or workflows for generating change requests. It fails on every dimension of the rubric.
Suggestions
Add a concrete change request template (e.g., a markdown or JSON schema) with required fields like description, impact assessment, rollback plan, and approval chain.
Provide a step-by-step workflow for generating a change request, including validation checkpoints such as verifying required fields are populated and risk assessment is complete.
Include at least one fully worked example showing input (a described change) and output (a complete, formatted change request document).
Remove all meta-description sections ('When to Use,' 'Example Triggers,' 'Capabilities') that describe the skill abstractly and replace them with actual actionable content.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is almost entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual instructions, code, or concrete guidance. Every section restates the same vague concept. | 1 / 3 |
Actionability | There is zero actionable content—no code, no commands, no templates, no concrete steps for generating a change request. The 'capabilities' section describes what it could do but never actually does it. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints. The skill claims to provide 'step-by-step guidance' but contains none. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no references to supporting files, no structured navigation, and no separation of overview from detail. There are no bundle files to reference either. | 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.