Agent skill

Verse Craft

by danjdewhurst in danjdewhurst/story-skills

This skill should be used when the user asks to "write a poem", "write a limerick", "write a sonnet", "haiku", "villanelle", "ballad", "song lyrics", "a song for my character", "a rhyme", "rhyming…

MITAuto-check: notesWriting & Content

Install Verse Craft

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

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

GitHub CLI
$ gh skill install danjdewhurst/story-skills verse-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/verse-craft .claude/skills/verse-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
verse-craft
GitHub stars
279
Used in
1 other repo
Token cost
~2.5k tokens
SKILL.md length
1,412 words
Files
4 (incl. references)
Skills in repo
24
Repo updated
First seen
Licence
MIT

At a glance

This skill should be used when the user asks to "write a poem", "write a limerick", "write a sonnet", "haiku", "villanelle", "ballad", "song lyrics", "a song for my character", "a rhyme", "rhyming…

  • Works in 6 steps: Mode and constraints → Draft → Scan → …
  • Asks to write a poem
  • SKILL.md covers Overview, Prerequisites, When to Use and Hard Rules, plus 3 more sections
  • Calls node

What it does

Verse Craft is an agent skill from danjdewhurst/story-skills. This skill should be used when the user asks to "write a poem", "write a limerick", "write a sonnet", "haiku", "villanelle", "ballad", "song lyrics", "a song for my character", "a rhyme", "rhyming couplets", "does this scan", "check the meter", "fix the rhythm of this poem", "rhyme scheme", "iambic pentameter", "a prophecy in verse", "a nursery rhyme", "rhyming picture book", or wants verse written, scanned, or revised, whether inside a story project or as a standalone poem. NOT for accidental rhymes in prose…

Its SKILL.md is about 2.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `references/forms.md`, `references/meter-and-scansion.md` and `references/rhyme.md`).

It sits in Writing & Content, covering Copy editing and proofreading and 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 to write a poem
  • Write a limerick
  • A song for my character
  • Rhyming couplets

Example prompts

  • “write a poem”
  • “write a limerick”
  • “write a sonnet”
  • “/verse-craft”

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Mode and constraints
  2. Draft
  3. Scan
  4. Check rhyme and form
  5. Revise
  6. Place story verse

What it can do on your machine

Read from SKILL.md and the folder at commit 1df23f9. 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

Verse Craft loads about 2.5k tokens when it runs, and up to ~6.4k if it reads all its reference files. Until then it costs about 158 tokens; SKILL.md has 1,412 words of instructions outside code blocks.

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

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:176
    run code) and `.env`, and a package script runs from the checkout's

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 1df23f9, republished under its MIT licence (© danjdewhurst). 1,412 words, ~2,531 tokens.

Download SKILL.mdSave it as .claude/skills/verse-craft/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
verse-craft
description
This skill should be used when the user asks to "write a poem", "write a limerick", "write a sonnet", "haiku", "villanelle", "ballad", "song lyrics", "a song for my character", "a rhyme", "rhyming couplets", "does this scan", "check the meter", "fix the rhythm of this poem", "rhyme scheme", "iambic pentameter", "a prophecy in verse", "a nursery rhyme", "rhyming picture book", or wants verse written, scanned, or revised, whether inside a story project or as a standalone poem. NOT for accidental rhymes in prose (use line-editing) or permissions for quoting someone else's poem or song lyrics (use editorial-review).

Verse Craft

Overview

