episode
Skill6 starsChanged 2 months agoMITView on GitHub
Split one source post into tier-sized drafts (teaser, main social post, longread, technical dev-log) with cross-links downward and a canonical link back to the repository. Draft-first: publishes nothing itself. Triggers: "/episode", "/adapt", "adapt this post", "make an episode".
1 other project uses a version of this.
Adopted by
Most recently taken up by
- NikolajSaudella/cuetheir own version, first seen Oct 11, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- NikolajSaudella/cue★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository100 other files it gives its agents.
- AGENTS.mdAGENTS.md
- 03Skill
- 1Skill
- agendaSkill
- alfa-search-recall-deepresearchSkill
- alpha-judgeSkill
- alpha-reviewSkill
- archSkill
- askSkill
- bibleSkill
- brainSkill
- busSkill
- canon-revisionSkill
- ccSkill
- chatgpt-syncSkill
- chat-searchSkill
- chatSkill
- claudeai-syncSkill
- coachSkill
- codex-mirrorSkill
- codex-reviewSkill
- cofounderSkill
- cofounder-watchSkill
- commentsSkill
- community-alphaSkill
- content-mineSkill
- crm-syncSkill
- declinedSkill
- dedupSkill
- defuddleSkill
- dr-fanoutSkill
- faaa-syncSkill
- faSkill
- fb-postSkill
- fb-replySkill
- fb-watchSkill
- findSkill
- fireflies-syncSkill
- five-hardSkill
- fleetSkill
- follower-onboardSkill
- geminiSkill
- gitbook-importSkill
- gmailSkill
- granola-syncSkill
- handoffSkill
- health-syncSkill
- inboxSkill
- intakeSkill
- intentionSkill
- introSkill
- issue-matchSkill
- journeySkill
- last30daysSkill
- local-chatgpt-token-healSkill
- mcpSkill
- migrateSkill
- mine-channelSkill
- n8nSkill
- notebooklmSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 42
WRITE (the model is named in each placeholder): teaser-ru/en, medium-fb (the body WITHOUT the link + a "1ST COMMENT" block), …
- Very specific: line 43
CHECK (the visibility layer): python episode_adapter.py check --slug <slug> — lengths (a teaser outside 240-370 = HARD FAIL.
- Distinctive: line 51
Don't invent facts — write from the real source material.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
EPISODE_ADAPTER (stage S5 of content factory v2 — the contract [[decision-content-pipeline-reality-show]] §7.2)
GOAL: ONE source post → an "episode" = one draft PER (tier × platform) from §7.2, with cross-links downward and canonical→GitHub baked in. Draft-first: we write drafts and publish NOTHING.
THE §7.2 CONTRACT (implemented 1:1):
tier length platforms (phase 1) language voice/model
teaser 240-370 (HARD) RU channel · X (EN) RU TG/EN X authorial · Opus
medium 800-2500 Facebook (RU) RU authorial diary · Opus · LINK IN THE 1ST COMMENT (not in the body) + a question
longread 4000+ narrative RU channel·VC.ru·Habr(RU) · GitHub(EN) RU and EN authorial reality-show · Opus
dev-log a dry log GitHub (EN, canonical) EN technical, impersonal · Sonnet scaffold + Opus for cohesion- The owner's voice (
authorial) = Opus ONLY. The dev-log is not authorial — Sonnet assembles it, Opus stitches it together. - canonical = the GitHub markdown on every platform (a single source of truth for AI). Repo:
github.com/tonydzi/clawrush. - NO copy-paste — every file is a NATIVE rewrite for its platform.
- Cross-links downward: teaser→longread; medium→longread (in the 1st comment); longread ←teaser →dev-log; dev-log→longread + an anchor to our Deep Research.
- THE PLATFORM DECIDES THE LANGUAGE (there is no bilingual pair on every tier).
- The S3 narrative ([[style-reality-show]]) by tier: teaser=cold open+cliffhanger; medium=a full episode arc; longread=an extended episode+recap; dev-log=raw material, no drama.
- The cofounder CTA (medium+longread, the owner's rule, memory [[cofounder-cta-public-contact]]): WhatsApp +1 341 222 9178 = an authorized PUBLIC contact (a privacy carve-out), never strip it.
- VC.ru + Habr (the RU geo longread) = phase 1 since 2026-07-04 (the style files
_STYLE-vcru.md/_STYLE-habr.mdare written and live incontent-factory\; the writer loads them by the pointer in the placeholder). PHASE 2 (deferred): onlyReddit(the EN geo dev-log) — scaffolded with the--with-phase2flag.
PATHS:
- ⭐ FACTS AND CONTINUITY (v2, 2026-07-10) = THE SINGLE CANON
$OBSIDIAN_VAULT/04-Projects\show-canon\: before assembling an episode, read the anchor beat (beats\) plus its arcs/loops — "previously on the show", the cliffhanger and the season question come FROM THERE (not from memory, not from SHOW-STATE, which is frozen). Respect the beat'srevealaxis: don't burn live_hold/spoiler_until. Pick the next move with/reality-show next. After publishing — write the consequences back into the beat + runcanon_render.py. - Source material:
$IMPORTS_ROOT/content-factory/triage/posts.md(📝) — or a topic the owner names. - The scaffolder (deterministic, 0 tokens):
$IMPORTS_ROOT/content-factory/episode_adapter.py. - Bundles:
episodes\<slug>\(8 .md files in phase 1 / 9 with--with-phase2+ meta.json; every §7.2 field is baked into the placeholders). - Style: [[style-reality-show]] (
08-Templates\style-reality-show.md) +04-Projects\personal\facebook-diary-auto\_STYLE.md+ [[style-Mei-influence]] + the golden corpus up to 2023.
STEPS:
- PICK the topic: if the owner named one, use it; otherwise show the 📝 items from
posts.mdand take the strongest thread. Runlistbeforenew. - SCAFFOLD:
python episode_adapter.py new --slug <kebab> --title "<title>" --source "hub:<id>"(+--with-phase2for VC.ru/Habr/Reddit) → a bundle of empty drafts + meta.json. - WRITE (the model is named in each placeholder): teaser-ru/en, medium-fb (the body WITHOUT the link + a "1ST COMMENT" block), longread-ru/en, devlog. Replace the stubs, leave the hint comments in place. Privacy is strict (the only carve-out is the cofounder's WhatsApp).
- CHECK (the visibility layer):
python episode_adapter.py check --slug <slug>— lengths (a teaser outside 240-370 = HARD FAIL; medium/longread = WARN), CTA present, empty files. Only FAIL=0 → step 5 (a WARN on an unfinished longread is acceptable until it is written out). - REVIEW (draft-first):
set-status --slug <slug> --status review; into Telegram Saved (chat_id<YOUR_CHAT_ID>, account "work_acct_a", no parse_mode): "🎬 Episode '<title>' — the per-tier drafts are ready (check ✅). episodes<slug>. Say 'publish' and I'll lay them out." NOTHING goes outward. - EXPORT TO PUBLISHING — only on the owner's explicit "publish"/"+" (Tier-2):
python episode_adapter.py export --slug <slug>→drafts\episode-<slug>.md(formattype: content-factory-draft+ the registers## -> TG/X/FB). From there the EXISTING path:content_approve.py --serve→content_publish.py(→ Saved; the real channels are Phase 2b/Tier-2). GitHub/Reddit/VC.ru/Habr are published MANUALLY (gh / natively), not through content_publish. We do NOT breed a second publisher.
LIMITS:
- Draft-first OUTWARD: channels/X/GitHub are untouched without an explicit "publish".
- MODEL: the authorial voice = Opus ONLY; dev-log = Sonnet+Opus; scaffold/check/export = deterministic, 0 tokens.
- One post = one episode. Windows cp1252: the script forces UTF-8 stdout itself.
- Don't invent facts — write from the real source material.
- Old bundles (4-file / interim) are still read by
list/show/check/exportthrough meta (backward compatibility).
<!--kit-footer-->Like this skill? It is one of 100 in second-brain-starter-kit: the second brain we built for ourselves and run every day at Palo Alto AI Research Lab. Install the whole set with npx skills add tonydzi/second-brain-starter-kit. Everything is open source and free, so take what you need.
Flagships worth a look on their own: secondop-panel (a second opinion from a panel of external models), claude-memory-tidy (stop your agent's memory from rotting), telegram-mcp-kit (your own Telegram over MCP in about 15 minutes).
Author: Anton Dziatkovskii, Palo Alto AI Research Lab. Telegram @tonydzi - WhatsApp +1 341 222 9178 - X @Tony_Stef_
Engineers: want to test-drive this setup? Message me. I hand out free starter seeds to engineers who test and report back, and custom skill requests are welcome.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

