threadify-30-day-viral-vault SKILL.md skillA
This file is byte-identical to the first copy the registry indexed, one of 3 indexed copies. Same content hash, so the same checks give both the same grade.
threadify-30-day-viral-vault 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-30-day-viral-vault@git:20261014.88addd0Pins git:20261014.88addd0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- lennoxsaint/threadify-workflows
- Path
plugins/claude/skills/threadify-30-day-viral-vault/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261014.88addd0, committed Oct 14, 2026
- First version recorded
- Oct 9, 2026
- Size
- 4,667 bytes
- Repository stars
- 7
- License
- a license file GitHub does not identify
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.
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
# 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 …
Read the whole file at its exact version.
How to install
mdr add lennoxsaint/threadify-workflows/threadify-30-day-viral-vault@sha256:034631483f2ceed3The line at the top of this page pins the label git:20261014.88addd0, 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_jdpu2d4hyydcib4g)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Oct 9, 2026 and Oct 14, 2026, about one every 2 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261014.88addd0 latest | 2026-10-14 | 88addd0 | 4,667 B | A | view · diff |
| git:20261009.e7abeed | 2026-10-09 | e7abeed | 4,411 B | A | view · diff |
| git:20261009.a74c9f4 | 2026-10-09 | a74c9f4 | 4,409 B | A | view · diff |
| git:20261009.bb038f3 | 2026-10-09 | bb038f3 | 4,410 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (4667 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 link to a raw IP address
- pass: No script tag
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_jdpu2d4hyydcib4g GET https://markdownregistry.com/api/v1/resolve?ref=lennoxsaint/threadify-workflows/threadify-30-day-viral-vault GET https://markdownregistry.com/api/v1/blob/034631483f2ceed33c878903c436411e1d7a404a0355fcd6497a7c0ab1348337
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