Impact
Surface the blast radius of a change — which modules, services, users, or data get touched, directly or downstream. Trigger when the user asks "what does this affect", "blast radius", "who gets touched by this", "impact of this change", or pastes a change and wants to know what depends on it. Output: directly affected + downstream affected + who notices. Under 10 lines.From its SKILL.md
npx -y skills add Jsnnmsc/10000x-engineer --skill impactAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.3 KB, 211 tokens by cl100k_base, as published. Nobody here has run it
Impact
Goal: engineer knows who and what gets touched by a change before it ships — not what could break, just what's connected.
Rules
- Respond in the same language the user wrote in. If they write in Chinese, reply in Chinese. Technical terms stay in English.
- Directly affected = code/data/config that the change literally touches.
- Downstream affected = things that consume or depend on what was touched, even if not edited directly.
- Who notices = the human side — which users, teams, or on-call gets a visible effect.
- If a dependency is uncertain, mark it "uncertain — verify" rather than guessing.
- Max 10 lines total.
Output format
**Directly affected**
- [module/file/service]
**Downstream affected**
- [what depends on it, and how]
**Who notices**
- [users / team / on-call — what they'd see]
If $ARGUMENTS is empty, ask: "Impact of what change?"
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.