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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill impact-analysis-helperOverall
score
17%
Does it follow best practices?
Validation for skill structure
Activation
0%This description is essentially a placeholder with no functional content. It provides only a skill name, a category label, and redundant trigger terms. There is no information about what the skill does, what actions it performs, or when it should be selected over other skills.
Suggestions
Add specific concrete actions the skill performs (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 clearly to distinguish from other enterprise skills (e.g., is this for code changes, database migrations, infrastructure updates, or business process changes?)
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'Impact Analysis Helper' is a name, not a description of capabilities. There are no verbs describing what the skill actually does. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. It only states it's an 'Auto-activating skill' in a category, with no functional information or explicit 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. 'Enterprise Workflows' could overlap with countless other skills, and 'Impact Analysis' without specifics (code? business? security?) provides no clear niche. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
0%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, code, examples, or workflows. The entire content could be replaced with a single sentence 'This skill helps with impact analysis' without losing any information.
Suggestions
Define what 'impact analysis' means in this context and provide a concrete workflow (e.g., 1. Identify change scope, 2. Map dependencies, 3. Assess risk levels, 4. Document findings)
Add executable code or specific commands for performing impact analysis tasks (e.g., scripts to analyze dependencies, templates for impact reports)
Include at least one concrete example showing input (a proposed change) and expected output (an impact analysis report structure)
Remove all generic boilerplate ('provides automated assistance', 'follows best practices') and replace with specific, actionable content
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual information. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler that waste tokens without teaching Claude anything specific. | 1 / 3 |
Actionability | There is zero concrete guidance - no code, no commands, no specific steps, no examples of actual impact analysis. The content only describes what the skill claims to do without providing any executable instructions. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. The skill mentions 'step-by-step guidance' but provides none. There are no sequences, no validation steps, and no actual process for performing impact analysis. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative structure with no references to detailed materials, no links to examples or advanced content, and no organization that would help Claude navigate to useful information. | 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
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.