Write, scan, and revise verse: fixed forms such as the limerick, sonnet, haiku, and villanelle; ballads and song lyrics; rhyming picture-book text; and verse that lives inside a story (a character's song, a prophecy, a skipping rhyme). Every claim that a line scans is shown, not asserted: the agent marks the stresses, counts the syllables, and labels the rhyme scheme so the author can check the work. The author's poem is the standard; propose changes, do not rewrite it wholesale.

Prerequisites

None. A standalone poem needs no project: save it where the user asks, as a plain .md file. Verse that belongs to a story needs the story project, story.md (POV, tone, era), and the file of the character who speaks or sings it.

When to Use

  • Writing a new poem, limerick, song, or rhyme in a given form
  • Checking whether an existing poem scans or keeps its rhyme scheme
  • Fixing meter, forced rhymes, or padded lines in a draft poem
  • Verse inside a story: a character's song, a riddle, a prophecy, an epigraph the author writes themselves
  • Rhyming text for a picture book (plan the spreads with adaptation, write and scan the verse here)
  • NOT for unintended rhymes or jingles in prose (use line-editing)
  • NOT for permissions when quoting another writer's poem or lyrics (use editorial-review)
  • NOT for a poetry collection as a story project: the CLI checks fiction entities, so keep a collection as plain files and do not run story init for it

Hard Rules

  • Never say a line scans without showing its stresses (or, in another language's tradition, what that tradition counts). Mark them as in references/meter-and-scansion.md.
  • Never pad a line to fill the meter ("did go", "so very", "oh", "all alone and lone"). Rewrite the line instead.
  • Never invert natural word order to land a rhyme ("the sea so blue I wade into" for "I wade into the blue sea") unless the author's style already does it on purpose.
  • Never reproduce copyrighted lyrics or poems, even a stanza. Allude or write something original in the same form; send permission questions to editorial-review.
  • Never rewrite the author's poem wholesale without explicit permission. Propose line-level fixes with a reason each.
  • Verse a character writes sounds like that character, not like a competent poet. A clumsy character's poem can be clumsy on purpose; say so rather than fixing it.

Workflow

1. Mode and constraints
  1. Work out the mode: write new verse, critique a poem, fix a poem's meter or rhyme, or story verse that sits inside a chapter.
  2. Pin the constraints, asking only for what the request leaves open: form, meter, rhyme scheme, line and stanza count, refrain, subject, tone, and any words that must appear. references/forms.md gives each form's rules; state the ones you are following.
  3. For story verse, read story.md (era, setting, tone), the speaker's character file (voice notes, voice-words, voice-avoid, education), and the chapter it goes in. Verse must not state canon the project does not already hold: no new names, history, or world rules, and no small facts either (how long something has gone on, what goods come in, who signs for what). Comic verse reaches for these to fill a line or land a rhyme. Before drafting, list the facts the verse may use (names, objects, habits, running jokes the project states) and take every detail from that list.
  4. Settle the language. For story verse it is language in story.md (a missing field means en); for a standalone poem, ask if the request leaves it open. Write and scan in that language's own tradition: syllabic (French, Spanish, Italian), quantitative (Classical Greek, Latin, Arabic), mora-based (Japanese), or tonal (Classical Chinese) verse is not measured in English feet. See "Verse in other languages" in references/meter-and-scansion.md and "Rhyme in other languages" in references/rhyme.md. The forms, examples, and forced-rhyme tells in the references are English; adapt them, and say when you cannot scan a tradition reliably.
  5. For English, ask which accent the verse is scanned in when it matters (British and American stress differ on words such as address, garage, cigarette), and which dialect the rhymes must work in.
2. Draft
  1. Draft for sense first: every line must say something a reader would say in prose. Then fit the meter.
  2. Choose rhyme words that carry meaning; build the line toward the rhyme rather than bolting the rhyme on. See references/rhyme.md for forced rhymes and the rhymes readers have seen too often.
  3. Keep the syntax natural. Read each line as a sentence: if nobody would say it that way, rewrite it.
3. Scan

Scan every line, including the author's lines in critique mode. Show a scansion table (format in references/meter-and-scansion.md) with the stress pattern, syllable count, and rhyme letter for each line, and mark each departure from the meter as deliberate (a trochee at the line start, a feminine ending) or a fault (a stress that falls on a weak syllable, a missing or extra beat).

When the user asks for the poem only, still scan every line and check the rhyme scheme before answering, then return just the verse and offer the table afterwards. Never return a line whose end word breaks the scheme or whose beat count breaks the form: fix it first.

Show full SKILL.md (534 more words)Show less
4. Check rhyme and form
  1. Label the rhyme scheme with letters (AABBA). Mark slant rhymes and eye rhymes, and say whether each was meant.
  2. Check the form's other rules from references/forms.md: refrains repeated exactly, the volta in a sonnet, the syllable count in a haiku, the punchline in a limerick's last line.
  3. Read the poem aloud, or offer the system's text-to-speech (say on macOS; espeak-ng or spd-say on Linux; check with command -v and ask before installing anything). A line that stumbles aloud is a fault even if the table says it scans.
5. Revise

Present fixes in the edit-note format the line-editing skill uses, with the verse line as the location:

markdown
**stanza 2, line 3** · rhythm
> Before: And the boat that did come on the Thursday tide
> After: And the boat that came in on the Thursday tide
Why: "did come" pads the line; "came in" keeps four beats without the filler.

Lead with faults that break the form, then weak rhymes, then polish. Apply only what the author accepts, or everything on explicit instruction. Rescan every line you change.

6. Place story verse
  1. Put the verse where it is read: in the chapter body, or in a matter/ file for an epigraph, created without a printed page title:
shell
story add matter 'Epigraph' --heading=false
  1. Keep line breaks through every build: end each line of a stanza, except the last, with a backslash (\), and leave a blank line between stanzas. For verse set off from the prose, put the stanza in a blockquote and end each quoted line the same way.
  2. Record the verse's facts in the usual places: a song that recurs is a motif (theme-craft), a prophecy is a promise (plot-structure).
  3. Run maintenance:
shell
story reindex .
story wordcount . --write
story check .

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 and word-count checks manually.

Reference Files

  • references/forms.md - Rules, an original example, and common faults for the limerick, sonnets, haiku, villanelle, ballad, clerihew, couplets, free verse, song lyrics, and rhyming picture-book text
  • references/meter-and-scansion.md - Feet and meters, how to find a word's stress, the scansion table format, which departures are allowed, and syllabic, quantitative, mora-based, and tonal traditions in other languages
  • references/rhyme.md - Kinds of rhyme, scheme notation, forced-rhyme tells, rhymes readers have seen too often, and rhyme in other languages

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 3 other files (references) in skills/verse-craft of danjdewhurst/story-skills.

  • SKILL.md
  • references/forms.md
  • references/meter-and-scansion.md
  • references/rhyme.md

Open the folder on GitHubat commit 1df23f9

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

Verse 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.

Verse Craft compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Verse Craft this skilldanjdewhurst/story-skills2791 repos~2.5kAutomated safety check: NotesMIT
Story Multi-Perspective Reviewzenstory-ai/oh-story-claudecode7.4k3 repos~3kAutomated safety check: PassMIT
Web Novel AI-Trace Removerzenstory-ai/oh-story-claudecode7.4k2 repos~2.6kAutomated safety check: PassMIT
InkOS Story ReviewNarcooo/inkos10k—~450Automated safety check: PassAGPL-3.0
Web Novel AI-Flavor Removeruu201/character-arc579—~2.3kAutomated safety check: PassMIT
Web Novel Polishing and De-AIuu201/character-arc5791 repos~508Automated 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
  • Web Novel AI-Trace Remover

    zenstory-ai/oh-story-claudecode

    Rewrites AI-sounding Chinese web novel text so it reads naturally, changing as little as possible and keeping plot, names and numbers intact.

    7.4k GitHub starsUsed in 2 repos~2.6k tokens
    Writing & ContentAuto-check passed
  • InkOS Story Review

    Narcooo/inkos

    Reviews chapters or manuscripts against the standard that fits their genre, audience and your own criteria, showing concrete issues and revising only when asked.

    10k GitHub stars~450 tokensUpdated 11 days ago
    Writing & ContentAuto-check passed
  • Web Novel AI-Flavor Remover

    uu201/character-arc

    Finds and rewrites AI-sounding passages in Chinese web novel text, changing as few words as possible while keeping plot, characters and names intact.

    579 GitHub stars~2.3k tokensUpdated 5 days ago
    Writing & ContentAuto-check passed
  • Polishes AI-generated web novel text to remove machine-sounding patterns, with rewriting strategies, instruction templates, style techniques and before-and-after examples.

    579 GitHub starsUsed in 1 repo~508 tokens
    Writing & ContentAuto-check passed
  • Exemplar Prose Calibration

    BingHanOfUESTC/open_agent_team

    Calibrate Chinese genre-fiction prose against Boss-provided high-quality novel examples without copying source text, names, settings, or plot chains.

    106 GitHub stars~675 tokensUpdated 3 mo ago
    Writing & ContentAuto-check passed

More from danjdewhurst/story-skills

All 24 skills in this repo
  • 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"…

    279 GitHub starsUsed in 2 repos~3.5k tokens
    Auto-check: notes
  • 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…

    279 GitHub starsUsed in 1 repo~5.4k tokens
    Auto-check: notes
  • Research

    danjdewhurst/story-skills

    This skill should be used when the user asks to "research", "fact-check", "check the history", "is this accurate", "research notes", "sources", "historical accuracy", "technical accuracy", "how…

    279 GitHub starsUsed in 2 repos~2.4k 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…

    279 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…

    279 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…

    279 GitHub starsUsed in 1 repo~2k tokens
    Auto-check: notes

Questions about Verse Craft

What does Verse Craft do?

This skill should be used when the user asks to "write a poem", "write a limerick", "write a sonnet", "haiku", "villanelle", "ballad", "song lyrics", "a song for my character", "a rhyme", "rhyming…. Verse Craft is an agent skill from danjdewhurst/story-skills. This skill should be used when the user asks to "write a poem", "write a limerick", "write a sonnet", "haiku", "villanelle", "ballad", "song lyrics", "a song for my character", "a rhyme", "rhyming couplets", "does this scan", "check the meter", "fix the rhythm of this poem", "rhyme scheme", "iambic pentameter", "a prophecy in verse", "a nursery rhyme", "rhyming picture book", or wants verse written, scanned, or revised, whether inside a story project or as a standalone poem.

When should I use Verse Craft?

Verse Craft fits situations like: asks to write a poem; write a limerick; A song for my character; rhyming couplets.

How do I install Verse Craft in Claude Code?

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

How do I install Verse Craft in Codex?

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

Can I use Verse 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 verse-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/verse-craft, .gemini/skills/verse-craft, .github/skills/verse-craft and .opencode/skills/verse-craft in your project.

What does Verse Craft need to run?

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

Does Verse 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 Verse 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 Verse Craft use?

Verse 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 Verse Craft use?

About 2.5k tokens (SKILL.md is roughly 10k 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 3.9k tokens, read only when the agent opens those files.

What are the alternatives to Verse Craft?

Skills that share tags, products or a category with Verse Craft: Story Multi-Perspective Review (zenstory-ai/oh-story-claudecode, 7.4k stars), Web Novel AI-Trace Remover (zenstory-ai/oh-story-claudecode, 7.4k stars), InkOS Story Review (Narcooo/inkos, 10k stars) and Web Novel AI-Flavor Remover (uu201/character-arc, 579 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Verse Craft?

danjdewhurst (a GitHub user) maintains it in danjdewhurst/story-skills, which has 279 GitHub stars. The repository holds 24 skills in this directory. The repository was last updated on October 8, 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.