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.
36
Quality
3%
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
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 severely underdeveloped, consisting almost entirely of metadata rather than functional information. It fails to explain what the skill does, what actions it performs, or when Claude should select it. The duplicated trigger term and absence of any capability description make this ineffective for skill selection.
Suggestions
Add concrete actions the skill performs (e.g., 'Generates ITSM change request tickets with risk assessment, implementation plans, and rollback procedures')
Include a 'Use when...' clause with natural trigger terms like 'change request', 'CR', 'change ticket', 'RFC', 'submit change', 'change management'
Specify the context or system this applies to (e.g., ServiceNow, Jira Service Management, or generic enterprise change management) to improve distinctiveness
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Change Request Generator') without describing any concrete actions. There are no verbs indicating what the skill actually does - no mention of creating, formatting, submitting, or any specific operations. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' (no actions described) and 'when should Claude use it' (no 'Use when...' clause or equivalent guidance). Only metadata about categorization is provided. | 1 / 3 |
Trigger Term Quality | The trigger terms listed are redundant ('change request generator, change request generator' - duplicated) and only cover the exact skill name. Missing natural variations users might say like 'CR', 'change ticket', 'RFC', 'request for change', or action-oriented phrases like 'submit a change'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'Change Request Generator' is somewhat specific to a domain, the lack of concrete details about what kind of change requests (IT, software, ITSM, etc.) or what format/system it targets means it could overlap with other enterprise workflow 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 a placeholder with no actionable content. It describes capabilities in abstract terms without providing any concrete guidance, templates, code, or examples for generating change requests. The content fails all dimensions by being verbose yet empty of substance.
Suggestions
Add a concrete change request template or schema showing the exact fields and format expected (e.g., title, description, impact assessment, rollback plan)
Include at least one complete example of a generated change request with sample input and output
Define a clear workflow: gather requirements → assess impact → generate request → validate completeness → submit
Remove generic boilerplate sections (Purpose, Capabilities, Example Triggers) and replace with actionable content specific to change request generation
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no specific value. Phrases like 'provides automated assistance' and 'follows industry best practices' are vague filler that Claude doesn't need explained. | 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 or what format/structure to use. | 1 / 3 |
Workflow Clarity | No workflow steps are defined. Claims to provide 'step-by-step guidance' but contains zero actual steps. There's no sequence, no validation, and no concrete process for generating change requests. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no references to detailed materials, templates, or examples. No structure for discovery or navigation to deeper 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
0c08951
- 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.