lennoxsaint/Threadify-workflows / plugins/claude/skills/threadify-refresh-your-threads-profile
threadify-refresh-your-threads-profile
VerifiedInterview a creator, combine their niche and approved context, and create exactly three coherent Threads bio-and-profile-picture systems for owner selection, private rendering, and a safely confirmed manual or agent-assisted profile update. Use when someone asks to improve, rewrite, redesign, review, or apply a Threads bio or profile picture.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 11.1 KB |
| references/profile-contract.md | markdown | 3.8 KB |
| references/profile-patterns.md | markdown | 4.6 KB |
| references/profile-plan.v1.json | config | 13.0 KB |
| references/profile-research.md | markdown | 53.3 KB |
| references/threadify-001.md | markdown | 3.7 KB |
| references/workflow-manifest.json | config | 3.2 KB |
| references/workflow-readme.md | markdown | 4.2 KB |
| scripts/cli.mjs | script | 31.5 KB |
references/profile-patterns.md
View on GitHub# Profile patterns
Read this reference completely before drafting a Threads profile refresh. These are starting structures and review heuristics, not formulas proven to cause growth or conversion.
## Evidence labels
- **Current verified:** observed on the intended live account or in a current authoritative source.
- **Historical verified:** supported but dated; never present it as the current profile.
- **Owner attested:** supplied by the owner and appropriate to use, but not independently verified.
- **Unknown:** omit from public-facing claims or ask the owner to verify it.
Use plain language such as “designed to reduce visitor guessing.” Do not claim that a bio or picture caused follows, reach, clicks, trust, leads, sales, or revenue.
## Interview
Ask only for missing answers:
1. Who should immediately know the account is for them?
2. What recurring niche, problem, or outcome should the profile promise to discuss?
3. What is the one preferred next action: follow, read recent posts, visit a link, or something else?
4. Which proof is current and supportable? Which claims should be avoided?
5. Which three words should the profile feel like?
6. Which existing pictures may be used, who owns them, and has each depicted person consented to editing, generation, and any external provider transfer?
7. Which visual traits should be kept or avoided?
8. Is the Threads profile linked, synchronized, imported, verified, or under review elsewhere in Meta's products?
## Three bio systems
Return all three in this order and pair each with a picture direction.
### A — Clarity first
Use an audience + recurring problem/outcome + useful mechanism or content lane. Prefer concrete nouns and verbs. Make the desired next action obvious without packing in unrelated credentials.
Starting structure: `Helping [audience] [outcome] with [mechanism]. [Next action].`
### B — Authority/proof
Lead with one supportable body of work, result, role, or firsthand experience, then connect it to the audience and topic. A number is useful only when current, contextualized, and verified. Proof of work is not proof that the profile itself converts.
Starting structure: `[Specific proof]. Sharing [topic/mechanism] for [audience]. [Next action].`
### C — Personality/distinctiveness
Use a recognizable point of view, voice, or a small set of content lanes. A classic three-topic list may work as a starting point, but reconcile it with current niche evidence and one destination.
Starting structure: `Writing about: [lane 1], [lane 2], [lane 3]. Building [destination].`
## Picture layouts
Preview each option as a tiny circle as well as a larger crop.
- **Face-led portrait:** one recognizable face, near eye-level, calm or warm expression, simple background, strong subject/background separation.
- **Context portrait:** one face plus one quiet contextual cue relevant to the work; keep the cue outside the face and test whether it survives the crop.
- **Distinctive brand portrait:** preserve recognizable human features while using one repeatable color, wardrobe cue, or restrained graphic device.
Keep the face and important features inside the central circular safe zone. Avoid tiny text, busy scenes, several faces, edge-dependent details, misleading status marks, and visual clutter. Ask an unfamiliar reviewer which option best communicates the intended trait; creators are not always their own strongest photo selectors.
For an existing picture, record an opaque asset ref, SHA-256, and rights basis. For generation or editing, record consented source refs and do not invent identity features. Before uploading a likeness to an external image provider, disclose the provider and applicable privacy/retention terms, obtain explicit transfer consent, and offer a local/no-upload path. When no usable asset exists, provide a photography/edit brief and a labelled placeholder rather than pretending the picture is finished.
## Review and apply
Score every system from 1–5 for clarity, credibility, distinctiveness, desired-action alignment, and tiny-circle legibility. Have the owner choose one complete system. If they request a hybrid, revise it into a coherent candidate and show the set again.
Immediately before a live update: capture baseline hashes, preserve an authorized restorable copy of the prior picture or explicitly mark rollback unavailable, inspect sync/import and verification warnings, verify the exact Threads account, show the exact bio and frozen picture, then ask once for confirmation. Use current semantic browser/native controls or manual steps. Save once, read both fields back, and stop without retry on a mismatch or ambiguous result.
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: 468k | 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 |