[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70M7DVS8G1PVHAZBY97M6GR":3,"skill-same:01M70M7DVS8G1PVHAZBY97M6GR":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},"01M70M7DVS8G1PVHAZBY97M6GR","enrich",null,"Enrich brain pages with tiered enrichment protocol. Creates and updates\nperson\u002Fcompany pages with compiled truth, timeline, and cross-links.\nUse when a new entity is mentioned or an existing page needs updating.","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-enrich\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"who is this","pages","true","page","backlinks","links","add","brain","update","create","query","updates","when","people","new","up","company","search","get","2026-11-10 10:12:30",false,"---\nname: enrich\nversion: 1.0.0\ndescription: |\n  Enrich brain pages with tiered enrichment protocol. Creates and updates\n  person\u002Fcompany pages with compiled truth, timeline, and cross-links.\n  Use when a new entity is mentioned or an existing page needs updating.\ntriggers:\n  - \"enrich\"\n  - \"create person page\"\n  - \"update company page\"\n  - \"who is this person\"\n  - \"look up this company\"\ntools:\n  - get_page\n  - put_page\n  - search\n  - query\n  - add_link\n  - add_timeline_entry\n  - get_backlinks\nmutating: true\nwrites_pages: true\nwrites_to:\n  - people\u002F\n  - companies\u002F\n---\n\n# Enrich Skill\n\nEnrich person and company pages from external sources. Scale effort to importance.\n\n## Contract\n\nThis skill guarantees:\n- Every enriched page has compiled truth (State section) with inline citations\n- Every enriched page has a timeline with dated entries\n- Back-links are created bidirectionally\n- Tiered enrichment: Tier 1 (full), Tier 2 (medium), Tier 3 (minimal) based on notability\n- No stubs: every new page has meaningful content from web search or existing brain context\n\n> **Filing rule:** Read `skills\u002F_brain-filing-rules.md` before creating any new page.\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## Philosophy\n\nA brain page should read like an intelligence dossier, not a LinkedIn scrape.\nFacts are table stakes. Texture is the value -- what do they believe, what are\nthey building, what makes them tick, where are they headed.\n\n## Citation Requirements (MANDATORY)\n\n> **Convention:** see `skills\u002Fconventions\u002Fquality.md` for citation formats and source precedence.\n\nWhen sources conflict, note the contradiction with both citations.\n\n## When To Enrich\n\n### Primary triggers\n- User mentions an entity in conversation\n- Entity appears in a meeting transcript or email\n- New contact appears with significant context\n- Entity makes news or has a major event\n- Any ingest pipeline encounters a notable entity\n\n### Do NOT enrich\n- Random mentions with no relationship signal\n- Bot\u002Fspam accounts\n- Entities with no substantive connection to the user's work\n- Same page enriched within the past week (unless new signal warrants it)\n\n## Enrichment Tiers\n\nScale enrichment to importance. Don't waste API calls on low-value entities.\n\n| Tier | Who | Effort | Sources |\n|------|-----|--------|---------|\n| 1 (key) | Inner circle, close collaborators, key contacts | Full pipeline | All available APIs + deep web research |\n| 2 (notable) | Occasional interactions, industry figures | Moderate | Web research + social + brain cross-ref |\n| 3 (minor) | Worth tracking, not critical | Light | Brain cross-ref + social lookup if handle known |\n\n## The Enrichment Protocol (7 Steps)\n\n### Step 1: Identify entities\n\nExtract people, companies, concepts from the incoming signal.\n\n### Step 2: Check brain state\n\nFor each entity:\n- `gbrain search \"name\"` -- does a page already exist?\n- **If yes:** UPDATE path (add new signal, update compiled truth if material)\n- **If no:** CREATE path (check notability gate first, then create)\n\n### Step 3: Extract signal from source\n\nDon't just capture facts. Capture texture:\n\n| Signal Type | What to Extract |\n|-------------|----------------|\n| Opinions, beliefs | What They Believe section |\n| Current projects, features shipped | What They're Building section |\n| Ambition, career arc, motivation | What Motivates Them section |\n| Topics they return to obsessively | Hobby Horses section |\n| Who they amplify, argue with, respect | Network \u002F Relationships |\n| Ascending, plateauing, pivoting? | Trajectory section |\n| Role, company, funding, location | State section (hard facts) |\n\n### Step 4: External data source lookups\n\nPriority order -- stop when you have enough signal for the entity's tier.\n\n**4a. Brain cross-reference (always, all tiers)**\n- `gbrain search \"name\"` and `gbrain query \"what do we know about name\"`\n- Check related pages: company pages for person enrichment and vice versa\n- This is free and often the richest source\n\n**4b. Web research (Tier 1 and 2)**\n- Use Perplexity, Brave Search, Exa, or equivalent web research tool\n- **Key pattern:** Send existing brain knowledge as context so the search\n  returns DELTA (what's new vs what you already know), not a rehash\n- Opus-class models for Tier 1 deep research, lighter models for Tier 2\n\n**4c. Social media lookup (all tiers when handle known)**\n- Pull recent posts\u002Ftweets for tone, interests, current focus\n- Social media is the highest-texture signal for what someone actually thinks\n\n**4d. People enrichment APIs (Tier 1)**\n- LinkedIn data, career history, connections, education\n\n**4e. Company enrichment APIs (Tier 1)**\n- Company data, financials, headcount, key hires, recent news\n\n| Data Need | Example Sources | Tier |\n|-----------|----------------|------|\n| Web research | Perplexity, Brave, Exa | 1-2 |\n| LinkedIn \u002F career | Crustdata, Proxycurl, People Data Labs | 1 |\n| Career history | Happenstance, LinkedIn | 1 |\n| Funding \u002F company data | Crunchbase, PitchBook, Clearbit | 1 |\n| Social media | Platform APIs, web scraping | 1-3 |\n| Meeting history | Calendar\u002Fmeeting transcript tools | 1-2 |\n\n### Step 5: Save raw data (preserves provenance)\n\nStore raw API responses via `put_raw_data` in gbrain:\n```json\n{\n  \"source\": \"crustdata\",\n  \"fetched_at\": \"2026-04-11T...\",\n  \"query\": \"jane doe\",\n  \"data\": { ... }\n}\n```\n\nRaw data preserves provenance. If the compiled truth is ever questioned,\nthe raw data shows exactly what the API returned.\n\n### Step 6: Write to brain\n\n#### CREATE path\n\n1. Check notability gate (see `skills\u002F_brain-filing-rules.md`)\n2. Check filing rules -- where does this entity go?\n3. Create page with the appropriate template (below)\n4. Fill compiled truth with citations\n5. Add first timeline entry\n6. Leave empty sections as `[No data yet]` (don't fill with boilerplate)\n\n#### UPDATE path\n\n1. Add new timeline entries (reverse-chronological, append-only)\n2. Update compiled truth ONLY if the new signal materially changes the picture\n3. Update State section with new facts\n4. Flag contradictions between new signal and existing compiled truth\n5. Don't overwrite user-written assessments with API boilerplate\n\n#### Person page template\n\n```markdown\n---\ntitle: Full Name\ntype: person\ncreated: YYYY-MM-DD\nupdated: YYYY-MM-DD\ntags: []\ncompany: Current Company\nrelationship: How the user knows them\nemail:\nlinkedin:\ntwitter:\nlocation:\n---\n\n# Full Name\n\n> 1-paragraph executive summary: HOW do you know them, WHY do they matter,\n> what's the current state of the relationship.\n\n## State\nRole, company, key context. Hard facts only.\n\n## What They Believe\nIdeology, first principles, worldview. What hills do they die on?\n\n## What They're Building\nCurrent projects, recent launches, what they're focused on.\n\n## What Motivates Them\nAmbition, career arc, what drives them.\n\n## Hobby Horses\nTopics they return to obsessively. Recurring themes in their work\u002Fposts.\n\n## Assessment\nYour read on this person. Strengths, gaps, trajectory.\n\n## Trajectory\nAscending, plateauing, pivoting, declining? Where are they headed?\n\n## Relationship\nHistory of interactions, shared context, relationship quality.\n\n## Contact\nEmail, social handles, preferred communication channel.\n\n## Network\nKey connections, mutual contacts, organizational relationships.\n\n## Open Threads\nActive conversations, pending items, things to follow up on.\n\n---\n\n## Timeline\nReverse chronological. Every entry has a date and [Source: ...] citation.\n- **YYYY-MM-DD** | Event description [Source: ...]\n```\n\n#### Company page template\n\n```markdown\n---\ntitle: Company Name\ntype: company\ncreated: YYYY-MM-DD\nupdated: YYYY-MM-DD\ntags: []\n---\n\n# Company Name\n\n> 1-paragraph executive summary.\n\n## State\nWhat they do, stage, key people, key metrics, your connection.\n\n## Open Threads\nActive items, pending decisions, things to track.\n\n---\n\n## Timeline\n- **YYYY-MM-DD** | Event description [Source: ...]\n```\n\n### Step 7: Cross-reference\n\n- Update company pages from person enrichment (and vice versa)\n- Update related project\u002Fdeal pages if relevant context surfaced\n- Check index files if the brain uses them\n\n**Note (v0.10.1):** Links between brain pages are auto-created on every\n`put_page` call (auto-link post-hook). Step 7 focuses on content\ncross-references (updating related pages' compiled truth with new signal\nfrom this enrichment), not on creating links. Verify via the `auto_links`\nfield in the put_page response (`{ created, removed, errors }`).\nTimeline entries still need explicit `gbrain timeline-add` calls.\n\n## Bulk Enrichment Rules\n\n- **Test on 3-5 entities first.** Read actual output. Check quality.\n- Only proceed to bulk after test shots pass your quality bar.\n- 3+ entities from one source -> batch process or spawn sub-agent\n- Throttle API calls. Respect rate limits.\n- Commit every 5-10 entities during bulk runs.\n- Save a report after bulk enrichment (see Report Storage below).\n\n## Validation Rules\n\n- Connection count \u003C 20 on LinkedIn = likely wrong person, skip\n- Name mismatch between brain and API = skip, flag for review\n- Joke profiles or obviously wrong data = save to raw, don't update page\n- Don't overwrite user-written assessments with API boilerplate\n- When in doubt: save raw data but don't update brain page\n\n## Report Storage\n\nAfter enrichment sweeps, save a report:\n- Number of entities processed\n- New pages created vs existing updated\n- Data sources called and results quality\n- Notable discoveries or contradictions\n- Validation flags or API failures\n\nThis creates an audit trail for brain enrichment over time.\n\n## Anti-Patterns\n\n- Creating stub pages with no content\n- Enriching without checking brain first\n- Overwriting user's direct statements with API data\n- Creating pages for non-notable entities\n\n## Output Format\n\nAn enriched person page contains:\n- **Frontmatter** with type, tags, company, relationship, and contact fields\n- **Executive summary** (1 paragraph: how you know them, why they matter, relationship state)\n- **State** section with hard facts and inline `[Source: ...]` citations\n- **Texture sections** (What They Believe, What They're Building, What Motivates Them, Hobby Horses)\n- **Assessment** with trajectory read\n- **Relationship** history and contact info\n- **Network** connections and mutual contacts\n- **Timeline** in reverse chronological order, every entry dated with source citation\n\nAn enriched company page contains:\n- **Frontmatter** with type and tags\n- **Executive summary** (1 paragraph)\n- **State** section (what they do, stage, key people, metrics, your connection)\n- **Open Threads** (active items, pending decisions)\n- **Timeline** in reverse chronological order with dated, cited entries\n\nBoth page types have bidirectional back-links to every entity they mention.\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- List pages in gbrain by type (list_pages)\n- Store raw API data in gbrain (put_raw_data)\n- Retrieve raw data from gbrain (get_raw_data)\n- Link entities in gbrain (add_link)\n- Check backlinks in gbrain (get_backlinks)\n","# Enrich Skill\n\nEnrich person and company pages from external sources. Scale effort to importance.\n\n## Contract\n\nThis skill guarantees:\n- Every enriched page has compiled truth (State section) with inline citations\n- Every enriched page has a timeline with dated entries\n- Back-links are created bidirectionally\n- Tiered enrichment: Tier 1 (full), Tier 2 (medium), Tier 3 (minimal) based on notability\n- No stubs: every new page has meaningful content from web search or existing brain context\n\n> **Filing rule:** Read `skills\u002F_brain-filing-rules.md` before creating any new page.\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## Philosophy\n\nA brain page should read like an intelligence dossier, not a LinkedIn scrape.\nFacts are table stakes. Texture is the value -- what do they believe, what are\nthey building, what makes them tick, where are they headed.\n\n## Citation Requirements (MANDATORY)\n\n> **Convention:** see `skills\u002Fconventions\u002Fquality.md` for citation formats and source precedence.\n\nWhen sources conflict, note the contradiction with both citations.\n\n## When To Enrich\n\n### Primary triggers\n- User mentions an entity in conversation\n- Entity appears in a meeting transcript or email\n- New contact appears with significant context\n- Entity makes news or has a major event\n- Any ingest pipeline encounters a notable entity\n\n### Do NOT enrich\n- Random mentions with no relationship signal\n- Bot\u002Fspam accounts\n- Entities with no substantive connection to the user's work\n- Same page enriched within the past week (unless new signal warrants it)\n\n## Enrichment Tiers\n\nScale enrichment to importance. Don't waste API calls on low-value entities.\n\n| Tier | Who | Effort | Sources |\n|------|-----|--------|---------|\n| 1 (key) | Inner circle, close collaborators, key contacts | Full pipeline | All available APIs + deep web research |\n| 2 (notable) | Occasional interactions, industry figures | Moderate | Web research + social + brain cross-ref |\n| 3 (minor) | Worth tracking, not critical | Light | Brain cross-ref + social lookup if handle known |\n\n## The Enrichment Protocol (7 Steps)\n\n### Step 1: Identify entities\n\nExtract people, companies, concepts from the incoming signal.\n\n### Step 2: Check brain state\n\nFor each entity:\n- `gbrain search \"name\"` -- does a page already exist?\n- **If yes:** UPDATE path (add new signal, update compiled truth if material)\n- **If no:** CREATE path (check notability gate first, then create)\n\n### Step 3: Extract signal from source\n\nDon't just capture facts. Capture texture:\n\n| Signal Type | What to Extract |\n|-------------|----------------|\n| Opinions, beliefs | What They Believe section |\n| Current projects, features shipped | What They're Building section |\n| Ambition, career arc, motivation | What Motivates Them section |\n| Topics they return to obsessively | Hobby Horses section |\n| Who they amplify, argue with, respect | Network \u002F Relationships |\n| Ascending, plateauing, pivoting? | Trajectory section |\n| Role, company, funding, location | State section (hard facts) |\n\n### Step 4: External data source lookups\n\nPriority order -- stop when you have enough signal for the entity's tier.\n\n**4a. Brain cross-reference (always, all tiers)**\n- `gbrain search \"name\"` and `gbrain query \"what do we know about name\"`\n- Check related pages: company pages for person enrichment and vice versa\n- This is free and often the richest source\n\n**4b. Web research (Tier 1 and 2)**\n- Use Perplexity, Brave Search, Exa, or equivalent web research tool\n- **Key pattern:** Send existing brain knowledge as context so the search\n  returns DELTA (what's new vs what you already know), not a rehash\n- Opus-class models for Tier 1 deep research, lighter models for Tier 2\n\n**4c. Social media lookup (all tiers when handle known)**\n- Pull recent posts\u002Ftweets for tone, interests, current focus\n- Social media is the highest-texture signal for what someone actually thinks\n\n**4d. People enrichment APIs (Tier 1)**\n- LinkedIn data, career history, connections, education\n\n**4e. Company enrichment APIs (Tier 1)**\n- Company data, financials, headcount, key hires, recent news\n\n| Data Need | Example Sources | Tier |\n|-----------|----------------|------|\n| Web research | Perplexity, Brave, Exa | 1-2 |\n| LinkedIn \u002F career | Crustdata, Proxycurl, People Data Labs | 1 |\n| Career history | Happenstance, LinkedIn | 1 |\n| Funding \u002F company data | Crunchbase, PitchBook, Clearbit | 1 |\n| Social media | Platform APIs, web scraping | 1-3 |\n| Meeting history | Calendar\u002Fmeeting transcript tools | 1-2 |\n\n### Step 5: Save raw data (preserves provenance)\n\nStore raw API responses via `put_raw_data` in gbrain:\n```json\n{\n  \"source\": \"crustdata\",\n  \"fetched_at\": \"2026-04-11T...\",\n  \"query\": \"jane doe\",\n  \"data\": { ... }\n}\n```\n\nRaw data preserves provenance. If the compiled truth is ever questioned,\nthe raw data shows exactly what the API returned.\n\n### Step 6: Write to brain\n\n#### CREATE path\n\n1. Check notability gate (see `skills\u002F_brain-filing-rules.md`)\n2. Check filing rules -- where does this entity go?\n3. Create page with the appropriate template (below)\n4. Fill compiled truth with citations\n5. Add first timeline entry\n6. Leave empty sections as `[No data yet]` (don't fill with boilerplate)\n\n#### UPDATE path\n\n1. Add new timeline entries (reverse-chronological, append-only)\n2. Update compiled truth ONLY if the new signal materially changes the picture\n3. Update State section with new facts\n4. Flag contradictions between new signal and existing compiled truth\n5. Don't overwrite user-written assessments with API boilerplate\n\n#### Person page template\n\n```markdown\n---\ntitle: Full Name\ntype: person\ncreated: YYYY-MM-DD\nupdated: YYYY-MM-DD\ntags: []\ncompany: Current Company\nrelationship: How the user knows them\nemail:\nlinkedin:\ntwitter:\nlocation:\n---\n\n# Full Name\n\n> 1-paragraph executive summary: HOW do you know them, WHY do they matter,\n> what's the current state of the relationship.\n\n## State\nRole, company, key context. Hard facts only.\n\n## What They Believe\nIdeology, first principles, worldview. What hills do they die on?\n\n## What They're Building\nCurrent projects, recent launches, what they're focused on.\n\n## What Motivates Them\nAmbition, career arc, what drives them.\n\n## Hobby Horses\nTopics they return to obsessively. Recurring themes in their work\u002Fposts.\n\n## Assessment\nYour read on this person. Strengths, gaps, trajectory.\n\n## Trajectory\nAscending, plateauing, pivoting, declining? Where are they headed?\n\n## Relationship\nHistory of interactions, shared context, relationship quality.\n\n## Contact\nEmail, social handles, preferred communication channel.\n\n## Network\nKey connections, mutual contacts, organizational relationships.\n\n## Open Threads\nActive conversations, pending items, things to follow up on.\n\n---\n\n## Timeline\nReverse chronological. Every entry has a date and [Source: ...] citation.\n- **YYYY-MM-DD** | Event description [Source: ...]\n```\n\n#### Company page template\n\n```markdown\n---\ntitle: Company Name\ntype: company\ncreated: YYYY-MM-DD\nupdated: YYYY-MM-DD\ntags: []\n---\n\n# Company Name\n\n> 1-paragraph executive summary.\n\n## State\nWhat they do, stage, key people, key metrics, your connection.\n\n## Open Threads\nActive items, pending decisions, things to track.\n\n---\n\n## Timeline\n- **YYYY-MM-DD** | Event description [Source: ...]\n```\n\n### Step 7: Cross-reference\n\n- Update company pages from person enrichment (and vice versa)\n- Update related project\u002Fdeal pages if relevant context surfaced\n- Check index files if the brain uses them\n\n**Note (v0.10.1):** Links between brain pages are auto-created on every\n`put_page` call (auto-link post-hook). Step 7 focuses on content\ncross-references (updating related pages' compiled truth with new signal\nfrom this enrichment), not on creating links. Verify via the `auto_links`\nfield in the put_page response (`{ created, removed, errors }`).\nTimeline entries still need explicit `gbrain timeline-add` calls.\n\n## Bulk Enrichment Rules\n\n- **Test on 3-5 entities first.** Read actual output. Check quality.\n- Only proceed to bulk after test shots pass your quality bar.\n- 3+ entities from one source -> batch process or spawn sub-agent\n- Throttle API calls. Respect rate limits.\n- Commit every 5-10 entities during bulk runs.\n- Save a report after bulk enrichment (see Report Storage below).\n\n## Validation Rules\n\n- Connection count \u003C 20 on LinkedIn = likely wrong person, skip\n- Name mismatch between brain and API = skip, flag for review\n- Joke profiles or obviously wrong data = save to raw, don't update page\n- Don't overwrite user-written assessments with API boilerplate\n- When in doubt: save raw data but don't update brain page\n\n## Report Storage\n\nAfter enrichment sweeps, save a report:\n- Number of entities processed\n- New pages created vs existing updated\n- Data sources called and results quality\n- Notable discoveries or contradictions\n- Validation flags or API failures\n\nThis creates an audit trail for brain enrichment over time.\n\n## Anti-Patterns\n\n- Creating stub pages with no content\n- Enriching without checking brain first\n- Overwriting user's direct statements with API data\n- Creating pages for non-notable entities\n\n## Output Format\n\nAn enriched person page contains:\n- **Frontmatter** with type, tags, company, relationship, and contact fields\n- **Executive summary** (1 paragraph: how you know them, why they matter, relationship state)\n- **State** section with hard facts and inline `[Source: ...]` citations\n- **Texture sections** (What They Believe, What They're Building, What Motivates Them, Hobby Horses)\n- **Assessment** with trajectory read\n- **Relationship** history and contact info\n- **Network** connections and mutual contacts\n- **Timeline** in reverse chronological order, every entry dated with source citation\n\nAn enriched company page contains:\n- **Frontmatter** with type and tags\n- **Executive summary** (1 paragraph)\n- **State** section (what they do, stage, key people, metrics, your connection)\n- **Open Threads** (active items, pending decisions)\n- **Timeline** in reverse chronological order with dated, cited entries\n\nBoth page types have bidirectional back-links to every entity they mention.\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- List pages in gbrain by type (list_pages)\n- Store raw API data in gbrain (put_raw_data)\n- Retrieve raw data from gbrain (get_raw_data)\n- Link entities in gbrain (add_link)\n- Check backlinks in gbrain (get_backlinks)\n",{"name":5,"tools":43,"version":49,"mutating":50,"triggers":51,"writes_to":56,"description":59,"writes_pages":50},[44,45,36,29,46,47,48],"get_page","put_page","add_link","add_timeline_entry","get_backlinks","1.0.0",true,[5,52,53,54,55],"create person page","update company page","who is this person","look up this company",[57,58],"people\u002F","companies\u002F","Enrich brain pages with tiered enrichment protocol. Creates and updates\nperson\u002Fcompany pages with compiled truth, timeline, and cross-links.\nUse when a new entity is mentioned or an existing page needs updating.\n","main","7850740bd837adb32f0a109ab2af82482196c6f2","skills\u002Fgbrain-enrich",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":50},[72,75,78],{"tool":73,"command":74},"npx","npx skills add shengdabai\u002FTony-Claude-Code-Skills --skill enrich",{"tool":76,"command":77},"bunx","bunx skills add shengdabai\u002FTony-Claude-Code-Skills --skill enrich",{"tool":79,"command":80},"pnpm","pnpm dlx skills add shengdabai\u002FTony-Claude-Code-Skills --skill enrich","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fgbrain-enrich\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",[],[]]