agentsclimarketplace
Sign in

Write substack

Skill gokul-kulkarni/content-studio-plugin/skills/write-substack

Writing phase for Substack — draft a publish-ready long-form essay from the LOCKED master content, in Substack's native reading-and-email format. Use whenever someone wants to write a Substack post, essay, article, or newsletter, or turn a finalized idea into long-form prose. Substack rewards clarity and scannability, not visual tricks. Do not run until the content is locked and approved (see explore); to fix an existing rough draft, use refine.From its SKILL.md

Install
npx -y skills add gokul-kulkarni/content-studio-plugin --skill write-substack

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

4.0 KB, as published. Nobody here has run it

Write — Substack

Turn the locked master content for $ARGUMENTS into a long-form essay. Substack is a reading-and-email platform — most reads happen in the email client, and the enemy is the wall of text.

Preconditions & change protocol (read first)

  • Content first. Only render once the master content is locked and the person has approved it (Phase 1 / explore). If it isn't, stop and finalize the content first.
  • One spine, faithful rendering. This is the same thesis as the LinkedIn carousel and Medium article, rendered as prose — it reinforces, never duplicates. Never paste carousel slides in as essay sections or images.
  • Same running example as every other asset.
  • Change protocol. If the person asks to change the substance after this exists, don't patch it here — update the master content (explore), re-approve, and regenerate all platform assets (refine runs the re-sync).
  • Match the person's voice — preserve first-person reflection, distinctive phrasing, and their own metaphors.

Save the essay as a Markdown file.

Structure

  • Title (#) — the strongest framing of the thesis.
  • Subtitle (####) — one line naming the specific, non-obvious shift the piece reveals (the curiosity gap).
  • Short hook opening — 1–2 tight paragraphs dropping the reader into a concrete moment, then a one-line pivot into the body ("Then we started climbing.").
  • Sectioned body with ## headers on every major beat — the single biggest fix for "people lose interest"; headers give the eye landing spots.
  • Bold lead-ins for enumerated history or steps, so the section scans even when skimmed (e.g. "Java — goodbye to the machine.").
  • A blockquote (>) around the single most quotable line — the core mental model — so it pops and is screenshot-able. Screenshot-ability is how essays get pulled back onto LinkedIn/X by other people.
  • Numbered list for any explicit progression of steps.
  • A short, open-ended ender — ideally a two-line kicker that hands the question back to the reader. If the person already wrote a strong ending, keep it.
  • At least one link out + a subscribe ask. An essay with zero links is a dead funnel step — it can't send readers to the Medium deep-dive, the previous post in the series, or anywhere that compounds. Place one relevant inline link where it's genuinely useful (not a footer dump), and end with a one-line subscribe ask. Rationale: real Substack data showed 0% click-through across every post that shipped without a link — the single biggest fixable outreach leak.
  • Series continuity — if part of a series, open by recalling where the previous piece left off and close by teasing the next (link the previous post — that's also a natural inline link).

Notes

  • Keep it scannable: a reader skimming only the title, subtitle, headers, and bold lead-ins should still get the whole arc.
  • Images are uploaded manually into the Substack editor at each section spot — the Markdown references (e.g. light-assets/2-...png) are just pointers. Keep Substack light on images (email rendering + deliverability): a shared hero plus a few section diagrams, not one per paragraph.
  • The SEO/meta description, topic categories, launch Note, and posting all live in the distribute skill — point there once the essay is drafted.
  • For the per-section image specs, use the design-brief skill once the content is locked.
  • If the input is an existing rough or overlong draft rather than locked content, use the refine skill instead (restructure, keep ideas).

Keep looking

Skills are one crate of 627,801. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.