本文へ移動
cccskills
無料GitHub で公開

second-brain-transcript

Clean a raw transcript before ingestion: punctuate, paragraph, label speakers, fix mistranscribed technical terms, and split long recordings by topic. Use this skill when the user drops an auto-generated transcript, subtitle file, podcast or lecture transcript, meeting recording text, or asks to process a video or audio source. Do NOT use for text that is already prose, for summarising a transcript, or for the ingestion itself.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md2.0 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Clean a transcript

Concept pages built from unpunctuated caption dumps are noticeably worse, because the model spends its attention reconstructing sentence boundaries instead of understanding claims.

Core rule

Clean, never summarise. Nothing is cut. This is a formatting pass on the record, and the record has to stay faithful.

Workflow

  1. Punctuate and paragraph. Sentence boundaries first, then paragraphs at topic shifts.
  2. Label speakers where they change. In an interview this is most of the value.
  3. Fix technical terms. Auto-captions mangle proper nouns and jargon consistently. Flag anything you could not resolve rather than guessing.
  4. Keep coarse timestamps every few minutes, so a claim on a wiki page can be verified in ten seconds instead of a rewatch.
  5. Propose split points if the recording covers separate topics. A three-hour podcast is not one source.
  6. Write frontmatter: title, channel or speaker, URL, date.

Output format

The cleaned transcript, then:

Cleaned: <source>
Speakers labelled: <n>
Terms corrected: <list>
Uncertain: <list of what could not be resolved>
Suggested splits: <topics with timestamps, or none>

Calibration

Never drop filler that carries meaning, such as hedging or a speaker correcting themselves. Those are exactly what distinguish a claim from an aside.

If the transcript is too garbled to clean reliably, say so and recommend re-pulling it rather than producing a plausible reconstruction.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Audit an agent's context layout against the four places: system prompt, tools, history, tail. Use when the user asks to audit, review or fix their agent's context, prompt caching, token spend per turn, or CLAUDE.md / AGENTS.md layout. Read-only: reports findings and a fix list, changes nothing. Do NOT use for writing evals (evals-bootstrap) or for loop design (goal-test).

日本語の概要は準備中です。原文の説明を表示しています。

undefined-ui/second-brain-os1,0222026年10月10日 更新

Scaffold a first eval suite for an agent: mine real failures into cases, write behavioural checks over traces, and generate the runner. Use when the user wants evals, regression tests for an agent, a golden set, or asks how to know a prompt/model change did not break things. Do NOT use for a single task's done-check (goal-test) or for auditing context (context-audit).

日本語の概要は準備中です。原文の説明を表示しています。

undefined-ui/second-brain-os1,0222026年10月10日 更新

Find the decisions in a pipeline that do not need the expensive model and propose the gate for each: a rule, a classic classifier, or a small model, with fail-closed routing. Use when the user asks to cut model costs or latency, says the big model handles everything, or wants a triage / routing / filter layer in front of an agent. Analysis plus an optional baseline scaffold. Do NOT use for auditing context layout (context-audit) or for building eval suites (evals-bootstrap).

日本語の概要は準備中です。原文の説明を表示しています。

undefined-ui/second-brain-os1,0222026年10月10日 更新

goal-test

無料

Turn a vague task into a testable definition of done and generate an executable goal-test script for it, optionally with a bounded retry loop around a headless agent. Use when the user wants to run an agent in a loop, asks how to know when an agent task is finished, or says a goal like "improve X" needs to become checkable. Do NOT use for building eval suites over many cases — that is evals-bootstrap.

日本語の概要は準備中です。原文の説明を表示しています。

undefined-ui/second-brain-os1,0222026年10月10日 更新

Audit an agent's harness against the four rings: containment, guides, sensors, permissions. Use when the user asks whether their agent setup is safe, wants a review of sandboxing / permissions / hooks / AGENTS.md guardrails, or asks what a bad session could break. Read-only: reports the blast radius and a hardening list, changes nothing. Do NOT use for context layout (context-audit) or cost routing (gate-check).

日本語の概要は準備中です。原文の説明を表示しています。

undefined-ui/second-brain-os1,0222026年10月10日 更新

Import a large archive into the vault in controlled batches: triage what is worth ingesting, process oldest first, checkpoint after every batch, and keep cost visible. Use this skill whenever the user wants to import years of bookmarks, an export from another notes app, a downloads folder, a chat history dump, or says "backfill", "bulk import", "process my archive". Do NOT use for ingesting one or a few new sources, which is second-brain-ingest.

日本語の概要は準備中です。原文の説明を表示しています。

undefined-ui/second-brain-os1,0222026年10月10日 更新

undefined-ui のスキルをすべて見る

このスキルの問題を報告する