Skip to content

lennoxsaint/Threadify-workflows / plugins/claude/skills/threadify-buyer-questions-to-content

threadify-buyer-questions-to-content

Verified

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.

FileKindSize
SKILL.mdskill md8.8 KB
references/threadify-001.mdmarkdown3.7 KB
references/workflow-manifest.jsonconfig2.6 KB
references/workflow-readme.mdmarkdown1.8 KB

references/workflow-readme.md

View on GitHub
# Buyer Questions to Content

Use this workflow to turn real buyer questions into a private content brief or draft. Start from sources the user supplies. Follow [Threadify-001](../../docs/threadify-001.md) only if the owner wants a current Threadify drafting, save or delivery capability.

Ask:

> Turn these buyer questions into one deidentified content draft. Tell me whether the idea comes from one source or a repeated pattern.

## Run the workflow

1. Import the minimum factual question evidence and private source reference. Do not copy the full conversation into the content record.
2. Run `questions-to-content`. Treat one question as `single` evidence. Use `repeated` only when distinct source records support the same underlying question. Repeated comments from one person or duplicated text do not increase the count.
3. Remove names, handles, links, unusual personal facts and other unnecessary identifiers. Deidentification reduces exposure; it is not a promise that reidentification is impossible.
4. Draft one useful answer within the evidence. Do not present one person's question as a market trend, customer majority or sales signal.
5. Show the exact draft, evidence label, distinct source count, uncertainty and private source map. Obtain exact approval before any provider save, schedule or publication.
6. Run `save-content` only for the approved local candidate. A local save is not a provider draft or publication.

```sh
node ~/.threadify-workflows/current/cli/bin/threadify-workflows.mjs conversations questions-to-content --state /absolute/private/directory
```

From a source checkout, use `node bin/threadify-workflows.mjs conversations ...`. If an optional content tool is unavailable, return the same local draft and manual next step. Keep feedback local unless the owner separately opts into sharing its exact text.
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 196kUpdated Claude CodeCodexVerifiedInstall