mcpField
W
write

write

github.com/iankikuMarketing & growth1842 installsUpdated 13w ago
Repository

About write

write is a content-writing skill for founders who want personal, experience-based posts rather than corporate copy. It provides voice rules and structures for X/Twitter threads and blog posts, emphasizing specific lessons and actionable takeaways.

Key features

  1. 01First-person founder voice guidelines
  2. 02X/Twitter thread structure
  3. 03Blog post outline
  4. 04Specific, evidence-based storytelling
  5. 05Anti-pattern guidance

Use cases

  1. 01Drafting a founder's X/Twitter thread
  2. 02Structuring an experience-based blog post
  3. 03Turning a hard-won lesson into actionable content

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/iankiku/forwward-teams --skill write

After installing, type/writein Claude Code to confirm it loaded.

Details

From the project README

Write — Founder Voice Content

Sound like a real person sharing hard-won lessons, not a marketing department.

Voice Rules

  1. First person, always. "I built" not "We implemented."
  2. Specific over general. "37 tools across 9 domains" not "many tools."
  3. Show the mess. The failed draft, the 3am realization, the thing you'd do differently.
  4. One idea per piece. If you can't tweet the core insight in one sentence, refocus.
  5. End with value. Reader leaves with something they can use today.

X/Twitter Thread Format

Tweet 1 (Hook):  Bold claim or surprising result. Stop the scroll.
                 Max 280 chars. No hashtags. No "thread incoming."

Tweet 2-3:       Context. Why this matters. What problem you were solving.

Tweet 4-7:       The meat. What you did, what happened, what you learned.
                 Numbers, screenshots, code snippets.
                 Each tweet stands alone AND flows in sequence.

Tweet 8-9:       Counterintuitive insight. What most people get wrong.

Final tweet:     One-sentence takeaway they'll screenshot.
                 Optional: link to blog for depth.

Blog Post Structure

  1. Hook — The result or surprise (not backstory)
  2. Problem — What you were up against
  3. Journey — What you tried (including what failed)
  4. Solution — What worked and why
  5. Lessons — What you'd tell someone starting today

What Makes Content Share-worthy

  • Contrarian + evidence: "Everyone says X, but here's what happened when I tried Y"
  • Specific numbers: revenue, users, time saved
  • Vulnerability + competence: admit mistakes while showing mastery
  • Actionable: templates, frameworks, step-by-step

Anti-Patterns

  • Throat-clearing ("In today's fast-paced world...")
  • Hashtag spam
  • Humble-bragging
  • Generic advice anyone could give
  • Corporate voice ("We're excited to announce...")

Comments

Markdown supported