threadify-whats-working SKILL.md skillB
threadify-whats-working from lennoxsaint/threadify-workflows is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add lennoxsaint/threadify-workflows/threadify-whats-working@git:20261014.f89b010Pins git:20261014.f89b010 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- B, 16 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- lennoxsaint/threadify-workflows
- Path
skills/threadify-whats-working/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261014.f89b010, committed Oct 14, 2026
- First version recorded
- Oct 14, 2026
- Size
- 10,187 bytes
- Repository stars
- 7
- License
- a license file GitHub does not identify
Check every Threads post you published this year against your own median views, show which kinds of posts Threads is killing and the one kind it still pushes 100x, then have Threadify write three posts in that winning pattern with tracked Auto Plugs and schedule them only after one exact approval. Use when someone asks "is Threads dead", "what's actually working on Threads", why their views dropped, or which of their posts get pushed.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# What's Working Threads isn't dead. Most of your posts are. This workflow reads every post you published this year, labels each one against **your own median views** (dead, stuck or alive), answers "is Threads dead for me?" month by month, names what the dead posts share and the one kind of post Threads still pushes hardest, then asks Threadify to write three new posts in that pattern, each with a tracked Auto Plug, and schedules them only after one "yes". It works the same in Claude Code, Codex and ChatGPT. Follow [Threadify-001: setup and first-loop video](references/threadify-001.md) before the first connected call. A connection never authorizes scheduling. Only the owner's "yes" to the exact approval packet does. ## Rules - Follow [demo feedback rules](references/demo-feedback-rules.md) for the whole run. If `~/.threadify/owner-overlay.md` exists, read it too and follow it; it is private, so never quote it into posts, files you publish or receipts. - Every number comes from the tools or the script. Missing data stays unknown: say "unknown", never 0. Describe what happened, never what will happen: no post or pattern "will" go viral. …
Read the whole file at its exact version.
How to install
mdr add lennoxsaint/threadify-workflows/threadify-whats-working@sha256:168ac67fb6a26c49The line at the top of this page pins the label git:20261014.f89b010, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_l44ayawhyizjahnb)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, all committed on Oct 14, 2026. Its first recorded version is graded A and its latest B.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261014.f89b010 latest | 2026-10-14 | f89b010 | 10,187 B | B | view · diff |
| git:20261014.c16a593 | 2026-10-14 | c16a593 | 9,771 B | A | view · diff |
| git:20261014.e148fef | 2026-10-14 | e148fef | 9,554 B | A | view · diff |
| git:20261014.88addd0 | 2026-10-14 | 88addd0 | 9,275 B | A | view |
Audit of the latest version
- fail: No link to a raw IP address (matched: http://127.0.0.1:8047)
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (10187 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No script tag
Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.
Source
lennoxsaint/threadify-workflows · 7 stars · license a license file GitHub does not identify · pushed 2026-11-01 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_l44ayawhyizjahnb GET https://markdownregistry.com/api/v1/resolve?ref=lennoxsaint/threadify-workflows/threadify-whats-working GET https://markdownregistry.com/api/v1/blob/168ac67fb6a26c495f9a9b77116332d90180648177fe238ef2b7f7960113abda
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from lennoxsaint/threadify-workflows
Every file in lennoxsaint/threadify-workflows