threadify-buyer-questions-to-content 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-buyer-questions-to-content 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-buyer-questions-to-content@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-buyer-questions-to-content/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261014.88addd0, committed Oct 14, 2026
- First version recorded
- Oct 9, 2026
- Size
- 1,971 bytes
- Repository stars
- 7
- License
- a license file GitHub does not identify
Turn supplied buyer questions into deidentified local content with honest single-or-repeated evidence labels. Use when the owner wants a draft or brief grounded in conversation evidence.
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
# Threadify Buyer Questions to Content Read `references/threadify-001.md`, `references/workflow-manifest.json` and `references/workflow-readme.md` from this skill directory. Use the installed exact-release CLI at `node ~/.threadify-workflows/current/cli/bin/threadify-workflows.mjs conversations`; when `THREADIFY_WORKFLOWS_HOME` was set during installation, resolve the same path below that state root. In a source checkout, use `node bin/threadify-workflows.mjs conversations`. Import minimal question evidence into the private conversation state. Run `questions-to-content`. Label one source `single`; label a pattern `repeated` only when distinct sources support the same underlying question. Duplicates and repeated messages from one person do not increase the count. Remove names, handles, direct links and unnecessary identifying details before drafting. Say that deidentification is a risk reduction, not perfect anonymity. Do not turn a single question into a trend or treat questions and likes as sales evidence. …
Read the whole file at its exact version.
How to install
mdr add lennoxsaint/threadify-workflows/threadify-buyer-questions-to-content@sha256:554c031e6a8993daThe 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_fl2awjp2jxuh5jxu)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Oct 9, 2026 and Oct 14, 2026, about one every 5 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261014.88addd0 latest | 2026-10-14 | 88addd0 | 1,971 B | A | view · diff |
| git:20261009.bb038f3 | 2026-10-09 | bb038f3 | 1,715 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 (1971 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_fl2awjp2jxuh5jxu GET https://markdownregistry.com/api/v1/resolve?ref=lennoxsaint/threadify-workflows/threadify-buyer-questions-to-content GET https://markdownregistry.com/api/v1/blob/554c031e6a8993da7d3a72033dffc0b2e12cae75f4a5a578000d80e4a78460c1
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