跳到正文
cccskills
免费在 GitHub 公开

episode

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)

  • SKILL.md6.8 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

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.md are written and live in content-factory\; the writer loads them by the pointer in the placeholder). PHASE 2 (deferred): only Reddit (the EN geo dev-log) — scaffolded with the --with-phase2 flag.

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's reveal axis: don't burn live_hold/spoiler_until. Pick the next move with /reality-show next. After publishing — write the consequences back into the beat + run canon_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:

  1. PICK the topic: if the owner named one, use it; otherwise show the 📝 items from posts.md and take the strongest thread. Run list before new.
  2. SCAFFOLD: python episode_adapter.py new --slug <kebab> --title "<title>" --source "hub:<id>" (+--with-phase2 for VC.ru/Habr/Reddit) → a bundle of empty drafts + meta.json.
  3. 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).
  4. 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).
  5. 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.
  6. EXPORT TO PUBLISHING — only on the owner's explicit "publish"/"+" (Tier-2): python episode_adapter.py export --slug <slug> → drafts\episode-<slug>.md (format type: 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/export through 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.

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

03

免费

Run an autonomous consensus round between agent peers on several machines: they negotiate a decision over a shared channel and execute it without a human relaying messages. Use when multiple machines must agree on a change. Triggers: "/03", "work it out among yourselves", "find consensus". Wakes the human only for irreversible actions or a deadlock.

中文简介正在准备中。当前显示原文说明。

tonydzi/second-brain-starter-kit92026年10月20日 更新

1

免费

Recover a session after a hard crash (app died, machine rebooted, context lost mid-work): replay the turn-state ledger for the last requests, files and decisions, run a green/red health ping over the system map, file sync and MCP connectors, then rebuild the previous session history for pickup. Triggers: "/1", "resume after crash", "wake".

中文简介正在准备中。当前显示原文说明。

tonydzi/second-brain-starter-kit92026年10月20日 更新

agenda

免费

Show the operator's day: today's calendar plus what needs them personally (leads due, people awaiting a reply, deadlines), pulled from Calendar and Telegram and ranked. Read-only: sends and commits nothing. Triggers: "/agenda", "what's on today", "my agenda".

中文简介正在准备中。当前显示原文说明。

tonydzi/second-brain-starter-kit92026年10月20日 更新

ai-slop

免费

Rewrite machine-written text so it reads like a busy human wrote it: cut 50-70%, break the even rhythm, drop AI-tell words and filler, keep facts and protected terms. Use before publishing any post, reply or email drafted by a model. Triggers: /ai-slop, /slop, humanize, anti-slop, make it shorter and alive.

中文简介正在准备中。当前显示原文说明。

tonydzi/second-brain-starter-kit92026年10月20日 更新

Decision protocol for strategic work: recall the knowledge vault, run a gap analysis, emit a deep-research prompt for external tools, then synthesize the returned reports into a decision memo. Use before any new product, feature, market, pricing, GTM or architecture call, where local recall alone is not enough. Triggers: "/alfa-search-recall-deepresearch", "alpha protocol", "R+DR".

中文简介正在准备中。当前显示原文说明。

tonydzi/second-brain-starter-kit92026年10月20日 更新

- КРЕДИТ АВТОРУ ИДЕИ: совет из комментария (TG @ClawRus / @ClawInga, комменты под постами Антона в FB, треды и issue на… Триггеры: “/alpha-credit“, “/credit“, “кто нам это посоветовал“, “запиши совет“, “поблагодари советчиков“, “кому мы должны спасибо“, “кредит автору“, “чей это был совет“, “credit the author“

中文简介正在准备中。当前显示原文说明。

tonydzi/second-brain-starter-kit92026年10月20日 更新

查看 tonydzi 的全部技能

报告此技能的问题