lennoxsaint/Threadify-workflows / plugins/claude/skills/threadify-first-followers
threadify-first-followers
VerifiedGet your first Threads followers from zero, one person at a time. Find 10 newcomers and small active creators in your niche, then your agent stages each comment in the Threads reply box and follows at the right step while you just press Post. Comments are written in your voice from your Threadify Brain, your edits are compared with what was staged so the agent learns your voice, and the progress is tracked on a local scoreboard. Works with no post history, in any agent, with copy mode when there is no browser control. Use when someone has few or zero followers, a brand-new Threads account, or asks how to get their first followers.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 20.5 KB |
| references/generation-models.json | config | 753 B |
| references/posts.md | markdown | 3.0 KB |
| references/schedule.md | markdown | 2.4 KB |
| references/threadify-001.md | markdown | 3.7 KB |
| references/workflow-manifest.json | config | 5.9 KB |
| references/workflow-readme.md | markdown | 2.4 KB |
| scripts/casing-guard.mjs | script | 7.1 KB |
| scripts/first-followers.mjs | script | 27.5 KB |
references/posts.md
View on GitHub# First Followers: your next 3 posts (optional)
Offered once, after the engagement loop. Run it only when the owner says yes. Resolve `scripts/` against the skill directory (one level up from this file). A connection never authorizes scheduling; only the owner's "yes" to the exact packet does.
## Rules
- Threadify writes the posts with `generate_content`. Show and schedule its exact text. The only permitted change is lowercasing, keeping proper nouns, and only when the owner asks; prove it with `scripts/casing-guard.mjs` (`lower(original) == lower(final)` PASS). Never reword Threadify's output and never use `edit_draft`. Never publish now.
- No links. Without a Threadify connection or generation access, never write the posts yourself; say what is missing and the manual next step.
## Steps
1. **Write.** Make three `generate_content` calls with `strict_facts: true`: an **intro** (who you are and who you help), a **proof** post (the thing you're proud of, with its real detail) and an **opinion** (one clear take from the niche), in the owner's voice from the Brain or their answers, and `selectedModel` from [generation models](generation-models.json) (Claude Opus 5.5 when the plan allows it, Gemini as fallback; record requested and reported model). Ask for concise copy, a first line that opens a loop and a strong closing line. Keep Threadify's exact text and `draft_id` (save with `save_draft` if no draft id comes back). Show all three posts in full. If the owner wants lowercase, run `casing-guard.mjs lowercase` with the proper nouns to keep, then `check`; show "guard: lower(original) == lower(final) PASS" per post.
2. **One approval packet.** Call `best_time_to_post` (owner's timezone) and `list_scheduled_posts`; a truncated response is not an empty calendar. With no post history, say the times are general, not measured. Pick three slots in the next 24 hours, at least 3 hours apart, the first at least 30 minutes from now, none within 90 minutes of a scheduled post. Call `validate_post` on each post. Send one message:
```text
First Followers · @handle · <timezone>
1) <weekday date, local time> · intro · <unchanged | casing guard PASS>
<exact final post text>
2) ... · proof
3) ... · opinion
Action: schedule these 3 posts exactly as shown. Nothing publishes now.
Reply "yes" to schedule all 3, or "no" to schedule nothing.
```
3. **Schedule.** Schedule only on an explicit "yes". Any change to text, account or time needs a new packet and a new "yes". On "yes", re-check `list_scheduled_posts`, then call `schedule_post` three times with a stable `idempotency_key` per post (account, slot and final text hash). Unchanged text: pass `draft_id` and `content_type`. Lowercased text: pass the exact final `text` without `draft_id`. Omit `platforms` and `auto_repost`. Read back each one with `get_schedule_status`: text and local time must match the packet. If an outcome is unclear, read back before retrying, and retry only that post with the same key. On "no", schedule nothing; the posts stay as Threadify drafts. Add the scheduled count to the scoreboard's `posts_scheduled`.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 469k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |