Skills

Teach Your Agent To Write Like A Human.

A skill is a SKILL.md your agent loads: the shape of a format, the method behind it, the pipeline from draft to publish. No daemon, no separate app. Add one and your agent knows how to write that thing the way a writer would.

X-Writer

Teaches your agent to write X posts the way a writer would: paragraph-based medium form, real arguments, Fischerian hooks, anti-performance prose. Not the same six shapes every AI tweet generator produces.

Fischerian hooks

Opening lines that land an idea in one beat, the kind a writer puts at the top because the rest of the piece earned it. Not curiosity-gap manipulation.

Medium-form paragraphs

One self-contained idea per paragraph. Threads chain real blocks, not one-liners with a line break every five words. Reads like writing, not a slideshow.

Anti-performance + scoring

No 'banger', no engagement bait, no 'agree?' closers. Every AI tell flagged and stripped. Long-form articles get scored on hook, argument, and payoff before publish.

X-Writer: Images, Threads, Comics

Visuals are part of the skill, not a separate one. It generates article covers, one image per thread tweet, and multi-panel comics that keep your characters consistent.

Article covers

One-image covers for long-form X articles, with style presets per category. The prompt is crafted from the article's angle and key claim, not a literal read of the title.

Thread images

One image per body tweet: progression visuals or supporting illustrations that earn an extra second of attention without taking over the argument.

Comic strips

Multi-panel comics with persistent character references. Define the cast once; the skill keeps them visually consistent across every panel of every strip.

$ npx skills add github:travsteward/openwriter --skill x-writer
Read the X-Writer docs →

Book-Writer

The orchestration layer for anything past a single essay. It organizes a book around the units that actually exist: chapters, beats, vignettes, research notes, each scored and reviewed on its own.

Chapter architecture

Per-chapter beat sheets, scene/science splits, cold opens, callbacks. The agent assembles a chapter from beats instead of one-shotting 5,000 words of nothing.

Beats methodology

Each beat is a self-contained 400–800 word unit with its own argument, scene, or vignette. The book is an assembly of beats, not a stretched outline, so it stays easy to revise and re-order.

Book mode

Whole-project context loaded at session start: TOC, voice spec, decisions log, working chapter. The agent knows the shape without re-explaining it every conversation.

Book-Writer: Fiction & Nonfiction

The same structure works for both: narrative arc, scene or argument, vignettes, callbacks. The skill handles shape; voice is handled by Author's Voice.

Nonfiction

Chapter = argument arc. Beats = self-contained claims with evidence. Research notes attached per chapter. Author's voice strict, structural rigor first.

Fiction

Chapter = scene sequence with a stakes shift. Beats = scenes with concrete sensory anchors. Vignette library for short-form material. Voice tighter, structure still load-bearing.

$ npx skills add github:travsteward/openwriter --skill book-writer
Read the Book-Writer docs →

Blog-Writer

The channel master for long-form posts. It owns beat structure, the title and preview, and per-post layout, then hands voice to Author's Voice and publishing to the GitHub plugin.

Beats before prose

Extract beats from a topic or an existing post, commit a title, preview, and slug, then draft against the structure, so the post has a spine before it has sentences.

Per-site voice

Discovers the voice anchor for each blog it writes for, so a post reads like the site it lands on, not like a generic content mill.

Straight to publish

When the draft is ready, the GitHub plugin commits it to your blog repo, featured image and frontmatter and all, in the format your site already expects.

$ npx skills add github:travsteward/openwriter --skill blog-writer
Read the Blog-Writer docs →

Newsletter-Writer

The writing workflow for email. It shapes the issue (subject line, preview, layout) and hands off to the Publish plugin to send from your own domain and list.

Built for the open

Subject line and preview text drafted as a pair, body shaped to one of four layouts. The issue is composed to be opened, not just written.

Send from the pad

Draft, preview, and send in the same editor. Delivery, your domain, and your subscriber list are handled by the Publish plugin. No Substack cut.

$ npx skills add github:travsteward/openwriter --skill newsletter-writer
Read the Newsletter docs →

Install A Skill. Teach Your Agent To Write.

Pure markdown, no signup, no daemon. Add the skill and your agent knows the format, the method, and the path to publish.

Install OpenWriter Free