impact-analysis-helper
Impact Analysis Helper - Auto-activating skill for Enterprise Workflows. Triggers on: impact analysis helper, impact analysis helper Part of the Enterprise Workflows skill category.
31
Quality
0%
Does it follow best practices?
Impact
87%
1.01xAverage 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/impact-analysis-helper/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 placeholder with no substantive content. It provides only a skill name, a redundant trigger phrase, and a category label. There is no explanation of what impact analysis this skill performs, what domain it applies to, or when it should be selected over other skills.
Suggestions
Add concrete actions describing what the skill does (e.g., 'Analyzes code changes to identify affected components, dependencies, and downstream systems')
Include a 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when assessing change impact, reviewing dependencies, or evaluating risk of modifications')
Specify the domain or context to distinguish from other analysis skills (e.g., 'for enterprise software deployments' or 'for database schema changes')
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'Impact Analysis Helper' is a name, not a description of capabilities. There is no indication of what this skill actually does. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. It only provides a category label ('Enterprise Workflows') and the skill name, with no functional description or usage guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'impact analysis helper' repeated twice, which is the skill name itself rather than natural keywords users would say. No domain-specific terms like 'dependencies', 'change impact', 'risk assessment', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The description is extremely generic. 'Impact Analysis' could apply to many domains (code changes, business decisions, security, etc.). Without specifics, it would be impossible to distinguish from other analysis-related 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 an empty template with no actual content. It describes what an impact analysis helper skill would do without providing any concrete guidance, examples, code, or workflows. The entire content is meta-description rather than actionable instruction.
Suggestions
Define what 'impact analysis' means in this context and provide a concrete workflow with numbered steps (e.g., 1. Identify change scope, 2. Map dependencies, 3. Assess risk levels)
Add executable code examples or specific commands for performing impact analysis tasks
Include at least one concrete example showing input (a proposed change) and expected output (an impact assessment)
Replace vague capability claims with actual implementation details - what files to check, what patterns to look for, what output format to produce
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely boilerplate with no actual substance. It explains what the skill does in abstract terms without providing any concrete information Claude doesn't already know. Every section is padded filler. | 1 / 3 |
Actionability | No concrete code, commands, or executable guidance whatsoever. The content only describes vague capabilities ('provides step-by-step guidance', 'generates production-ready code') without actually providing any of them. | 1 / 3 |
Workflow Clarity | No workflow steps, sequences, or processes are defined. The skill claims to provide 'step-by-step guidance' but contains zero actual steps for performing impact analysis. | 1 / 3 |
Progressive Disclosure | No references to detailed materials, no links to related documentation, and no structured navigation. The content is a shallow placeholder with no depth or organization beyond generic headers. | 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.