One newsletter a week, five derivatives a day. Skill-driven editorial calendar for Claude Code.
Writing consistently is hard. Writing consistently across formats — newsletter, X threads, LinkedIn carousels, devlogs — is harder. Most calendar tools assume you already know what to write. Most AI tools generate slop because they don't know your voice.
scribetronic is a different bet: a small set of opinionated skills that turn one weekly long-form piece into a full week of derivative content, in your voice, with quality gates between each step.
You write the source. The pipeline handles the spread.
Works with Claude Code today. The skills are portable; the CLI installs them into any project.
npx scribetronic initThe CLI will:
- Scaffold the editorial calendar templates into
scribetronic/ - Register the scribetronic plugin marketplace in
.claude/settings.json - Create the folder structure for drafts, published pieces, and notes
Restart Claude Code; the 23 skills load as /scribetronic:write, /scribetronic:agenda, etc. The bare /write form also works.
If you only want the writing skills and don't need the editorial calendar:
/plugin marketplace add r-bart/scribetronic-plugin
/plugin install scribetronic@scribetronic
You'll get every /scribetronic:* skill without scribetronic/calendar/ or publish-config.yaml.
npm install -g scribetronic
cd ~/your-writing-project
scribetronic initHacking on scribetronic itself? See Local development below for a
git clone+npm linkflow.
The CLI does not automatically seed your voice — you do that explicitly with scribetronic style (next step).
scribetronic style # Seeds scribetronic/style/writing-style.md from the template, then opens it in $EDITOR
scribetronic style --reset # Overwrite with the template (asks for confirmation)The first run copies a starter scribetronic/style/writing-style.md into your project. After that, edits open it in $EDITOR (falls back to $VISUAL, then vi). On a non-TTY (CI, automation), it just prints the path.
Every long-form and short-form skill reads from this file before generating anything — that's how the pipeline stays in your voice instead of generic AI tone.
Inside Claude Code:
/agenda # Plan the next 7 days
/write # Draft a piece (long-form or short-form)
/write-publish # Polish + run quality gates + mark ready
That's the whole loop.
- 23 skills covering planning, drafting, editing, and quality
- 3 orchestrators that compose the pipeline
- 6 long-form formats (newsletter, devlog, hot take, how-to, launch retro, manifesto)
- 8 short-form formats (X vs Y, listicles, observations, carousels, threads, etc.)
- 6 shared utilities (style, editing, AI-slop check, style extraction, style refinement, parallel review)
- A small CLI to install, list, and inspect skills
No accounts. No SaaS. Plain markdown files in your repo.
| Document | Description |
|---|---|
| Architecture | Repo layout and skill organization |
| Plugin Mode | Marketplace architecture, hooks, and v0.1.x → v0.2.x migration |
| Philosophy | Why scribetronic exists and what it bets on |
| Skills Reference | Detailed docs for all 23 skills |
| CLI Reference | Full command documentation |
| Customization | Editing rules.yaml, publish-config.yaml, voice |
| Contracts | Pipeline data contracts (week IDs, plan schema, etc.) |
| Tutorials | Step-by-step walkthroughs |
| Skill | What it does |
|---|---|
/agenda |
Plans the next 7 days of content from your backlog and goals |
/write |
Drafts a single piece in the chosen format |
/write-publish |
Polishes a draft, runs quality gates, marks it ready |
| Skill | What it does |
|---|---|
/writing-style |
Your voice baseline — read by every other skill |
/editing-pass |
Structural + line edits, preserving voice |
/ai-slop-check |
Detects generic AI patterns, hedge words, em-dash abuse |
/style-extract |
Extracts a style profile from existing writing samples |
/style-refine |
Proposes evidence-backed deltas to scribetronic/style/writing-style.md from real edit history |
/review |
Parallel multi-focus review (voice, structure, slop, hook, closer, optional factual) — N subagents concurrent, severity-grouped report |
| Skill | Format |
|---|---|
/long-form-weekly-newsletter |
The flagship weekly piece |
/long-form-monthly-devlog |
Build-in-public retrospective |
/long-form-hot-take |
Pointed opinion on a current topic |
/long-form-how-to |
Tutorial-style walkthrough |
/long-form-launch-retro |
Post-launch lessons learned |
/long-form-manifesto |
Belief-driven essay |
| Skill | Format |
|---|---|
/short-form-x-vs-y |
Comparison post |
/short-form-listicle |
Numbered list |
/short-form-observation |
One-sharp-thought post |
/short-form-motivational |
Energy / mindset post |
/short-form-present-vs-future |
Then-vs-now framing |
/short-form-thread-from-longform |
X/Twitter thread derived from a long-form piece |
/short-form-carousel-li |
LinkedIn carousel |
/short-form-voice-adjustments |
Re-tune any short post to a target platform |
Seven commands.
scribetronic init [path] # Scaffold project + register plugin marketplace
scribetronic style [--reset] # Seed or edit writing-style skill
scribetronic list # List bundled skills (mirrors the marketplace)
scribetronic info <skill> # Show skill metadata
scribetronic update [path] # Refresh marketplace registration in settings.json
scribetronic doctor [path] # Verify the install end-to-end
scribetronic uninstall [path] # Disable the plugin (leaves your content intact)See docs/cli-reference.md for full flags and examples, or docs/plugin-mode.md for the marketplace architecture.
Monday → /agenda (plan the week)
Tue–Wed → /write long-form (draft the flagship piece)
Thursday → /write-publish (polish, quality gates, ship)
Fri–Sun → /short-form-* x5 (derivatives across platforms)
One source piece, five derivatives. Compounding output without compounding effort.
- Voice first. Generic AI writing is a liability. Every skill reads
/writing-stylebefore generating anything. - Quality gates between steps.
/ai-slop-checkand/editing-passrun on every draft before it's marked ready. - Skills, not chains. Each skill is independent and inspectable. Compose them however you want.
- Plain files. Your content lives in your repo as markdown. No vendor lock-in, no proprietary database.
- Refined daily. This toolkit comes from the writing pipeline I run for my own newsletter. It evolves with use.
If you want to hack on scribetronic itself (before publishing to npm, or to contribute):
git clone https://github.com/r-bart/scribetronic.git
cd scribetronic/packages/cli
npm install
npm run devSee CONTRIBUTING.md for the full contributor guide.
- v0.1 — Core skills + CLI (
init,style,list,info), published to npm. Current. - v0.2 — Harder
styletest cases;update --skills-onlycommand for in-place skill upgrades. - v0.3 — Multi-author voice profiles;
list --treeshowing the inheritance graph. - v0.4 — Plugin marketplace integration for Claude Code (
/plugin add scribetronic). - v0.5 — Calendar export (ICS, Notion, Google Calendar) and analytics hooks feeding back into
/agenda. - v1.0 — API stability commitment.
Feedback and ideas: open an issue.
- devtronic — The engineering counterpart. Same philosophy, applied to code.
- See RECOMMENDED-SKILLS.md for skills and plugins that pair well with scribetronic.
MIT © 2026 Roberto Díaz