Skip to content

lennoxsaint/Threadify-workflows / plugins/claude/skills/threadify-30-day-viral-vault

threadify-30-day-viral-vault

Verified

Plan 30 days and prepare six rights-cleared Threads posts daily while revealing only the next unresolved card. Use for a 30-Day Viral Vault or a six-post one-at-a-time daily queue.

30-Day Viral Vault

Follow references/creator-system.md and references/creator-engine.md. Use this skill's bundled scripts/creator.mjs with Node 18+ and a dedicated private state directory. The engine performs no provider calls.

Start or resume

Run vault30-status, then vault30-continue before starting a new plan. Resume an unresolved or ambiguous card before preparing another day. Never display, summarize or tease a later card while a current card remains.

For a new plan, confirm:

  1. The intended account and IANA timezone.
  2. reach_first, balanced or lead_first. Balanced and lead-first require one current verified offer.
  3. Exactly six distinct local posting times. Use fresh connected best-time/calendar evidence when available; otherwise ask the user for the times. Resolve timezone gaps or duplicated civil times explicitly.
  4. The user understands that this workflow uses patterns from previously successful posts but does not guarantee virality, followers or leads.

Create the 30-day blueprint with vault30-plan. It contains slots only. Prepare copy for the current day just in time.

Prepare today's six

Build exactly two greatest_hit, two viral_vault, and two my_vault cards. Require four proven, two challenger; two each of broad, expertise, and personal; at least three viral_structure values including one listicle; and at most one earned CTA.

  • Reach first: zero earned CTAs and no lead-oriented requirement.
  • Balanced: exactly one offer-aligned card, with at most one earned CTA.
  • Lead first: exactly three buyer-problem cards, with at most one earned CTA.

Greatest Hits may use exact_repost only when the connected/user evidence proves that account owns the source. Every other card uses literal_fill_in only when current evidence proves ownership, license or permission. Declare every source-specific person, brand, number, claim, example, topic, personal proof and CTA destination as a placeholder. The template must reconstruct the exact source, and verified replacements must reconstruct the exact final post. A missing right, source span or replacement fact blocks that candidate. Do not silently switch to structure-only or cross-fill another lane.

Carry prior leave_for_tomorrow cards before topping up to six. Their content must remain byte-for-byte unchanged; only a new evidenced time suggestion may be appended. Save connected drafts with exact resolved copy when a deterministic provider surface exists. Never send source text to provider generation and never use generate_content for these cards.

Call vault30-add-day only after all six cards, rights proofs and suggestions pass. The engine returns only card one.

Review exactly one card

Use vault30-next. Show only its returned card, source lineage, rights basis, literal template mapping, exact final parts, validation, and proposed local time.

  • edit: persist the exact edit, revalidate, and show the same card again.
  • approve: require fresh validation and exact owner approval, then persist the schedule intent.
  • edit and approve: bind fresh validation and approval to the exact edited copy.
  • skip: preserve the copy for tomorrow and advance.
  • reject: close the card and advance.

Connected approval is not scheduling by itself. After vault30-decide, refresh account, timezone, facts, rights, provider validation and calendar. Use vault30-begin-attempt to persist the exact idempotent request before calling schedule_post. Never call publish_now. Then call get_schedule_status and use vault30-reconcile only when account, draft, copy, time, idempotency id and scheduled state match exactly.

An unavailable or ambiguous result stays approved_unscheduled, queues no retry and blocks the next card. Inspect provider state before doing anything else. Disconnected cards may use vault30-complete-local after exact approval; say “reviewed locally,” not “scheduled.”

After six decisions, show only a compact state rollup. Day 30 ends new packet generation. Preserve private state for recovery and keep source bodies, facts, drafts, IDs and receipts out of public artifacts.

Demo feedback rules

Before the first step, read the demo feedback rules at the end of this file and follow them for the whole run. If ~/.threadify/owner-overlay.md exists, follow it too; it is private, so never quote, publish or upload it.

Demo feedback rules (full text)

Corrections creators gave Threadify workflows while running them live, turned into rules so nobody has to give the same feedback twice. Every workflow follows these; a workflow's own rules win where they are stricter. A private overlay at ~/.threadify/owner-overlay.md, when present, adds the owner's personal preferences; read it, follow it, and never publish, quote or upload it.

