iankiku/forwward-teams

write

(forwward) Produces founder-voice blog posts, X/Twitter threads, and newsletters that sound like a real person sharing hard-won lessons, not a marketing department. Triggers on blog posts, threads, newsletters, content writing, or any founder-voice content.

First seen Mar 20, 2026

Installation

$ npx skills add iankiku/forwward-teams --skill write

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from iankiku/forwward-teams · top by installs.

npx skills add iankiku/forwward-teams

Browse all from iankiku/forwward-teams

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 18
License LICENSE
Default branch main
Open issues 0
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,193 B
  • docs SUMMARY.md 270 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 40 installs

SKILL.md

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...")