- name
SKILL.md
El archivo de la skill permanece en el repositorio del publicador.
Pega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add coreyhaines31/makerskills --skill ingest -a cursor -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add coreyhaines31/makerskills --skill ingest -a claude-code -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add coreyhaines31/makerskills --skill ingest -a codex -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add coreyhaines31/makerskills --skill ingest -a grok -yEnvía el mensaje copiado en un chat de Grok Bot. El Bot obtiene este SKILL.md de GitHub y lo añade a las skills que comparten todos tus Bots.
Install this skill: https://github.com/coreyhaines31/makerskills/tree/HEAD/skills/ingestDel publicador
You are a relay hub: clients text you, partners email you, calls get transcribed. Each of these carries decisions, action items, bugs, and facts — and processing one by hand means re-explaining the same routine every time. This skill is that routine, written down.
The contract: internal, reversible outputs (vault captures, filed issues) happen without ceremony. Outward-facing outputs (replies) are always drafted, never sent.
<vault> is ${SECOND_BRAIN_VAULT:-$HOME/Documents/SecondBrain}.
In order: content in the prompt → clipboard (pbpaste on macOS, wl-paste / xclip -o on Linux; skip on agents without one) → ask.
Classify by shape, not by what the user called it:
Long transcripts arrive truncated in chat sometimes — if the content visibly cuts off mid-sentence, say so and ask for the file (or a path) rather than processing a fragment.
Read people.yaml. Match participants/senders against name and aliases.
people.yaml so the question never repeats. If the user declines to add them, process the input with explicit destinations instead of routed defaults.Read the whole input first. Then pull out, with a short verbatim quote or paraphrase anchoring each:
keep CLI is authed; skip silently otherwise).Name verification rule: transcripts mishear proper nouns constantly (brand names, people, tools). Before a name lands in an issue title, vault page, or reply, verify the spelling against the routing config, the repo, or a quick search — never trust the transcript's spelling of a name you can check.
One compact table before acting:
Then proceed without waiting — everything in the table is internal or a draft. Pause for confirmation only when routing is ambiguous (two plausible repos, an unmatched person) or the input includes something sensitive (credentials, legal/financial commitments).
Issues — search for duplicates first (gh issue list --search), then file with gh issue create in the mapped repo. Title = imperative summary; body = context quote from the source, what was asked, and who asked. Apply issue_labels from config if set. Never assign anyone but the user.
Vault capture — one file per ingest, second-brain raw schema:
# message-jane-bulk-export (2026-09-04)
source: text message from Jane
project: Acme App
## Summary
…
## Decisions
…
## Action items
- [ ] mine: …
- [ ] theirs: Jane to …
## Filed
- myorg/acme-app#123 — Bulk-export button on the reports page
Slug: call- or message- + person + topic. Follow the vault's auto-commit convention (semantic commit per session).
Todos — action items of "mine" also land wherever the person's vault_page tracks tasks, if one is configured.
Reply draft — in the user's voice for that channel (config tone + channel norms: text = brief and casual; email = fuller). Structure when it fits: acknowledge → what I'm doing about it → what I need from you → when they'll hear back. End with the draft in a paste-ready block (compose with /paste rules for the channel — e.g. no URLs in an X post body). Never send it.
Close with a compact recap: TLDR of the input (2–3 sentences), decisions, both action-item lists, links to filed issues, the vault file path, and the reply draft. This recap is the deliverable — someone who never saw the input should understand what happened and what's next.
second-brain — captures land in its raw/ schema for later compilepaste — channel formatting for the reply draftdeep-research — when an extracted question needs real research before it's answerableproject-manager — when a call produces enough work to deserve a project card, not just issuesWhen you paste raw human input — a call transcript (Grain, Zoom, Granola, Fathom), a text or email from a client/partner/friend, a voice-memo dump, or meeting notes — and want it converted into struct
---name: ingestdescription: When you paste raw human input — a call transcript (Grain, Zoom, Granola, Fathom), a text or email from a…---# skills/ingest/SKILL.mdResumen general
When you paste raw human input — a call transcript (Grain, Zoom, Granola, Fathom), a text or email from a client/partner/friend, a voice-memo dump, or meeting notes — and want it converted into structured work. Extracts decisions, action items (yours vs theirs), bugs/feature requests, and facts worth keeping; files GitHub issues in the right repo, captures to the second-brain vault, and drafts (never sends) the reply. Triggers on "/ingest", "ingest this", "here's my call with X," "here's the transcript," "this is from [person]," "[person] asked me this," "from [person]:", a pasted transcript with speaker labels, or a forwarded client message that clearly expects processing. Person→project routing lives in a private config; unknown senders get asked about once, then remembered.
Preguntas frecuentes
Descarga skills/ingest/SKILL.md desde el publicador, o copia la ruta y abre el repositorio. PlugMCP lista la skill y no aloja el archivo.
El publicador lo mantiene en https://github.com/coreyhaines31/makerskills.
Claude, Cursor, Codex y Grok Build pueden leer un SKILL.md que añadas desde el repositorio del publicador. Grok Bot lo instala cuando envías en un chat el enlace a la carpeta de la skill en GitHub.