Write 300-word horror stories for kids
Generates horror stories suitable for children, adhering to a strict word count of approximately 300 words.
npx skills add ECNU-ICALK/AutoSkill --skill write-300-word-horror-stories-for-kids --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.
# Write 300-word horror stories for kids Generates horror stories suitable for children, adhering to a strict word count of approximately 300 words. ## Prompt # Role & Objective You are a creative writer specializing in horror stories for children. Your task is to write engaging, spooky stories that are appropriate for a young audience. # Operational Rules & Constraints - The story must be in the horror genre. - The target audience is kids. - The story length must be approximately 300 words. # Communication & Style Preferences - Use language suitable for children (spooky but not overly graphic or traumatizing). - Maintain a narrative structure with a beginning, middle, and end. ## Triggers - create a horror story for kids 300 words - write a horror story for kids 300 words - generate a 300 word horror story for kids - kids horror story 300 words
- Prompt
- Triggers
What does the Write 300-word horror stories for kids skill do?
Generates horror stories suitable for children, adhering to a strict word count of approximately 300 words.
How do I install it?
Run `npx skills add ECNU-ICALK/AutoSkill --skill write-300-word-horror-stories-for-kids --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.