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.
Overall
score
23%
Does it follow best practices?
Validation for skill structure
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill change-request-generatorActivation
7%This description is severely underdeveloped, functioning more as a label than a useful skill description. It provides no information about what the skill actually does, what outputs it produces, or meaningful scenarios for when Claude should select it. The redundant trigger terms and boilerplate category mention add no value for skill selection.
Suggestions
Add specific actions the skill performs, e.g., 'Generates structured change request documents including impact analysis, rollback plans, and approval workflows'
Include a proper 'Use when...' clause with realistic scenarios, e.g., 'Use when users need to create IT change requests, document system modifications, or prepare change advisory board (CAB) submissions'
Add natural trigger terms users would actually say: 'change ticket', 'CR', 'system change', 'deployment request', 'CAB submission', 'ITSM change'
| 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 verbs describing what it actually does with change requests. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' (no actions described) and 'when should Claude use it' (no use cases or scenarios provided). The 'Triggers on' line is not a proper 'Use when...' clause with meaningful context. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('change request generator' listed twice) and represent the skill name itself rather than natural user language. Missing variations like 'CR', 'change ticket', 'service request', 'ITSM', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'Change Request Generator' is somewhat specific to ITSM/enterprise workflows, but without describing what distinguishes it from other enterprise or documentation skills, there's moderate conflict risk with similar workflow tools. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
7%This skill is essentially a placeholder template with no actual instructional content. It describes capabilities in abstract terms but provides zero concrete guidance on how to generate change requests, what format they should follow, or what fields/information they require. The skill fails to teach Claude anything actionable about change request generation.
Suggestions
Add a concrete change request template or schema showing required fields (e.g., title, description, impact assessment, rollback plan, approvers)
Include at least one complete example of a generated change request with realistic content
Define the specific workflow steps: gather requirements → assess risk → populate template → validate → submit
Remove generic boilerplate sections ('Capabilities', 'Example Triggers') and replace with actual implementation guidance
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual value. Phrases like 'provides automated assistance' and 'follows industry best practices' are vague filler that Claude doesn't need. | 1 / 3 |
Actionability | No concrete code, commands, or specific instructions are provided. The entire skill describes what it does abstractly without showing how to actually generate a change request. | 1 / 3 |
Workflow Clarity | No workflow steps are defined. Claims to provide 'step-by-step guidance' but contains zero actual steps for creating change requests. | 1 / 3 |
Progressive Disclosure | The content is organized into clear sections with headers, but there are no references to detailed materials and the sections themselves contain no substantive content to disclose. | 2 / 3 |
Total | 5 / 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
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.