القائمة
Use when the user has an existing post (tweet, blog, Reddit thread) and wants variants for other platforms, with fresh related context layered in.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Pull a multi-source social digest (Reddit, Hacker News, blogs, X) on a topic and summarize what people are actually saying right now. Use when the user wants the current conversation around a specific subject.
Use when the user wants to find recent posts semantically similar to a piece of content (URL or text). Embeds the input + ranks candidates across Reddit / HN / blogs / X by cosine similarity. Use for repurpose workflows or "what else is being said about this" research.
Track mentions of a topic across Reddit, Hacker News, blogs, and X over a multi-day window. Use when the user wants to know whether something is getting picked up, how mentions are trending, or to monitor a launch/release over time.
Surface what is blowing up right now in a niche across Reddit, Hacker News, blogs, and X. Short-window (6h default) scan reranked by ZeroEntropy. Use when the user wants the current pulse of a space, not a curated read on one topic.
Surface the influential voices (authors, accounts, subreddits) on a topic across Reddit, Hacker News, blogs, and X. Use when the user wants to know who is shaping the conversation, not what is being said.
Use when the user wants 5-10 candidate H1 titles + meta descriptions for a blog post, SEO-optimized for a focus keyword. Faster than `notslop-write-blog-post`; produces titles only, no body.
| name | notslop-repurpose |
| description | Use when the user has an existing post (tweet, blog, Reddit thread) and wants variants for other platforms, with fresh related context layered in. |
| Capability | Required | Providers (BYOK) | Setup | Cost |
|---|---|---|---|---|
| Pull social signal (Reddit/HN/blogs) | yes | built-in, no key needed | — | free |
| Rerank by relevance | yes | ZeroEntropy zerank-2 | PROVIDERS.md#zeroentropy-rerank--embed | free tier OK |
| Embed for cross-source dedup | yes | ZeroEntropy zembed-1 | PROVIDERS.md#zeroentropy-rerank--embed | free tier OK |
| Scrape X posts | only if topic needs X data | Orthogonal (ScrapeCreators) | PROVIDERS.md#x-twitter--via-orthogonal | ~$0.02/handle, $10 free at signup |
Same as notslop-write-post: requires notslop init and a ZeroEntropy key.
Read the source content. If it's a URL, fetch via Bash:
curl -sL "<URL>" | head -100 # or use a more targeted fetch
If the user pasted the content directly, use that.
Identify the core insight (the ONE thing the post is saying). Strip the platform-specific framing.
Pull recent related discussions using find-related (more precise than a generic digest because it embeds the source content itself):
notslop find-related "<URL_OR_PASTED_TEXT>" --since 14d --top 10 --format json
Parse the JSON related array. Each entry has post.title, post.source, post.url, and similarity score.
Write the adapted version for each target platform the user asked for. The adapted version:
Show all variants. Highlight where you added fresh context.
User: "Repurpose https://x.com/karpathy/status/123 for LinkedIn"
→ Read source: karpathy's quick benchmark thread on Claude 4.5
→ Identify insight: "4.5 is better at code but slower"
→ Bash: npx notslop@latest digest "Claude 4.5 benchmark" --since 7d --format json --top 5
→ Find: 2 more recent benchmarks discussing same trade-off
→ Write LinkedIn version: longer-form, professional tone, cites Karpathy + 2 newer threads, calls out the trade-off concretely
LinkedIn draft (~1100 chars):
Claude 4.5 is better at code but noticeably slower. That's the trade-off Karpathy flagged on X last week, and the follow-up data is starting to confirm it.
Three data points from the last 7 days:
- Karpathy's bench: ~18% improvement on multi-step coding tasks, ~30% latency increase
- An r/LocalLLaMA thread reproducing the result on a 6-file refactor
- An HN comment from a YC engineer reporting the same pattern in production
The pricing change on Sonnet pushed people to test 4.5 in workloads where they previously used Haiku. Latency lands differently when the work is interactive vs batch. Worth measuring on your own stack before committing.
See examples/example.md for the full walkthrough.