Agent skill

Genre Craft

by danjdewhurst in danjdewhurst/story-skills

This skill should be used when the user asks about "mystery", "fair play", "clue", "red herring", "romance beats", "HEA", "thriller", "ticking clock", "horror", "dread", "MG", "YA", "middle grade"…

MITAuto-check: notesWriting & Content

Install Genre Craft

skills CLI
$ npx skills add danjdewhurst/story-skills --skill genre-craft -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install danjdewhurst/story-skills genre-craft --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/danjdewhurst/story-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/genre-craft .claude/skills/genre-craft && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
genre-craft
GitHub stars
286
Used in
1 other repo
Token cost
~2.6k tokens
SKILL.md length
1,233 words
Files
11 (incl. references)
Skills in repo
24
Repo updated
First seen
Licence
MIT

At a glance

This skill should be used when the user asks about "mystery", "fair play", "clue", "red herring", "romance beats", "HEA", "thriller", "ticking clock", "horror", "dread", "MG", "YA", "middle grade"…

  • Works in 5 steps: Pick the pack. Read story.md for… → Set the constraints up front. Apply the… → Draft against the pack. Use the pack's… → …
  • Asks about mystery
  • SKILL.md covers Overview, Prerequisites, When to Use and Workflow, plus 4 more sections
  • Calls node

What it does

Genre Craft is an agent skill from danjdewhurst/story-skills. This skill should be used when the user asks about "mystery", "fair play", "clue", "red herring", "romance beats", "HEA", "thriller", "ticking clock", "horror", "dread", "MG", "YA", "middle grade", "young adult", "science fiction", "sci-fi", "fantasy", "quest", "chosen one", "historical fiction", "period voice", "anachronism", "comedy", "humour", "humor", "romcom", "farce", "satire", "running gag", "serial", "episodic", "web serial", "genre conventions", or wants genre-specific structural craft for a story…

Its SKILL.md is about 2.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 11 other files, including reference files (for example `references/comedy.md`, `references/fantasy.md` and `references/historical.md`).

It sits in Writing & Content, covering Creative writing and fiction. The repository describes itself as: Agent Skills for end-to-end story writing in markdown, packaged as Codex and Claude Code plugins. The licence is MIT.

When your agent uses it

  • Asks about mystery
  • Science fiction
  • Historical fiction
  • Genre conventions

