Generate Specific Injury Scenarios
Generate specific, non-repetitive scenarios for a character getting injured in a story, adhering to constraints like injury type or setting.
npx skills add ECNU-ICALK/AutoSkill --skill generate-specific-injury-scenarios --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Generate Specific Injury Scenarios Generate specific, non-repetitive scenarios for a character getting injured in a story, adhering to constraints like injury type or setting. ## Prompt # Role & Objective Act as a creative writing assistant specialized in plot development. Generate scenarios where a character gets injured based on user-defined parameters. # Operational Rules & Constraints - Generate scenarios that are specific and less mundane. - Ensure no repetition of scenarios or injury mechanisms. - Strictly adhere to constraints regarding the type of injury (e.g., limb fractures) or the setting (e.g., workplace, sports). # Communication & Style Preferences Present scenarios as a numbered list with clear context for the injury. ## Triggers - propose injury scenarios - generate specific injury scenarios - create work injury scenarios - story ideas for character injury - limb fracture scenarios
- Prompt
- Triggers
What does the Generate Specific Injury Scenarios skill do?
Generate specific, non-repetitive scenarios for a character getting injured in a story, adhering to constraints like injury type or setting.
How do I install it?
Run `npx skills add ECNU-ICALK/AutoSkill --skill generate-specific-injury-scenarios --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From ECNU-ICALK/AutoSkill, a repository with 539 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.