Pace and confirmations

  • Keep going until the agreed scope is finished. Never stop just to report progress.
  • At each checkpoint, state what is done, what remains and an honest time estimate, without being asked.
  • Make routine choices yourself (titles, posting times, picks between close options) and state the choice in one line.
  • Ask for one confirmation per irreversible action. Never ask the same confirmation twice.
  • Put every action of a run into one approval packet that says what each does. After the single yes, run to the end and read each result back. Never ask again for anything already inside the packet.
  • The owner's "yes" in chat is the approval. If the host (an approval queue, a hook or a gate) still holds the call, say where to approve it in one line and wait. Never route around it or retry another way. If the rule holding it looks stale (it asks for something the owner has since changed), say so and offer to fix the rule itself, with its own yes, then retry once.
  • Build for whoever runs the workflow: find or ask what actually makes them money, confirm it, and never hardcode one creator's offer, handle, tools or data.
  • Plan for the owner's setup, not a developer's: no-code actions first. Say "here's what I'll do, in this order, and why. OK?", then work most important first. Start slow work, ship the quick win, then finish it.
  • Look it up before you ask. Never ask the owner something their connected account, files or past posts can answer, and never offer an action the product cannot do.
  • Ask questions in batches of at most three, each with your recommended answer. Use the host's native question tool when it has one.
  • Run commands yourself. Never hand the user a terminal command you could run.
  • In step-by-step demo mode, do exactly one step, then wait for "next".

Output on screen

  • Show generated posts and their Auto Plugs in full, in chat, as plain text. Never show only a file path, a summary, or text inside a card, box or next-step prompt.
  • Show Threadify's generated drafts exactly as returned. Don't audit, polish or rewrite them unless the user asks.
  • After any correction, print the whole set again (every post and every Auto Plug) with the change applied. Never show only the changed item or a diff.
  • Make only the edit the owner asked for. Keep everything else exactly as it was, keep what they praised, and say what you removed.
  • When a workflow writes posts, offer an edit-in-place step (editable text with a Done button) that keeps the originals for comparison. Skip it when the owner says they won't edit.
  • Narrate each step in plain, viewer-facing language, as if the audience is watching the screen.
  • Open what you produced (page, tab or file) and confirm it opened before saying it is ready.
  • Review pages and videos must load and play quickly on a phone.
  • Work in the background or the in-app browser. Don't take over the presenter's screen.
  • Keep tables and visuals phone-readable: few columns and short cells.

Truth and numbers

  • Use real, current account numbers, refreshed at run time. Never use stale or estimated figures.
  • Drop metrics that prove nothing (zero or unknown outcomes) instead of padding with them.
  • Show real screenshots of what you describe. For a fix, show before and after.
  • Hide only real secrets (keys, tokens, IDs, emails). Never blur the evidence the viewer needs.
  • Label any hook without performance evidence as unproven. Never call it proven.
  • Keep each claim exactly as strong as the data: "one of my most viewed" stays "one of", a median is not an average, and a rough rate stays rough.

Copy

  • Start from the owner's own material before writing from scratch: past posts and threads, testimonials, receipts, screenshots and notes. Use the real story or proof you find there.
  • Base each post on a real outlier post turned into a template with placeholders: copy its whole structure (hook, line breaks, list shape, length and ending), not just its hook. Make the first 3 to 5 words the strongest.
  • The hook carries a benefit for as many readers as possible. Use specific numbers, but never so specific that they shut most readers out.
  • Never lead with numbers that kill social proof (a weak count like "1 signup" or "0 paid"). Frame them as the discovery or the win.
  • Write with diary energy: what just happened, told like you just found out.
  • Never reuse a hook, template or proof point within one batch.
  • Listicles go from the hook straight into the numbered list: no analogy, setup paragraph or "here are N things" bridge.
  • Short post: a one-sentence hook that opens a loop. Long thread: a three-sentence hook with two loops that ends in a colon.
  • Be concise: short posts under about 350 characters (unless the workflow asks for a long thread), CTAs about 100 to 250 characters, and cut anything that does not earn its place.
  • End each post with a grand, bold, emotional "so what" line for the reader that flows from the sentence before.
  • Copy follows the channel's casing: lowercase on Threads (proper nouns kept), the site's own casing on the site and in offers.
  • CTAs must be relevant, specific and seamlessly integrated. Point to the product, not the workflow name, and include a real number or social proof. Model each Auto Plug on the plugs that got the most clicks. A proven plug shape: one line from the post's subject to the product, one line of pain, the product as the fix, a free-to-try or social-proof line, then the offer's plain link (Threadify tracks clicks itself, so no tracking tags).
  • Reuse the offer the account already has for the product. Never create, rename or duplicate an offer per run, episode or rehearsal; the Auto Plug carries the run's specific message.
  • Remove AI tells and hedging ("not because X, but because Y", vague abstractions, qualifiers).
  • Use plain words and no internal jargon a viewer would not know.

Failure handling

  • If a dependency stalls, switch to the fallback or the files already provided and say so. Never wait silently.
  • On failure, report the exact error in one line, then retry the way the workflow was meant to run.
  • After a rehearsal the user asked for, cancel only the test schedules and drafts that rehearsal created, and read back the result.
  • When a redo replaces a draft or a scheduled post the run created, delete the replaced draft and cancel its schedule, then read the list back.
  • When the user corrects output during a run, apply the correction to every remaining item, keep a visible running list of corrections, and at the end remind them to write that list back into the workflow so it is never needed again.
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 196kUpdated Claude CodeCodexVerifiedInstall