Example prompts

  • “mystery”
  • “fair play”
  • “red herring”
  • “/genre-craft”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Pick the pack. Read story.md for genre/sub-genre and load the
  2. Set the constraints up front. Apply the pack's structural
  3. Draft against the pack. Use the pack's beat concepts and rules
  4. Run the pack audit in revision. Each reference ends with an audit
  5. Record genre decisions. Any deliberate deviation from the pack (a

What it can do on your machine

Read from SKILL.md and the folder at commit 9a54e04. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • node

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Genre Craft loads about 2.6k tokens when it runs, and up to ~16k if it reads all its reference files. Until then it costs about 150 tokens; SKILL.md has 1,233 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~150
When it runs · the whole SKILL.md, loaded when a task matches
~2.6k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~16k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NoteMentions a .env fileSKILL.md:126
    `bunfig.toml` (which can run code) and `.env`, and a package script runs from the checkout's root. If no CLI is availab

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from danjdewhurst/story-skills at commit 9a54e04, republished under its MIT licence (© danjdewhurst). 1,233 words, ~2,644 tokens.

Download SKILL.mdSave it as .claude/skills/genre-craft/SKILL.md (or your agent's skills folder). This skill also uses 10 other files; get the full folder from GitHub.
name
genre-craft
description
This skill should be used when the user asks about "mystery", "fair play", "clue", "red herring", "romance beats", "HEA", "thriller", "ticking clock", "horror", "dread", "MG", "YA", "middle grade", "young adult", "science fiction", "sci-fi", "fantasy", "quest", "chosen one", "historical fiction", "period voice", "anachronism", "comedy", "humour", "humor", "romcom", "farce", "satire", "running gag", "serial", "episodic", "web serial", "genre conventions", or wants genre-specific structural craft for a story project. NOT for a clue check as a revision pass (use revision-continuity).

Genre Craft

Overview

Genre-specific structural packs: the codified craft each genre expects, as checkable rules, ledgers, and audits. Packs cover mystery (fair play + clue ledger), romance (beats + HEA contract), thriller (ticking clock, power imbalance, set pieces), horror (dread/terror ordering, monster rules), MG/YA (category constraints), science fiction (load-bearing speculative elements), fantasy (quest structure, magic paid off by its rules and costs), historical fiction (period voice, anachronisms, real people), comedy (escalation, comic set-ups and payoffs, tone), and serial/episodic structure. Use at story-init (pick the pack, set the constraints) and in revision (run the pack's audit).

Prerequisites

A story project must already exist (created via the story-init skill) with its genre recorded in story.md. A plot structure (plot-structure) should exist or be in progress.

When to Use

  • Starting or re-categorizing a story in one of the covered genres
  • Planning genre load-bearing elements (clues, clocks, season goals)
  • Auditing a draft against its genre's contract
  • NOT for line-level genre voice (that belongs to the better-writing skill's genre work); these packs are structural
  • NOT for literary fiction as a pack — its conventions resist deterministic encoding by design

Workflow

  1. Pick the pack. Read story.md for genre/sub-genre and load the matching reference:
    • Mystery / crime / detective → references/mystery-fair-play.md
    • Romance → references/romance-beats.md
    • Thriller / action / suspense → references/thriller.md
    • Horror → references/horror.md
    • Middle grade / young adult → references/mg-ya.md
    • Science fiction → references/scifi-pipeline.md
    • Fantasy (epic, quest, secondary-world) → references/fantasy.md
    • Historical fiction → references/historical.md
    • Comedy (romantic comedy, farce, satire, cosy comedy) → references/comedy.md; a cosy mystery not played for laughs needs only the mystery pack
    • Serial / episodic / web serial → references/serial-episodic.md
    • Multi-genre stories: load each applicable pack; where packs conflict (e.g. horror's slow dread vs. thriller's cliffhangers), decide with the user which genre's contract dominates per section and record the decision in story.md notes.
  2. Set the constraints up front. Apply the pack's structural requirements during planning:
    • Mystery: create continuity/clues/ and ledger every clue and red herring via story add clue '...' --planted chapter-NN --payoff chapter-NN, with significance-delayed frontmatter where the reader sees the clue before understanding it and red-herring: true on misleading clues (story add clue '...' --red-herring; their payoff is the chapter that debunks them). Run story clues . for the fair-play matrix and story diagram clues for the plant-to-reveal flow.
    • Thriller: log every promised deadline in continuity/promises/ and give every scene a date and time, so story timeline . shows the story clock.
    • Serial: record season-goal: in story.md and episode-question: in each installment's frontmatter, and the release cadence as release-every: (days, or months such as 1 month) and release-start: (YYYY-MM-DD) in story.md, or release-date: on a chapter. story next . shows the next episode due and warns when one due within release-warn-days: (default 3) has no prose.
    • MG/YA: record target-words: in story.md and check the category constraints (protagonist age, minimized adult involvement).
    • Sci-fi: write the speculative element's rules, costs, and limits in worldbuilding/systems/ before the climax exploits them.
    • Fantasy: write the magic's rules, costs, and limits in worldbuilding/systems/ (the worldbuilding skill designs them) and log the quest goal and any prophecy in continuity/promises/.
    • Historical: record setting-era in story.md, the chosen period register in the style sheet, and a research/ note (the research skill) for every fact the plot leans on and every real person; run the editorial-review real-people pass for anyone living or recently dead.
    • Comedy: record the comic sub-genre in story.md, the tone line (where comedy stops) in its ## Tone & Style section, each comic lead's flaw in their character file, and each running gag or call-back the reader is owed a payoff on as one promise in continuity/promises/. Sentence-level comic timing belongs to the line-editing skill.
  3. Draft against the pack. Use the pack's beat concepts and rules alongside the chapter-writing workflow and the scene-craft scene-grain tools. Cross-link thriller pacing to the Fichtean curve note in references/thriller.md, and check thriller and serial chapter endings with story pacing . (chapter hook values, and runs of resolution endings); cross-link serial book-level canon to the series-continuity skill.
  4. Run the pack audit in revision. Each reference ends with an audit checklist. Run it as part of a developmental revision pass (see the revision-continuity skill) and record findings in the revision plan.
  5. Record genre decisions. Any deliberate deviation from the pack (a romance without a black moment, a mystery that withholds) is a story decision: note it in story.md with the reason, so later audits don't "fix" it.
Show full SKILL.md (523 more words)Show less

Conventions

  • Pack-specific entities use the project conventions: kebab-case ids, YAML frontmatter, _index.md registries where a collection exists (continuity/clues/ follows the continuity/promises/ pattern).
  • Clue planted must precede payoff (story continuity flags payoff-before- plant as an error); deadline promises follow the same ordering logic as promise/question ordering.
  • Clues carry the links: each clue names its planted and payoff chapters and, under characters, the suspects it implicates or clears, and story links checks those ids. Character files have no clue field; to list a suspect's clues, run story list clues --where characters={character-id}.
  • Genre audits live in the revision plan or continuity/ audit files — never only in chat.

CLI Maintenance

Use the Story CLI when it is available. If story is not installed, use the bundled fallback node ../story-maintenance/scripts/story.js with the same arguments. Use node <checkout>/bin/story.js instead only when the user names a Story Skills repository checkout or you are working in one. Write the script as an absolute path (resolve the fallback relative to this skill folder) and run it from the folder you would run story from, so . and other relative paths keep their meaning. Use Node, not Bun or a package script: Bun would load that folder's bunfig.toml (which can run code) and .env, and a package script runs from the checkout's root. If no CLI is available, perform the registry, backlink, and word-count checks manually.

After adding or changing genre entities (clues, deadlines, comic set-ups, season goals, episode questions):

shell
story reindex .
story wordcount . --write
story check .
story clues .     # mystery: fair-play matrix and warnings

Reference Files

  • references/mystery-fair-play.md - Fair-play doctrine, clue-planting techniques, red-herring discipline (red-herring: true), gather-suspects reveal, clue ledger convention, the story clues fair-play matrix and story diagram clues
  • references/romance-beats.md - Widely-published romance beat concepts (paraphrased), HEA/HFN reader contract, the black moment
  • references/thriller.md - Ticking clock honored once promised, power imbalance, set pieces, mini-cliffhanger endings, Fichtean curve pairing
  • references/horror.md - Dread vs. terror vs. gross-out ordering, the uncanny, monster rules stated early, recovery periods
  • references/mg-ya.md - Word-count norms, age-appropriate voice/stakes, minimized adult involvement, content boundaries
  • references/scifi-pipeline.md - Speculative element must be load-bearing, rules stated before exploited, worldbuilding→plot pipeline
  • references/fantasy.md - Quest and journey structure, magic rules stated before the climax relies on them, cost and limits, secondary-world exposition, chosen-one pitfalls
  • references/historical.md - Period voice vs. readability, anachronism checks (things, words, ideas), invented vs. real people, ethics of the real past, the author's note
  • references/comedy.md - Escalation, reversals, comic set-ups and payoffs (call-backs, rule of three, running gags), character-driven humour (comic flaw, straight man and funny man, want vs. need), tone management and comic sub-genres; sentence-level timing handed to line-editing
  • references/serial-episodic.md - Season/volume goal, per-episode dramatic question, a reward in every installment, recap discipline

Shared Conventions

Every story skill follows the shared conventions in ../story-maintenance/references/conventions.md, resolved relative to this skill folder. Read it before creating, renaming, or linking story files. If that file is missing because this skill was installed without story-maintenance, the essentials are: kebab-case ids and filenames, YAML frontmatter on every story-project file, _index.md registry tables that story reindex rebuilds (never edit them by hand), bidirectional links between entities, characters for who is on the page and mentions for who is only referred to, status: deceased plus died-in: chapter-{NN} for deaths, and no project-local generator or build scripts (run only the installed or bundled Story CLI).

© danjdewhurst, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 10 other files (references) in skills/genre-craft of danjdewhurst/story-skills.

  • SKILL.md
  • references/comedy.md
  • references/fantasy.md
  • references/historical.md
  • references/horror.md
  • references/mg-ya.md
  • references/mystery-fair-play.md
  • references/romance-beats.md
  • references/scifi-pipeline.md
  • references/serial-episodic.md
  • references/thriller.md

Open the folder on GitHubat commit 9a54e04

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in danjdewhurst/story-skills, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Genre Craft next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Genre Craft compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Genre Craft this skilldanjdewhurst/story-skills2861 repos~2.6kAutomated safety check: NotesMIT
Story Multi-Perspective Reviewzenstory-ai/oh-story-claudecode7.4k3 repos~3kAutomated safety check: PassMIT
Short Web Fiction Trend Scanzenstory-ai/oh-story-claudecode7.4k2 repos~1.2kAutomated safety check: PassMIT
InkOS Creative HarnessNarcooo/inkos10k1 repos~1.1kAutomated safety check: PassAGPL-3.0
Novel Arteternityspring/shuohao-skills4.3k—~1.1kAutomated safety check: NotesApache-2.0
SepiaNanako0129/sepia3.1k—~3.6kAutomated safety check: PassMIT

Similar skills

  • Story Multi-Perspective Review

    zenstory-ai/oh-story-claudecode

    Reviews Chinese web-novel text with several reviewer agents in parallel, falling back to a single-agent pass, and reports structure, character, prose and setting problems with fixes.

    7.4k GitHub starsUsed in 3 repos~3k tokens
    Writing & ContentAuto-check passed
  • Short Web Fiction Trend Scan

    zenstory-ai/oh-story-claudecode

    Scans popular short web-fiction rankings on Chinese platforms such as Dianzhong and Heiyan to surface trending emotional hooks, themes and topic candidates with an expiry warning.

    7.4k GitHub starsUsed in 2 repos~1.2k tokens
    Writing & ContentAuto-check passed
  • Drives long-form fiction, scripts, storyboards, interactive films and long-document translation through InkOS, with every change made by a typed action.

    10k GitHub starsUsed in 1 repo~1.1k tokens
    Writing & ContentAuto-check passed
  • Novel Art

    eternityspring/shuohao-skills

    给 AI 短剧出美术设定集(场景 + 叙事道具):场景的设计意图、一致性锚点、光照时段变体、 空景提示词;道具的戏剧功能、状态变体、尺度参照、白底无手提示词。

    4.3k GitHub stars~1.1k tokensUpdated 2 days ago
    Writing & ContentAuto-check: notes
  • Sepia

    Nanako0129/sepia

    Make AI-generated writing read as human-written, in fiction and in professional prose.

    3.1k GitHub stars~3.6k tokensUpdated yesterday
    Writing & ContentAuto-check passed
  • Story Toolbox Router

    zenstory-ai/oh-story-claudecode

    Routes a Chinese web-novel writing request to the matching tool in a 13-skill toolbox, covers author habit memory, and can launch a local dashboard for browsing a project.

    7.4k GitHub stars~1.7k tokensUpdated today
    Writing & ContentAuto-check passed

More from danjdewhurst/story-skills

All 24 skills in this repo
  • Story Maintenance

    danjdewhurst/story-skills

    This skill should be used when the user asks to "validate", "reindex", "repair registries", "check links", "run the continuity, pacing, clue, voice, or name checks", "count words", "summarize a…

    286 GitHub starsUsed in 1 repo~5.4k tokens
    Auto-check: notes
  • Adaptation

    danjdewhurst/story-skills

    This skill should be used when the user asks to "make an audiobook", "narration script", "narrator", "ACX", "Findaway", "pronunciation guide", "how long is the audiobook", "adapt to a screenplay"…

    286 GitHub starsUsed in 1 repo~3.5k tokens
    Auto-check: notes
  • Chapter Writing

    danjdewhurst/story-skills

    This skill should be used when the user asks to "write a chapter", "next chapter", "chapter outline", "draft chapter", "continue the story", "write a scene", "outline a chapter", or wants to write…

    286 GitHub starsUsed in 1 repo~4.8k tokens
    Auto-check: notes
  • Character Management

    danjdewhurst/story-skills

    This skill should be used when the user asks to "create a character", "update a character", "add a character", "build a family tree", "character relationships", "character timeline", "character…

    286 GitHub starsUsed in 1 repo~3.9k tokens
    Auto-check: notes
  • Discovery Drafting

    danjdewhurst/story-skills

    This skill should be used when the user asks about "pantsing", "discovery write", "write without an outline", "discovery draft", "write into the dark", "story kernel", "reconcile a chapter", "dead…

    286 GitHub starsUsed in 1 repo~2k tokens
    Auto-check: notes
  • Editorial Review

    danjdewhurst/story-skills

    This skill should be used when the user asks for a "sensitivity reader", "authenticity reader", "cultural review", "is this portrayal okay", "real people in my novel", "defamation", "can I use song…

    286 GitHub starsUsed in 1 repo~3.6k tokens
    Auto-check: notes

Questions about Genre Craft

What does Genre Craft do?

This skill should be used when the user asks about "mystery", "fair play", "clue", "red herring", "romance beats", "HEA", "thriller", "ticking clock", "horror", "dread", "MG", "YA", "middle grade"…. Genre Craft is an agent skill from danjdewhurst/story-skills.

When should I use Genre Craft?

Genre Craft fits situations like: asks about mystery; science fiction; historical fiction; genre conventions.

How do I install Genre Craft in Claude Code?

Run `npx skills add danjdewhurst/story-skills --skill genre-craft -a claude-code`. Or copy the skill folder (skills/genre-craft in danjdewhurst/story-skills) into .claude/skills/genre-craft in your project. Claude Code loads it when a task matches its description.

How do I install Genre Craft in Codex?

Run `npx skills add danjdewhurst/story-skills --skill genre-craft -a codex`. Or copy the skill folder (skills/genre-craft in danjdewhurst/story-skills) into .agents/skills/genre-craft in your project. Codex loads it when a task matches its description.

Can I use Genre Craft in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add danjdewhurst/story-skills --skill genre-craft -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/genre-craft, .gemini/skills/genre-craft, .github/skills/genre-craft and .opencode/skills/genre-craft in your project.

What does Genre Craft need to run?

Going by SKILL.md and its folder, Genre Craft needs the command-line tools its instructions call (node).

Does Genre Craft access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Genre Craft safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Genre Craft use?

Genre Craft is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Genre Craft use?

About 2.6k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 13k tokens, read only when the agent opens those files.

What are the alternatives to Genre Craft?

Skills that share tags, products or a category with Genre Craft: Story Multi-Perspective Review (zenstory-ai/oh-story-claudecode, 7.4k stars), Short Web Fiction Trend Scan (zenstory-ai/oh-story-claudecode, 7.4k stars), InkOS Creative Harness (Narcooo/inkos, 10k stars) and Novel Art (eternityspring/shuohao-skills, 4.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Genre Craft?

danjdewhurst (a GitHub user) maintains it in danjdewhurst/story-skills, which has 286 GitHub stars. The repository holds 24 skills in this directory. The repository was last updated on October 9, 2026.

Source: danjdewhurst/story-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.