[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70M7MR6D3FDPXMRE83RSXM3":3,"skill-same:01M70M7MR6D3FDPXMRE83RSXM3":83},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":60,"commitSha":61,"skillDirectory":62,"forksCount":63,"repositoryHtmlUrl":64,"repositoryHomepageUrl":65,"ownerHtmlUrl":66,"ownerBlogUrl":67,"ownerDescription":68,"updatedAt":69,"install":70,"resources":82},"01M70M7MR6D3FDPXMRE83RSXM3","ingest",null,"Route content to specialized ingestion skills. Detects input type and delegates.","shengdabai\u002FTony-Claude-Code-Skills","shengdabai","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F116417419?v=4","01M70F6D2WY5PQV5A92BKYJQEW","Tony Sheng","01M70F6D3GAAAYZ5H4CC1G8VXM",3,"MIT","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fgbrain-ingest\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"input","process","delegates","meetings","type","true","page","save","add","concepts","sync","brain","route","specialized","people","search","get","ingestion","sources","2026-11-10 10:12:30",false,"---\nname: ingest\ndescription: Route content to specialized ingestion skills. Detects input type and delegates.\ntriggers:\n  - \"ingest this\"\n  - \"save this to brain\"\n  - \"process this meeting\"\ntools:\n  - search\n  - get_page\n  - put_page\n  - add_link\n  - add_timeline_entry\n  - sync_brain\nmutating: true\nwrites_pages: true\nwrites_to:\n  - people\u002F\n  - companies\u002F\n  - concepts\u002F\n  - meetings\u002F\n  - sources\u002F\n---\n\n# Ingest Skill\n\nIngest meetings, articles, media, documents, and conversations into the brain.\n\n> **Filing rule:** Read `skills\u002F_brain-filing-rules.md` before creating any new page.\n\n## Contract\n\n- Every fact written to a brain page carries an inline `[Source: ...]` citation with date and provenance.\n- Every entity mention creates a back-link from the entity's page to the page mentioning them (Iron Law).\n- Raw sources are preserved for provenance via `gbrain files upload-raw` with automatic size routing.\n- State sections are rewritten with current best understanding, never appended to.\n- Entity detection fires on every inbound message; notable entities get pages or updates.\n\n> **Convention:** See `skills\u002Fconventions\u002Fquality.md` for Iron Law back-linking.\n\nEvery mention of a person or company with a brain page MUST create a back-link\nFROM that entity's page TO the page mentioning them. An unlinked mention is a\nbroken brain. See `skills\u002F_brain-filing-rules.md` for format.\n\n## Citation Requirements (MANDATORY)\n\nEvery fact written to a brain page must carry an inline `[Source: ...]` citation.\n\n- **User's statements:** `[Source: User, {context}, YYYY-MM-DD]`\n- **Meeting data:** `[Source: Meeting \"{title}\", YYYY-MM-DD]`\n- **Email\u002Fmessage:** `[Source: email from {name} re: {subject}, YYYY-MM-DD]`\n- **Web content:** `[Source: {publication}, {URL}, YYYY-MM-DD]`\n- **Social media:** `[Source: X\u002F@handle, YYYY-MM-DD](URL)` (include link)\n- **Synthesis:** `[Source: compiled from {sources}]`\n\n## Phases\n\n> **Router note:** This skill is a router. For specialized ingestion, see: idea-ingest, media-ingest, meeting-ingestion.\n\n1. **Parse the source.** Extract people, companies, dates, and events from the input.\n2. **For each entity mentioned:**\n   - Read the entity's page from gbrain to check if it exists\n   - If exists: update compiled_truth (rewrite State section with new info, don't append)\n   - If new: check notability gate, then store the page in gbrain with the appropriate type and slug\n3. **Append to timeline.** Add a timeline entry in gbrain for each event, with date, summary, and source citation.\n4. **Create cross-reference links.** Link entities in gbrain for every entity pair mentioned together, using the appropriate relationship type.\n5. **Back-link all entities.** Update EVERY mentioned entity's page with a back-link to this page (Iron Law).\n6. **Timeline merge.** The same event appears on ALL mentioned entities' timelines. If Alice met Bob at Acme Corp, the event goes on Alice's page, Bob's page, and Acme Corp's page.\n\n## Entity Detection on Every Message\n\nProduction agents should detect entity mentions on EVERY inbound message. This is\nthe signal detection loop that makes the brain compound over time.\n\n### Protocol\n\n1. **Scan the message** for entity mentions: people, companies, concepts, original\n   thinking. Fire on every message (no exceptions unless purely operational).\n2. **For each entity detected:**\n   - `gbrain search \"name\"` -- does a page already exist?\n   - **If yes:** load context with `gbrain get \u003Cslug>`. Use the compiled truth to\n     inform your response. Update the page if the message contains new information.\n   - **If no:** assess notability (see `skills\u002F_brain-filing-rules.md`). If the entity\n     is worth tracking, create a new page with `gbrain put \u003Ctype\u002Fslug>` and populate\n     with what you know.\n3. **After creating or updating pages:** sync to gbrain:\n   ```bash\n   gbrain sync --no-pull --no-embed\n   ```\n4. **Don't block the conversation.** Entity detection and enrichment should happen\n   alongside the response, not before it. The user shouldn't wait for brain writes\n   to get an answer.\n\n### What counts as notable\n\n- People the user interacts with or discusses (not random mentions)\n- Companies relevant to the user's work or interests\n- Concepts or frameworks the user references or creates\n- The user's own original thinking (ideas, theses, observations) -- highest value\n- See `skills\u002F_brain-filing-rules.md` for the full notability gate\n\n### What to capture from the user's own thinking\n\nOriginal thinking is the most valuable signal. Capture exact phrasing -- the user's\nlanguage IS the insight. Don't paraphrase.\n\n- Novel observations or theses\n- Frameworks, mental models, heuristics\n- Connections between ideas that others miss\n- Contrarian positions with reasoning\n- Strong reactions to external stimuli (what triggered it and why)\n\n## Media Workflows\n\nContent the user encounters should be captured in the brain. File by PRIMARY\nSUBJECT, not by format (see `skills\u002F_brain-filing-rules.md`).\n\n### Articles & Web Content\n\n**Input:** URL shared by user, or article mentioned in conversation.\n\n**Process:**\n1. Fetch content (`web_fetch` or equivalent)\n2. Extract: title, author, publication, date, full text\n3. Summarize: executive summary + key arguments (not a rehash)\n4. Extract entities: people, companies, concepts mentioned\n5. **Save raw source** for provenance (see Raw Source Preservation below)\n6. Analyze for the user: don't just summarize. What's interesting given what you\n   know about them? Flag connections, contradictions, content opportunities.\n\n**Write to:** appropriate directory per filing rules (about a person -> `people\u002F`,\nabout a company -> `companies\u002F`, reusable framework -> `concepts\u002F`, raw data -> `sources\u002F`)\n\n### Videos & Podcasts\n\n**Input:** URL (YouTube, podcast, etc.) or local audio\u002Fvideo file.\n\n**Process:**\n1. Get transcript -- speaker-diarized if possible (services like Diarize.io provide\n   speaker-labeled, word-level timing)\n2. **Save raw transcript** (both JSON and human-readable TXT)\n3. Analyze: executive summary, key ideas, key quotes with speaker attribution,\n   notable stories\u002Fanecdotes, people and companies mentioned\n4. Extract and cross-reference all entities mentioned\n5. **HARD RULE:** every video\u002Fpodcast brain page MUST link to the raw diarized\n   transcript. A page without transcript links is incomplete.\n\n**Write to:** `media\u002Fvideos\u002F` or `media\u002Fpodcasts\u002F` with back-links to all entities.\n\n**Quality bar:**\n- Compelling headline (not \"This video discusses...\")\n- Executive summary that makes you want to watch\u002Flisten\n- Key Ideas as actual insights, not topic labels\n- Verbatim quotes with real speaker names (not \"speaker_0\")\n- All entities extracted with context and back-linked\n\n### PDFs & Documents\n\n**Input:** File path or URL.\n\n**Process:**\n1. Extract text (OCR if scanned\u002Fimage PDF)\n2. **Save raw source** for provenance\n3. Summarize: executive summary + key sections + notable data\n4. Extract entities\n5. Cross-reference from entity pages\n\n**Write to:** per filing rules (file by primary subject, not format).\n\n### Screenshots & Images\n\n**Input:** Image file.\n\n**Process:**\n1. Analyze content (OCR for text-heavy images, description for photos)\n2. If tweet screenshot: extract text, author, date, route to social media workflow\n3. If article screenshot: extract text, route to article workflow\n4. If data\u002Fchart: extract data points, describe findings\n\n**Write to:** depends on content -- route to the appropriate workflow above.\n\n### Meeting Transcripts\n\n**Input:** Transcript from meeting recording service, or manual notes.\n\n**Process:**\n1. Pull full transcript (source of truth -- AI summaries are medium-low trust)\n2. **Save raw transcript** for provenance\n3. Write meeting page with YOUR analysis above the line, raw transcript below\n4. **Entity propagation (MANDATORY):** for each attendee and company discussed:\n   - Update their brain page State section if new info surfaced\n   - Append to their Timeline with link to the meeting page\n   - Create page if person\u002Fcompany is notable and has no page yet\n5. A meeting is NOT fully ingested until all entity pages are updated\n\n**Write to:** `meetings\u002FYYYY-MM-DD-short-description.md`\n\n**What makes a good meeting page:**\n- Reveals the real crux, not a bullet dump\n- Connects to existing brain pages (people, companies, deals)\n- Flags what changed (status, decisions, new info)\n- Names tension or what was left unsaid\n- Captures actual dynamic, not performative summary\n\n### Social Media Content\n\n**Input:** Tweet, thread, or social media post.\n\n**Process:**\n1. Fetch full content (thread, quote tweets, context)\n2. If images present: OCR via vision model for full text extraction\n3. Summarize: what's being said, why it matters, who's involved\n4. Extract entities and update brain pages\n5. Include direct link to the original post (MANDATORY for citations)\n\n**Write to:** `media\u002Fx\u002F` for daily aggregation, or entity-specific directories\nif the post is primarily about a person\u002Fcompany.\n\n## Raw Source Preservation\n\nEvery ingested item must have its raw source preserved for provenance.\n\n**Use `gbrain files upload-raw` for automatic size routing:**\n```bash\ngbrain files upload-raw \u003Cfile> --page \u003Cpage-slug> --type \u003Ctype>\n```\n\n- **\u003C 100 MB text\u002FPDF**: stays in git (brain repo `.raw\u002F` sidecar directories)\n- **>= 100 MB OR media** (video, audio, images): uploaded to cloud storage\n  via TUS resumable upload, `.redirect.yaml` pointer left in the brain repo\n\nThe `.redirect.yaml` pointer format:\n```yaml\ntarget: supabase:\u002F\u002Fbrain-files\u002Fpage-slug\u002Ffilename.mp4\nbucket: brain-files\nstorage_path: page-slug\u002Ffilename.mp4\nsize: 524288000\nsize_human: 500 MB\nhash: sha256:abc123...\nmime: video\u002Fmp4\nuploaded: 2026-04-11T...\ntype: transcript\n```\n\n**Accessing stored files:**\n- `gbrain files signed-url \u003Cstorage-path>` -- generate 1-hour signed URL for viewing\u002Fsharing\n- `gbrain files restore \u003Cdir>` -- download back to local from cloud storage\n\nUse `put_raw_data` in gbrain to store raw API responses and metadata (JSON, not binary).\n\n## Test Before Bulk\n\nWhen processing multiple items (batch video ingestion, bulk meeting processing, etc.):\n\n1. **Test on 3-5 items first.** Run in test mode if available.\n2. **Read the actual output.** Is the quality good? Are titles compelling (not\n   \"This video discusses...\")? Are entities extracted and back-linked? Is the\n   format clean?\n3. **Fix what's wrong** in the approach\u002Fskill, not via one-off patches.\n4. **Only then: bulk execute** with throttling, commits every 5-10 items.\n\nThe marginal cost of testing 3 items first is near zero. The cost of cleaning\nup 100 bad pages is enormous.\n\n## Quality Rules\n\n- Executive summary in compiled_truth must be updated, not just timeline appended\n- State section is REWRITTEN, not appended to. Current best understanding only.\n- Timeline entries are reverse-chronological (newest first)\n- Every person\u002Fcompany mentioned gets a page if notable (see filing rules)\n- Link types: knows, works_at, invested_in, founded, met_at, discussed\n- Source attribution: every timeline entry includes [Source: ...] citation\n- Back-links: every entity mention creates a back-link (Iron Law)\n- Filing: file by primary subject, not format or source (see filing rules)\n\n## Anti-Patterns\n\n- **Appending to State sections.** State is rewritten with the current best understanding on every update. Append-only State sections grow stale and contradictory.\n- **Ingesting without back-links.** An unlinked mention is a broken brain. Every entity mentioned must have a back-link from their page to the page mentioning them.\n- **Skipping raw source preservation.** Every ingested item must have its raw source preserved. A brain page without provenance is unverifiable.\n- **Bulk processing without sample test.** Test on 3-5 items first. Fix quality issues in the approach, not via one-off patches.\n- **Paraphrasing the user's original thinking.** The user's exact language IS the insight. Capture verbatim phrasing for ideas, theses, and frameworks.\n\n## Output Format\n\n```\nINGESTED: [title]\n==================\n\nPage: [slug]\nType: [person \u002F company \u002F meeting \u002F media \u002F concept]\nSource: [source description]\n\nEntities detected: N\n- [entity] -> [created \u002F updated] ([slug])\n\nBack-links created: N\nTimeline entries: N\nRaw source: [preserved at path \u002F uploaded to cloud]\n```\n\n## Tools Used\n\n- Read a page from gbrain (get_page)\n- Store\u002Fupdate a page in gbrain (put_page)\n- Add a timeline entry in gbrain (add_timeline_entry)\n- Link entities in gbrain (add_link)\n- List tags for a page (get_tags)\n- Tag a page in gbrain (add_tag)\n- Store raw data in gbrain (put_raw_data)\n- Check backlinks in gbrain (get_backlinks)\n","# Ingest Skill\n\nIngest meetings, articles, media, documents, and conversations into the brain.\n\n> **Filing rule:** Read `skills\u002F_brain-filing-rules.md` before creating any new page.\n\n## Contract\n\n- Every fact written to a brain page carries an inline `[Source: ...]` citation with date and provenance.\n- Every entity mention creates a back-link from the entity's page to the page mentioning them (Iron Law).\n- Raw sources are preserved for provenance via `gbrain files upload-raw` with automatic size routing.\n- State sections are rewritten with current best understanding, never appended to.\n- Entity detection fires on every inbound message; notable entities get pages or updates.\n\n> **Convention:** See `skills\u002Fconventions\u002Fquality.md` for Iron Law back-linking.\n\nEvery mention of a person or company with a brain page MUST create a back-link\nFROM that entity's page TO the page mentioning them. An unlinked mention is a\nbroken brain. See `skills\u002F_brain-filing-rules.md` for format.\n\n## Citation Requirements (MANDATORY)\n\nEvery fact written to a brain page must carry an inline `[Source: ...]` citation.\n\n- **User's statements:** `[Source: User, {context}, YYYY-MM-DD]`\n- **Meeting data:** `[Source: Meeting \"{title}\", YYYY-MM-DD]`\n- **Email\u002Fmessage:** `[Source: email from {name} re: {subject}, YYYY-MM-DD]`\n- **Web content:** `[Source: {publication}, {URL}, YYYY-MM-DD]`\n- **Social media:** `[Source: X\u002F@handle, YYYY-MM-DD](URL)` (include link)\n- **Synthesis:** `[Source: compiled from {sources}]`\n\n## Phases\n\n> **Router note:** This skill is a router. For specialized ingestion, see: idea-ingest, media-ingest, meeting-ingestion.\n\n1. **Parse the source.** Extract people, companies, dates, and events from the input.\n2. **For each entity mentioned:**\n   - Read the entity's page from gbrain to check if it exists\n   - If exists: update compiled_truth (rewrite State section with new info, don't append)\n   - If new: check notability gate, then store the page in gbrain with the appropriate type and slug\n3. **Append to timeline.** Add a timeline entry in gbrain for each event, with date, summary, and source citation.\n4. **Create cross-reference links.** Link entities in gbrain for every entity pair mentioned together, using the appropriate relationship type.\n5. **Back-link all entities.** Update EVERY mentioned entity's page with a back-link to this page (Iron Law).\n6. **Timeline merge.** The same event appears on ALL mentioned entities' timelines. If Alice met Bob at Acme Corp, the event goes on Alice's page, Bob's page, and Acme Corp's page.\n\n## Entity Detection on Every Message\n\nProduction agents should detect entity mentions on EVERY inbound message. This is\nthe signal detection loop that makes the brain compound over time.\n\n### Protocol\n\n1. **Scan the message** for entity mentions: people, companies, concepts, original\n   thinking. Fire on every message (no exceptions unless purely operational).\n2. **For each entity detected:**\n   - `gbrain search \"name\"` -- does a page already exist?\n   - **If yes:** load context with `gbrain get \u003Cslug>`. Use the compiled truth to\n     inform your response. Update the page if the message contains new information.\n   - **If no:** assess notability (see `skills\u002F_brain-filing-rules.md`). If the entity\n     is worth tracking, create a new page with `gbrain put \u003Ctype\u002Fslug>` and populate\n     with what you know.\n3. **After creating or updating pages:** sync to gbrain:\n   ```bash\n   gbrain sync --no-pull --no-embed\n   ```\n4. **Don't block the conversation.** Entity detection and enrichment should happen\n   alongside the response, not before it. The user shouldn't wait for brain writes\n   to get an answer.\n\n### What counts as notable\n\n- People the user interacts with or discusses (not random mentions)\n- Companies relevant to the user's work or interests\n- Concepts or frameworks the user references or creates\n- The user's own original thinking (ideas, theses, observations) -- highest value\n- See `skills\u002F_brain-filing-rules.md` for the full notability gate\n\n### What to capture from the user's own thinking\n\nOriginal thinking is the most valuable signal. Capture exact phrasing -- the user's\nlanguage IS the insight. Don't paraphrase.\n\n- Novel observations or theses\n- Frameworks, mental models, heuristics\n- Connections between ideas that others miss\n- Contrarian positions with reasoning\n- Strong reactions to external stimuli (what triggered it and why)\n\n## Media Workflows\n\nContent the user encounters should be captured in the brain. File by PRIMARY\nSUBJECT, not by format (see `skills\u002F_brain-filing-rules.md`).\n\n### Articles & Web Content\n\n**Input:** URL shared by user, or article mentioned in conversation.\n\n**Process:**\n1. Fetch content (`web_fetch` or equivalent)\n2. Extract: title, author, publication, date, full text\n3. Summarize: executive summary + key arguments (not a rehash)\n4. Extract entities: people, companies, concepts mentioned\n5. **Save raw source** for provenance (see Raw Source Preservation below)\n6. Analyze for the user: don't just summarize. What's interesting given what you\n   know about them? Flag connections, contradictions, content opportunities.\n\n**Write to:** appropriate directory per filing rules (about a person -> `people\u002F`,\nabout a company -> `companies\u002F`, reusable framework -> `concepts\u002F`, raw data -> `sources\u002F`)\n\n### Videos & Podcasts\n\n**Input:** URL (YouTube, podcast, etc.) or local audio\u002Fvideo file.\n\n**Process:**\n1. Get transcript -- speaker-diarized if possible (services like Diarize.io provide\n   speaker-labeled, word-level timing)\n2. **Save raw transcript** (both JSON and human-readable TXT)\n3. Analyze: executive summary, key ideas, key quotes with speaker attribution,\n   notable stories\u002Fanecdotes, people and companies mentioned\n4. Extract and cross-reference all entities mentioned\n5. **HARD RULE:** every video\u002Fpodcast brain page MUST link to the raw diarized\n   transcript. A page without transcript links is incomplete.\n\n**Write to:** `media\u002Fvideos\u002F` or `media\u002Fpodcasts\u002F` with back-links to all entities.\n\n**Quality bar:**\n- Compelling headline (not \"This video discusses...\")\n- Executive summary that makes you want to watch\u002Flisten\n- Key Ideas as actual insights, not topic labels\n- Verbatim quotes with real speaker names (not \"speaker_0\")\n- All entities extracted with context and back-linked\n\n### PDFs & Documents\n\n**Input:** File path or URL.\n\n**Process:**\n1. Extract text (OCR if scanned\u002Fimage PDF)\n2. **Save raw source** for provenance\n3. Summarize: executive summary + key sections + notable data\n4. Extract entities\n5. Cross-reference from entity pages\n\n**Write to:** per filing rules (file by primary subject, not format).\n\n### Screenshots & Images\n\n**Input:** Image file.\n\n**Process:**\n1. Analyze content (OCR for text-heavy images, description for photos)\n2. If tweet screenshot: extract text, author, date, route to social media workflow\n3. If article screenshot: extract text, route to article workflow\n4. If data\u002Fchart: extract data points, describe findings\n\n**Write to:** depends on content -- route to the appropriate workflow above.\n\n### Meeting Transcripts\n\n**Input:** Transcript from meeting recording service, or manual notes.\n\n**Process:**\n1. Pull full transcript (source of truth -- AI summaries are medium-low trust)\n2. **Save raw transcript** for provenance\n3. Write meeting page with YOUR analysis above the line, raw transcript below\n4. **Entity propagation (MANDATORY):** for each attendee and company discussed:\n   - Update their brain page State section if new info surfaced\n   - Append to their Timeline with link to the meeting page\n   - Create page if person\u002Fcompany is notable and has no page yet\n5. A meeting is NOT fully ingested until all entity pages are updated\n\n**Write to:** `meetings\u002FYYYY-MM-DD-short-description.md`\n\n**What makes a good meeting page:**\n- Reveals the real crux, not a bullet dump\n- Connects to existing brain pages (people, companies, deals)\n- Flags what changed (status, decisions, new info)\n- Names tension or what was left unsaid\n- Captures actual dynamic, not performative summary\n\n### Social Media Content\n\n**Input:** Tweet, thread, or social media post.\n\n**Process:**\n1. Fetch full content (thread, quote tweets, context)\n2. If images present: OCR via vision model for full text extraction\n3. Summarize: what's being said, why it matters, who's involved\n4. Extract entities and update brain pages\n5. Include direct link to the original post (MANDATORY for citations)\n\n**Write to:** `media\u002Fx\u002F` for daily aggregation, or entity-specific directories\nif the post is primarily about a person\u002Fcompany.\n\n## Raw Source Preservation\n\nEvery ingested item must have its raw source preserved for provenance.\n\n**Use `gbrain files upload-raw` for automatic size routing:**\n```bash\ngbrain files upload-raw \u003Cfile> --page \u003Cpage-slug> --type \u003Ctype>\n```\n\n- **\u003C 100 MB text\u002FPDF**: stays in git (brain repo `.raw\u002F` sidecar directories)\n- **>= 100 MB OR media** (video, audio, images): uploaded to cloud storage\n  via TUS resumable upload, `.redirect.yaml` pointer left in the brain repo\n\nThe `.redirect.yaml` pointer format:\n```yaml\ntarget: supabase:\u002F\u002Fbrain-files\u002Fpage-slug\u002Ffilename.mp4\nbucket: brain-files\nstorage_path: page-slug\u002Ffilename.mp4\nsize: 524288000\nsize_human: 500 MB\nhash: sha256:abc123...\nmime: video\u002Fmp4\nuploaded: 2026-04-11T...\ntype: transcript\n```\n\n**Accessing stored files:**\n- `gbrain files signed-url \u003Cstorage-path>` -- generate 1-hour signed URL for viewing\u002Fsharing\n- `gbrain files restore \u003Cdir>` -- download back to local from cloud storage\n\nUse `put_raw_data` in gbrain to store raw API responses and metadata (JSON, not binary).\n\n## Test Before Bulk\n\nWhen processing multiple items (batch video ingestion, bulk meeting processing, etc.):\n\n1. **Test on 3-5 items first.** Run in test mode if available.\n2. **Read the actual output.** Is the quality good? Are titles compelling (not\n   \"This video discusses...\")? Are entities extracted and back-linked? Is the\n   format clean?\n3. **Fix what's wrong** in the approach\u002Fskill, not via one-off patches.\n4. **Only then: bulk execute** with throttling, commits every 5-10 items.\n\nThe marginal cost of testing 3 items first is near zero. The cost of cleaning\nup 100 bad pages is enormous.\n\n## Quality Rules\n\n- Executive summary in compiled_truth must be updated, not just timeline appended\n- State section is REWRITTEN, not appended to. Current best understanding only.\n- Timeline entries are reverse-chronological (newest first)\n- Every person\u002Fcompany mentioned gets a page if notable (see filing rules)\n- Link types: knows, works_at, invested_in, founded, met_at, discussed\n- Source attribution: every timeline entry includes [Source: ...] citation\n- Back-links: every entity mention creates a back-link (Iron Law)\n- Filing: file by primary subject, not format or source (see filing rules)\n\n## Anti-Patterns\n\n- **Appending to State sections.** State is rewritten with the current best understanding on every update. Append-only State sections grow stale and contradictory.\n- **Ingesting without back-links.** An unlinked mention is a broken brain. Every entity mentioned must have a back-link from their page to the page mentioning them.\n- **Skipping raw source preservation.** Every ingested item must have its raw source preserved. A brain page without provenance is unverifiable.\n- **Bulk processing without sample test.** Test on 3-5 items first. Fix quality issues in the approach, not via one-off patches.\n- **Paraphrasing the user's original thinking.** The user's exact language IS the insight. Capture verbatim phrasing for ideas, theses, and frameworks.\n\n## Output Format\n\n```\nINGESTED: [title]\n==================\n\nPage: [slug]\nType: [person \u002F company \u002F meeting \u002F media \u002F concept]\nSource: [source description]\n\nEntities detected: N\n- [entity] -> [created \u002F updated] ([slug])\n\nBack-links created: N\nTimeline entries: N\nRaw source: [preserved at path \u002F uploaded to cloud]\n```\n\n## Tools Used\n\n- Read a page from gbrain (get_page)\n- Store\u002Fupdate a page in gbrain (put_page)\n- Add a timeline entry in gbrain (add_timeline_entry)\n- Link entities in gbrain (add_link)\n- List tags for a page (get_tags)\n- Tag a page in gbrain (add_tag)\n- Store raw data in gbrain (put_raw_data)\n- Check backlinks in gbrain (get_backlinks)\n",{"name":5,"tools":43,"mutating":49,"triggers":50,"writes_to":54,"description":7,"writes_pages":49},[34,44,45,46,47,48],"get_page","put_page","add_link","add_timeline_entry","sync_brain",true,[51,52,53],"ingest this","save this to brain","process this meeting",[55,56,57,58,59],"people\u002F","companies\u002F","concepts\u002F","meetings\u002F","sources\u002F","main","7850740bd837adb32f0a109ab2af82482196c6f2","skills\u002Fgbrain-ingest",1,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills","https:\u002F\u002Fzturnsgo.com","https:\u002F\u002Fgithub.com\u002Fshengdabai","https:\u002F\u002Fzturnsgo.com\u002F","AI × education creator — producer, not consumer. Taught 6,000+ learners; shipping learning tools & daily essays with Claude Code, practicing @xiaolai's way 🥋","2026-11-01 21:28:23",{"source":8,"skillName":5,"commands":71,"prompt":81,"zipAvailable":49},[72,75,78],{"tool":73,"command":74},"npx","npx skills add shengdabai\u002FTony-Claude-Code-Skills --skill ingest",{"tool":76,"command":77},"bunx","bunx skills add shengdabai\u002FTony-Claude-Code-Skills --skill ingest",{"tool":79,"command":80},"pnpm","pnpm dlx skills add shengdabai\u002FTony-Claude-Code-Skills --skill ingest","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fgbrain-ingest\u002FSKILL.md",[],[84,93,101,109,117,125],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":88,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":92},"01M73H7XKBHE1ETQDZT94MF9HH","seedance-prompt-en","Write effective prompts for Jimeng Seedance 2.0 multimodal AI video generation. Use when users want to create video prompts using text, images, videos, and audio inputs with the @ reference system. Covers camera movements, effects replication, video extension, editing, music beat-matching, e-commerce ads, short dramas, and educational content.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fseedance-prompt-en\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fseedance-prompt-en\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":97,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":92},"01M73GRE9998Q1DZWC71N41JWG","onepage-pdf","Convert an HTML page into a single continuous-page PDF (one tall page, no pagination breaks), preserving desktop layout, backgrounds and selectable text. Use when the user asks to turn an HTML file\u002Freport\u002Fproposal into a \"single-page PDF\", \"long PDF\", \"不分页 PDF\", \"单页 PDF\", \"长图式 PDF\", or complains that an HTML-to-PDF export breaks into pages or cuts content. Supports optional string redaction with leak verification.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fonepage-pdf\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fonepage-pdf\u002FSKILL.md",[],[],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":105,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":92},"01M73GQG1KZDADVPV3MHAT1J5A","native-feel-cross-platform-desktop","Use when the user is designing, prototyping, or rewriting a desktop app that must run on multiple OSes (macOS + Windows, optionally Linux) AND feel indistinguishable from a native app to its users — fast launch, native windowing, native input handling, native materials. Trigger words include \"cross-platform desktop\", \"Electron alternative\", \"Tauri vs native\", \"WebView wrapper\", \"near-native performance\", \"Raycast architecture\", \"WebKit\u002FWebView2 quirks\", \"WKWebView\", \"system tray app\", \"global hotkey app\", \"launcher app\". Do NOT trigger this skill for pure web apps, pure mobile apps, or for greenfield projects that have no native-feel requirement.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fnative-feel-cross-platform-desktop\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fnative-feel-cross-platform-desktop\u002FSKILL.md",[],[],{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":113,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":92},"01M73G87PDNSMKG2FHWCYER6N8","gstack","Router for the gstack skill suite. (gstack)","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fgstack\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fgstack\u002FSKILL.md",[],[],{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":121,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":92},"01M73G3EAQWKCM8DB8D0N0QSVG","fireworks-tech-graph","Use when the user wants to create any technical diagram - architecture, data flow, flowchart, sequence, agent\u002Fmemory, or concept map - and export as SVG+PNG. Trigger on: \"画图\" \"帮我画\" \"生成图\" \"做个图\" \"架构图\" \"流程图\" \"可视化一下\" \"出图\" \"generate diagram\" \"draw diagram\" \"visualize\" or any system\u002Fflow description the user wants illustrated.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ffireworks-tech-graph\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ffireworks-tech-graph\u002FSKILL.md",[],[],{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":131,"publishedAt":92},"01M73G086AXAH9DW1H5G5N3CPB","dbs-video-extract","接收抖音、小红书、微信视频号等短视频链接或分享文案，查询作品／账号数据并提取语音文字稿，按作者和标题归档为 Markdown。用户希望完整解析短视频、取得数据或文字稿时使用；运行前检查 TikHub 与轻抖使用凭证，缺少时用新手能理解的方式引导购买和安全配置。","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fdbs-video-extract\u002FSKILL.md",[],[]]