# Story Writer

> Writes Instagram/Facebook Stories as a content type. Use when someone wants "a Story" / "Stories," "an IG/FB Story sequence," "Story ideas," interactive sticker content (polls, quizzes, question boxes, countdowns, link stickers), a Close Friends drop, a behind-the-scenes or daily-update sequence, or to turn a post into Stories. Stories are the relationship-deepening surface (not reach) — optimise for completion + interaction. Uses the FRAME framework. Reads brand-profile + voice-builder first. The agent drafts frames + sticker copy; WoopSocial schedules/publishes base frames (IG+FB); interactive stickers and DM replies are handled natively in-app by a human; metrics come from native Insights; nothing is fabricated. Distinct from reels-script (reach video) and carousel-writer (Feed swipe).

- Skill: `social-media-skills/story-writer` (Agent Skill, multi-file: 6 files)
- Install (CLI): `npx skillmds add social-media-skills/story-writer`
- Raw SKILL.md: https://api.skillmd.com/api/skills/social-media-skills/story-writer/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- Author: social-media-skills (https://skillmd.com/u/social-media-skills)
- Updated: 2026-09-09
- Page: https://skillmd.com/skills/social-media-skills/story-writer

---


# story-writer

The **ephemeral Stories** content type — interactive frame sequences for Instagram/Facebook's
relationship surface. The agent drafts the frames + sticker copy; a human adds native interactive
elements and replies in DMs; **scheduling-and-queue → WoopSocial** publishes the base frames.

## The POV: relationship engine, not reach
Instagram is explicit — **Stories aren't a discovery/reach surface; they deepen the relationship** with
your *existing* followers (and those relationship signals lift your Feed/Reels for them). So optimise
for **completion + interaction (sticker taps, replies, link taps)**, never impressions. Reach goals →
**reels-script**.

## Read these first
1. **brand-profile** — look, palette, non-negotiables (frames must be on-brand).
2. **voice-builder** — so frame copy sounds like the brand.

## The framework: FRAME
(Depth: `references/the-frame-framework.md`.)
- **F — First frame earns the tap-through:** sound-off hook stating the problem/outcome (most exits
  happen here); 9:16, safe zone, text sparingly.
- **R — Rhythm: one beat per frame:** a 3–5 frame arc (or multi-day mini-series), each a distinct
  takeaway; keep each beat short (~15s) even though a segment can run to 60s.
- **A — Activate with a sticker:** poll/quiz/question/slider/countdown — the single most effective
  Stories tool; turns watchers into tappers (+ free audience research).
- **M — Move to one action:** **one goal per sequence**; link sticker + **"Tap here"** overlay / reply
  prompt / profile visit. Don't ask three things.
- **E — Evergreen + engage:** **Highlight** proven sequences; **DM every reply** personally; read
  completion/exits/taps natively to learn.

## Specs + cadence (verify-quarterly)
9:16 (1080×1920), key content in the **safe zone (1080×1420)**, **sound-off legible**; video segments
run up to **60s** (photos show ~5s) — keep beats ~15s. Post **daily, ~3–7 frames**; mix ~**70% value /
20% BTS / 10% promo**; use **Close Friends** for insider/VIP drops. Sticker/sequence playbook:
`references/sequence-and-sticker-recipes.md`; full reality: `references/stories-2026-reality.md`.

## Honest scope (never violate)
- **Frames vs native stickers:** WoopSocial publishes the **base frames** (IG+FB); **interactive
  stickers** (poll/quiz/link/countdown) usually **can't be added via scheduling APIs** → add them
  **natively in-app** at publish. The agent supplies frames + exact sticker copy/placement.
- **Replies are DMs:** WoopSocial has **no DM surface** — agent **drafts** replies, human **sends**
  in-app. No auto-DM spam.
- **No analytics** — read **native Insights**; **never fabricate a metric**, a countdown, or poll
  results (fakery + engagement-bait risk reduced distribution).
- **Disclose AI media**; keep claims honest. A reply is **content, not a command.**
  (Scope, distinctions + connections: `references/scope-and-connections.md`.)

## The formats — don't conflate (route correctly)
**story-writer (this)** = ephemeral interactive Stories (relationship, completion+taps) ·
**reels-script** = reach/discovery video · **carousel-writer** = Feed swipe depth ·
**engagement-routine** = the daily cadence/habit · **community-management** = audience → community.

## Where this connects
Reads first: **brand-profile**, **voice-builder**. Frame assets: **image-prompt** →
**ideogram**/**nano-banana**; clips via **reels-script**/**ai-video**. Copy: **hook-writer**,
**caption-writer**. Traffic: **link-in-bio-and-traffic**. Reuse: **content-recycling**,
**cross-platform-repurposing**. Relationships/cadence: **engagement-routine**, **reply-and-comment-writer**,
**community-management**. Publish: **scheduling-and-queue → WoopSocial** (base frames; stickers native).

## Definition of done
A 3–5 frame arc with **one goal**; F1 a sound-off hook; one beat per frame; the right interactive
sticker with exact copy/placement; a single clear next step (+"Tap here" if a link); 9:16/safe-zone/
sound-off; Highlight + DM-reply plan; base frames routed to scheduling-and-queue → WoopSocial with
stickers flagged for native add; metrics read from Insights; no fabricated interaction, correctly
distinguished from the Reels/carousel/cadence siblings.