threads-substance
/threads-substance
Pogłębia post na Threads lub krótkie media społecznościowe: nadaje mu jasną tezę, dowód i wniosek dla czytelnika zamiast samej listy linków.
- Autor
- sam666-byte ↗
- Repozytorium
- nusantara-bots ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 06.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 3
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 06.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Pogłębia post na Threads lub krótkie media społecznościowe: nadaje mu jasną tezę, dowód i wniosek dla czytelnika zamiast samej listy linków.
Oryginalny opis (EN)
Use when deepening a Threads (or short social) post so it has a clear claim, evidence, and a reader takeaway—not just a link dump or tool list.
Jak działa
- When this applies
- Inputs to gather (use what exists; do not invent)
- Quality bar (fail any → rewrite)
- Recipe
- Anti-patterns
Podgląd SKILL.md
--- name: threads-substance description: Use when deepening a Threads (or short social) post so it has a clear claim, evidence, and a reader takeaway—not just a link dump or tool list. version: 1.0.0 --- # Threads substance Turn raw intel, a link, a product note, or a half-draft into a **Threads-ready short post** with real substance: one claim, grounded evidence, and a concrete takeaway. Draft only unless the user already asked you to publish through their normal posting path. ## When this applies - User wants a Threads / short social post that **reads smarter**, not longer. - Input is X intel, a changelog, a YouTube takeaway, a workflow note, or a thin draft. - Goal is **內涵** (argument + proof + so-what), not scheduling or API publish mechanics. Do **not** use this for Lightroom outbox mechanics, pure research digests with no post ask, or long-form essays (use a teaching/explain skill first, then compress here). ## Inputs to gather (use what exists; do not invent) 1. **Seed** — the fact, ship, quote, or draft to write from. 2. **Primary sources** — dated original posts, docs, or official accounts (prefer over roundups). 3. **Audience lens** — who cares (builders, agent users, creators) and what they can do differently after reading. 4. **Voice** — match the user’s language and register. Default to short, scannable paragraphs; no corporate filler. If the seed is only a rumor or secondhand roundup, say so in the draft or refuse to present it as fact. ## Quality bar (fail any → rewrite) - **One spine**: the post has a single main claim a reader can repeat in one sentence. - **Evidence**: at least one checkable source (URL + who said it + rough date when known). No fake citations. - **So-what**: why it matters *now*, and what the reader might try, watch, or ignore. - **Not a dump**: no “10 tools” lists, no vibe-coding roundups, no engagement bait without a point. - **Rumor hygiene**: label rumor vs confirmed; omit “acquisition rumor” style noise unless the user asked to address it. - **Length**: prefer one tight post; thread only if each beat earns its own post (claim → proof → takeaway). ## Recipe ### 1. Frame (3 lines, private scratch) Write only for yourself: - **Claim**: … - **Proof**: … (source) - **Takeaway**: … If you cannot fill Proof without guessing, stop and ask for a source or drop the claim. ### 2. Optional deepen (when installed) If available and helpful, run lightly—do not paste their full output into Threads: - Ideation / angles → pick **one** angle. - Point of view → sharpen the claim. - Explain → clarify the mechanism in plain words, then compress. ### 3. Draft the post Structure (adapt, don’t label these headings in the public text): 1. **Hook** — the claim or tension in the first line (no “Here’s why…” throat-clearing). 2. **What happened** — concrete, dated, attributed. 3. **Why it matters** — product / workflow / craft insight, not hype. 4. **For you** — one actionable or judgmental line (what to try, watch, or skip). 5. **Source** — URL(s) when the platform and voice allow; otherwise keep attribution in-prose. Style rules: - Complete sentences; scannable breaks; rare emoji only if the user’s voice uses them. - Prefer plain words over buzzwords (“agent harness”, “token cost”) only when the reader needs the term—then define once. - Put identifiers, commands, and model names in backticks when the client supports markdown; otherwise keep them clear and exact. - Never invent metrics, quotes, or “Source: …” labels. ### 4. Self-check before handoff - [ ] Claim is falsifiable or clearly opinion-labeled - [ ] Proof is primary or honestly marked secondhand - [ ] Takeaway is specific to this seed (not generic “AI is moving fast”) - [ ] Would still make sense if the reader never clicks the link - [ ] Language matches the user ### 5. Deliver Return: 1. **Final draft** (ready to paste or hand to the user’s posting agent). 2. **Spine** (Claim / Proof / Takeaway) — one line each. 3. **Discarded angles** — at most two bullets, so the user can redirect. 4. **Publish note** — draft-only unless they already ordered a send; then follow their Threads / outbox / posting-agent path, do not post from this skill itself. ## Anti-patterns - Rewriting a link roundup into a slightly prettier link roundup. - Padding with “in today’s AI landscape”. - Stealing another creator’s thread structure or loading unique phrasing. - Mixing three news items into one mushy post—split or pick one. - Treating marketplace “documentation” or changelog generators as a substitute for judgment.
Pliki w paczce (3)
- SKILL.md 5 KB
- SOURCE.md 1 KB
- manifest.json 1 KB
Wersje
W bazie nie ma innych skilli o nazwie threads-substance.
Migawka bazy z 13.11.2026 · wersja paczki a7d00866f789 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100threads
Publikuje na koncie Threads przez oficjalne API wpisy tekstowe, z obrazem, wideo lub karuzelą i czyta własne ostatnie posty, z tokenem dostępu Threads. - 100social-threads
Pisze i poprawia posty, odpowiedzi i teksty premierowe na Meta Threads głosem autora: dobór formatu, uczciwy dowód, konwersacja i ścieżki konwersji. - 100social-post-writer
Pisze posty do LinkedIn, X, Threads lub Bluesky, zamieniając temat lub krótki opis w gotowy tekst. - 100social-media-platform-post
Pisze post natywny dla X, LinkedIn, Instagrama, Threads lub Bluesky, z planem mediów i hashtagami. - 100threads-post
Publikuje i planuje posty na Threads na własnym koncie przez serwer 1Social, sprawdzając limit 500 znaków i zasady obrazów. - 100threads-post-writer
Pisze post lub krótki wątek na Threads, który zaczyna rozmowę: dobiera hak pod wybraną reakcję i trzyma limit 500 znaków.