Ext Ops Panel
Open dashboard
Comparison

Long-Form Content vs ew

Long-Form Content is a plugin bundle for AI coding tools published by danielrosehill. Marketplaces we read that list it: 1 (Community GitHub marketplaces). ew is a plugin bundle for AI coding tools published by deupaxx. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-11-07. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceLong-Form Contentew
Community marketplace danielrosehill/claude-code-plugins Not seen in the last pass
Version: 2.0
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Not listed
Community marketplace deupaxx/everyday-writer Not listed Listed
Version: 0.3.0
Forks (GitHub): 6
Stars (GitHub): 38
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

Long-Form Content vs ew
FactLong-Form Contentew
Marketplaces that list it11
Stars (GitHub) (differs)1 (worse)38 (better)
Forks (GitHub) (differs)0 (worse)6 (better)
Last releaseNot publishedNot published
Where it runsInstalls as a plugin bundleInstalls as a plugin bundle
TransportNot statedNot stated
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)3715
LicenceMITMIT
Repository (differs)github.com/danielrosehill/long-form-content-plugingithub.com/deupaxx/everyday-writer
Changes in the last 7 days (differs)20
First seen (differs)2026-11-022026-10-15

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

Long-Form Content

In its own words, on Community GitHub marketplaces:

Produce books, long-form research reports, screenplays and audiobooks with teams of subagents. One pipeline (definition, planning, parallel unit drafting, review), then a production stage per type: print handoff, PDF, Fountain, or spoken script + per-chapter TTS + chaptered m4b. Consistency is carried by a style guide, per-unit briefs and a continuity ledger, and a seam reviewer checks every join between units. Successor to book-writing.

ew

In its own words, on Community GitHub marketplaces:

Claude creative writing, storytelling, script writing, and publication sub-skills constrained by a voice fingerprint and anti-AI writing rules.

How to run each

Long-Form Content As a Claude Code plugin

Claude Code
/plugin marketplace add danielrosehill/claude-code-plugins
/plugin install long-form-content@danielrosehill

ew As a Claude Code plugin

Claude Code
/plugin marketplace add deupaxx/everyday-writer
/plugin install ew@everyday-writer

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: Long-Form Content · What it can do: ew · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built