brain-export
/brain-export
How `export-to-brain` sends ready Clips transcripts to Brain — single exports, bounded historical imports, cursor pagination, required secrets, and the retry sweep. Use when exporting transcripts to Brain, backfilling past recordings, or debugging a missing or stuck Brain export.
- Author
- builderio ↗
- Repository
- agent-native ↗
- Licence
- MIT
- Last repository change
- 27.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
How `export-to-brain` sends ready Clips transcripts to Brain — single exports, bounded historical imports, cursor pagination, required secrets, and the retry sweep. Use when exporting transcripts to Brain, backfilling past recordings, or debugging a missing or stuck Brain export.
Original author description
How `export-to-brain` sends ready Clips transcripts to Brain — single exports, bounded historical imports, cursor pagination, required secrets, and the retry sweep. Use when exporting transcripts to Brain, backfilling past recordings, or debugging a missing or stuck Brain export.
How it works
- Rule
- Single export
- Bounded historical import
- Required secrets
- Durable delivery and the retry sweep
- Related skills
SKILL.md preview
--- name: brain-export description: >- How `export-to-brain` sends ready Clips transcripts to Brain — single exports, bounded historical imports, cursor pagination, required secrets, and the retry sweep. Use when exporting transcripts to Brain, backfilling past recordings, or debugging a missing or stuck Brain export. --- # Brain Export ## Rule Transcripts reach Brain through the `export-to-brain` action and the durable post-finalize worker — never through an ad hoc fetch to the Brain ingest URL. ## Single export Use `export-to-brain --recordingId=<id>` for one ready transcript. ## Bounded historical import For a bounded historical import, omit `recordingId` and pass `lookbackDays`, `limit`, and `concurrency`. When `nextCursor` is non-null, pass it as `cursor` on the next call until `nextCursor` is null. The cursor keeps the original lookback snapshot and advances by recording creation time plus id, so pages cannot reselect the same recordings or expand forever as new clips arrive. The action only selects current-user recordings with ready transcripts in the active organization, and reports exported, quarantined, skipped, and failed counts. ## Required secrets Both `BRAIN_INGEST_URL` and `BRAIN_INGEST_TOKEN` must be available as scoped Clips secrets. Never hardcode either value — read them through the app secret surface. ## Durable delivery and the retry sweep Transcript completion persists a pending export before handing it to the durable post-finalize worker. Delivery receipts include the Brain capture or sensitivity receipt id, while transient failures are swept and retried. The sweep also discovers ready transcripts from the last seven days that predate export-state tracking, in bounded batches, so recent recordings are backfilled after the connection is configured. Netlify builds emit a protected per-minute scheduled sweep because in-process intervals are not durable there. Other serverless hosts must invoke `runBrainExportSweepOnce` from their own scheduler. ## Related skills - `ai-video-tools` — how a transcript becomes ready in the first place. - `recording` — the finalize path that triggers the post-finalize worker. - `security` — scoped secret storage for the ingest URL and token.
Versions
The database has no other skills named brain-export.
Database snapshot: 13.11.2026 · package version 39700b280a2b (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 1003d-brain
Use when someone asks to build a 3D brain, visualize their AIOS or second brain, turn their knowledge into an interactive graph, or run /3d-brain or /3D brain. - 100brain-sync
Use when the user asks to update their second brain from a chat, to sync new learnings into the brain repo, to process brain Inbox, or after a meaningful conversation that should become lasting notes. Also use for /brain sync or "این چت رو به brain ببر". - 100panning-for-gold
Use when processing voice transcripts, brain dumps, stream-of-consciousness notes, or any raw multi-topic capture. Extracts every idea thread, then evaluates each one with deep brainstorming, then captures results to Open Brain. Trigger on transcripts, exports, "process this",… - 100brain
Capture a thought into the user's personal brain (an Obsidian vault) or look something up there, from any Claude Code session. Only when the user types /brain. - 90psycheon
A second brain that gets to know you and helps you actually learn, kept as a folder of plain markdown. Sets up a brain, imports exports (Instagram, WhatsApp, ChatGPT, Claude, Takeout, Obsidian), files notes, teaches topics by making the user produce, runs spaced-repetition… - 100brain
Read/write brain files (Obsidian vault at brain/). Use for any task that persists knowledge — reflection, planning, or direct edits. Triggers after debugging sessions, mistakes, corrections, architectural decisions, or any insight worth preserving across sessions. Use on 'add to…