[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70M87HW19Q6GYQMB0ETMTJS":3,"skill-same:01M70M87HW19Q6GYQMB0ETMTJS":94},{"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":64,"commitSha":65,"skillDirectory":66,"forksCount":67,"repositoryHtmlUrl":68,"repositoryHomepageUrl":69,"ownerHtmlUrl":70,"ownerBlogUrl":71,"ownerDescription":72,"updatedAt":73,"install":74,"resources":87},"01M70M87HW19Q6GYQMB0ETMTJS","query",null,"Answer questions using the brain's knowledge with 3-layer search, synthesis,\nand citation propagation. Use when the user asks a question, wants a lookup,\nor needs information from the brain.","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-query\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"notes","page","for","backlinks","do","graph","layer","list","brain","me","relationship","when","false","information","question","knowledge","up","search","get","2026-11-10 10:12:30",false,"---\nname: query\nversion: 1.0.0\ndescription: |\n  Answer questions using the brain's knowledge with 3-layer search, synthesis,\n  and citation propagation. Use when the user asks a question, wants a lookup,\n  or needs information from the brain.\ntriggers:\n  - \"what do we know about\"\n  - \"tell me about\"\n  - \"who is\"\n  - \"what happened\"\n  - \"search for\"\n  - \"look up\"\n  - \"background on\"\n  - \"notes on\"\n  - \"who knows who\"\n  - \"relationship between\"\n  - \"connections\"\n  - \"graph query\"\ntools:\n  - search\n  - query\n  - get_page\n  - list_pages\n  - get_backlinks\n  - traverse_graph\n  - get_timeline\nmutating: false\n---\n\n# Query Skill\n\nAnswer questions using the brain's knowledge with 3-layer search and synthesis.\n\n## Contract\n\nThis skill guarantees:\n- Every answer is grounded in brain content (no hallucination)\n- Every claim has a citation tracing back to a specific page slug\n- Gaps are flagged explicitly (\"the brain doesn't have information on X\")\n- Source precedence is respected (user statements > compiled truth > timeline > external)\n- Conflicting sources are noted with both citations\n\n## Phases\n\n1. **Decompose the question** into search strategies:\n   - Keyword search for specific names, dates, terms\n   - Semantic query for conceptual questions\n   - Structured queries (list by type, backlinks) for relational questions\n2. **Execute searches:**\n   - Keyword search gbrain for FTS matches (search)\n   - Hybrid search gbrain for semantic+keyword with expansion (query)\n   - List pages in gbrain by type or check backlinks for structural queries\n3. **Read top results.** Read the top 3-5 pages from gbrain to get full context.\n4. **Synthesize answer** with citations. Every claim traces back to a specific page slug.\n5. **Flag gaps.** If the brain doesn't have info, say \"the brain doesn't have information on X\" rather than hallucinating.\n\n## Anti-Patterns\n\n- Answering from general knowledge when the brain has relevant content\n- Hallucinating facts not in the brain\n- Silently picking one source when sources conflict\n- Loading full pages when search chunks are sufficient\n- Ignoring source precedence (user statements are highest authority)\n\n## Output Format\n\nAnswers should include:\n- Direct response to the question\n- Citations: \"According to [Source: people\u002Fjane-doe, compiled truth]...\"\n- Gap flags: \"The brain doesn't have information on X\"\n- Conflict notes when sources disagree\n\n## Quality Rules\n\n- Never hallucinate. Only answer from brain content.\n- Cite sources: \"According to concepts\u002Fdo-things-that-dont-scale...\"\n- Flag stale results: if a search result shows [STALE], note that the info may be outdated\n- For \"who\" questions, use backlinks and typed links to find connections\n- For \"what happened\" questions, use timeline entries\n- For \"what do we know\" questions, read compiled_truth directly\n\n## Token-Budget Awareness\n\nSearch returns **chunks**, not full pages. Read the excerpts first before deciding\nwhether to load a full page.\n\n- `gbrain search` \u002F `gbrain query` return ranked chunks with context snippets.\n  These are often enough to answer the question directly.\n- Only use `gbrain get \u003Cslug>` to load the full page when a chunk confirms the\n  page is relevant and you need more context (e.g., compiled truth, timeline).\n- **\"Tell me about X\"** -- get the full page (the user wants the complete picture).\n- **\"Did anyone mention Y?\"** -- search results are enough (the user wants a yes\u002Fno with evidence).\n\n### Source precedence\n\nWhen multiple sources provide conflicting information, follow this precedence:\n\n1. **User's direct statements** (highest authority -- what the user told you directly)\n2. **Compiled truth** (the brain's synthesized, cited understanding)\n3. **Timeline entries** (raw evidence, reverse-chronological)\n4. **External sources** (web search, API enrichment -- lowest authority)\n\nWhen sources conflict, note the contradiction with both citations. Don't silently\npick one.\n\n## Citation in Answers\n\nWhen referencing brain pages in your answer, propagate inline citations:\n- Cite the page: \"According to [Source: people\u002Fjane-doe, compiled truth]...\"\n- When brain pages have inline `[Source: ...]` citations, propagate them so\n  the user can trace facts to their origin\n- When you synthesize across multiple pages, cite all sources\n\n## Graph Traversal (v0.10.1+)\n\nFor relationship questions (\"who knows who at X?\", \"connections between A and B\",\n\"who works at Acme?\", \"who attended the standup?\"), use the graph layer instead\nof full-text search:\n\n- `gbrain graph-query \u003Cslug> --type \u003Clink_type> --depth N --direction in|out|both`\n- Available link types: `attended`, `works_at`, `invested_in`, `founded`, `advises`, `mentions`, `source`\n- `--direction in` answers \"who points to X?\" (e.g., who works at company X)\n- `--direction out` answers \"what does X point to?\" (default)\n- `--depth N` controls multi-hop traversal (default 5)\n\nExamples:\n- \"Who works at Acme?\" → `gbrain graph-query companies\u002Facme --type works_at --direction in`\n- \"Who attended Demo Day W26?\" → `gbrain graph-query meetings\u002Fdemo-day-w26 --type attended --direction out`\n- \"What companies has Emily advised?\" → `gbrain graph-query people\u002Femily --type advises --direction out`\n- \"Who has Alice met (via meetings)?\" → `gbrain graph-query people\u002Falice --type attended --depth 2`\n\nCombine with `gbrain query` for queries that need BOTH semantic similarity AND\ngraph structure. Search results are ranked with a small backlink boost so well-\nconnected entities surface higher.\n\n## Search Quality Awareness\n\nIf search results seem off (wrong results, missing known pages, irrelevant hits):\n- Run `gbrain doctor --json` to check index health\n- Check embedding coverage -- partial embeddings degrade hybrid search\n- Compare keyword search (`gbrain search`) vs hybrid search (`gbrain query`)\n  for the same query to isolate whether the issue is embedding-related\n- Report search quality issues in the maintain workflow (see maintain skill)\n\n## Tools Used\n\n- Keyword search gbrain (search)\n- Hybrid search gbrain (query)\n- Read a page from gbrain (get_page)\n- List pages in gbrain with filters (list_pages)\n- Check backlinks in gbrain (get_backlinks)\n- Traverse the link graph in gbrain (traverse_graph)\n- View timeline entries in gbrain (get_timeline)\n","# Query Skill\n\nAnswer questions using the brain's knowledge with 3-layer search and synthesis.\n\n## Contract\n\nThis skill guarantees:\n- Every answer is grounded in brain content (no hallucination)\n- Every claim has a citation tracing back to a specific page slug\n- Gaps are flagged explicitly (\"the brain doesn't have information on X\")\n- Source precedence is respected (user statements > compiled truth > timeline > external)\n- Conflicting sources are noted with both citations\n\n## Phases\n\n1. **Decompose the question** into search strategies:\n   - Keyword search for specific names, dates, terms\n   - Semantic query for conceptual questions\n   - Structured queries (list by type, backlinks) for relational questions\n2. **Execute searches:**\n   - Keyword search gbrain for FTS matches (search)\n   - Hybrid search gbrain for semantic+keyword with expansion (query)\n   - List pages in gbrain by type or check backlinks for structural queries\n3. **Read top results.** Read the top 3-5 pages from gbrain to get full context.\n4. **Synthesize answer** with citations. Every claim traces back to a specific page slug.\n5. **Flag gaps.** If the brain doesn't have info, say \"the brain doesn't have information on X\" rather than hallucinating.\n\n## Anti-Patterns\n\n- Answering from general knowledge when the brain has relevant content\n- Hallucinating facts not in the brain\n- Silently picking one source when sources conflict\n- Loading full pages when search chunks are sufficient\n- Ignoring source precedence (user statements are highest authority)\n\n## Output Format\n\nAnswers should include:\n- Direct response to the question\n- Citations: \"According to [Source: people\u002Fjane-doe, compiled truth]...\"\n- Gap flags: \"The brain doesn't have information on X\"\n- Conflict notes when sources disagree\n\n## Quality Rules\n\n- Never hallucinate. Only answer from brain content.\n- Cite sources: \"According to concepts\u002Fdo-things-that-dont-scale...\"\n- Flag stale results: if a search result shows [STALE], note that the info may be outdated\n- For \"who\" questions, use backlinks and typed links to find connections\n- For \"what happened\" questions, use timeline entries\n- For \"what do we know\" questions, read compiled_truth directly\n\n## Token-Budget Awareness\n\nSearch returns **chunks**, not full pages. Read the excerpts first before deciding\nwhether to load a full page.\n\n- `gbrain search` \u002F `gbrain query` return ranked chunks with context snippets.\n  These are often enough to answer the question directly.\n- Only use `gbrain get \u003Cslug>` to load the full page when a chunk confirms the\n  page is relevant and you need more context (e.g., compiled truth, timeline).\n- **\"Tell me about X\"** -- get the full page (the user wants the complete picture).\n- **\"Did anyone mention Y?\"** -- search results are enough (the user wants a yes\u002Fno with evidence).\n\n### Source precedence\n\nWhen multiple sources provide conflicting information, follow this precedence:\n\n1. **User's direct statements** (highest authority -- what the user told you directly)\n2. **Compiled truth** (the brain's synthesized, cited understanding)\n3. **Timeline entries** (raw evidence, reverse-chronological)\n4. **External sources** (web search, API enrichment -- lowest authority)\n\nWhen sources conflict, note the contradiction with both citations. Don't silently\npick one.\n\n## Citation in Answers\n\nWhen referencing brain pages in your answer, propagate inline citations:\n- Cite the page: \"According to [Source: people\u002Fjane-doe, compiled truth]...\"\n- When brain pages have inline `[Source: ...]` citations, propagate them so\n  the user can trace facts to their origin\n- When you synthesize across multiple pages, cite all sources\n\n## Graph Traversal (v0.10.1+)\n\nFor relationship questions (\"who knows who at X?\", \"connections between A and B\",\n\"who works at Acme?\", \"who attended the standup?\"), use the graph layer instead\nof full-text search:\n\n- `gbrain graph-query \u003Cslug> --type \u003Clink_type> --depth N --direction in|out|both`\n- Available link types: `attended`, `works_at`, `invested_in`, `founded`, `advises`, `mentions`, `source`\n- `--direction in` answers \"who points to X?\" (e.g., who works at company X)\n- `--direction out` answers \"what does X point to?\" (default)\n- `--depth N` controls multi-hop traversal (default 5)\n\nExamples:\n- \"Who works at Acme?\" → `gbrain graph-query companies\u002Facme --type works_at --direction in`\n- \"Who attended Demo Day W26?\" → `gbrain graph-query meetings\u002Fdemo-day-w26 --type attended --direction out`\n- \"What companies has Emily advised?\" → `gbrain graph-query people\u002Femily --type advises --direction out`\n- \"Who has Alice met (via meetings)?\" → `gbrain graph-query people\u002Falice --type attended --depth 2`\n\nCombine with `gbrain query` for queries that need BOTH semantic similarity AND\ngraph structure. Search results are ranked with a small backlink boost so well-\nconnected entities surface higher.\n\n## Search Quality Awareness\n\nIf search results seem off (wrong results, missing known pages, irrelevant hits):\n- Run `gbrain doctor --json` to check index health\n- Check embedding coverage -- partial embeddings degrade hybrid search\n- Compare keyword search (`gbrain search`) vs hybrid search (`gbrain query`)\n  for the same query to isolate whether the issue is embedding-related\n- Report search quality issues in the maintain workflow (see maintain skill)\n\n## Tools Used\n\n- Keyword search gbrain (search)\n- Hybrid search gbrain (query)\n- Read a page from gbrain (get_page)\n- List pages in gbrain with filters (list_pages)\n- Check backlinks in gbrain (get_backlinks)\n- Traverse the link graph in gbrain (traverse_graph)\n- View timeline entries in gbrain (get_timeline)\n",{"name":5,"tools":43,"version":49,"mutating":39,"triggers":50,"description":63},[36,5,44,45,46,47,48],"get_page","list_pages","get_backlinks","traverse_graph","get_timeline","1.0.0",[51,52,53,54,55,56,57,58,59,60,61,62],"what do we know about","tell me about","who is","what happened","search for","look up","background on","notes on","who knows who","relationship between","connections","graph query","Answer questions using the brain's knowledge with 3-layer search, synthesis,\nand citation propagation. Use when the user asks a question, wants a lookup,\nor needs information from the brain.\n","main","7850740bd837adb32f0a109ab2af82482196c6f2","skills\u002Fgbrain-query",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":75,"prompt":85,"zipAvailable":86},[76,79,82],{"tool":77,"command":78},"npx","npx skills add shengdabai\u002FTony-Claude-Code-Skills --skill query",{"tool":80,"command":81},"bunx","bunx skills add shengdabai\u002FTony-Claude-Code-Skills --skill query",{"tool":83,"command":84},"pnpm","pnpm dlx skills add shengdabai\u002FTony-Claude-Code-Skills --skill query","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fgbrain-query\u002FSKILL.md",true,[88],{"path":89,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":92,"sourceHtmlUrl":93},"routing-eval.jsonl","OTHER","其他",535,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fgbrain-query\u002Frouting-eval.jsonl",[95,104,112,120,128,136],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":99,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":103},"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":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":108,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":103},"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":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":116,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":103},"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":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":124,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":103},"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":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":132,"sourceHtmlUrl":133,"categories":134,"keywords":135,"publishedAt":103},"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":137,"name":138,"nameZh":6,"description":139,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":140,"categories":141,"keywords":142,"publishedAt":103},"01M73G086AXAH9DW1H5G5N3CPB","dbs-video-extract","接收抖音、小红书、微信视频号等短视频链接或分享文案，查询作品／账号数据并提取语音文字稿，按作者和标题归档为 Markdown。用户希望完整解析短视频、取得数据或文字稿时使用；运行前检查 TikHub 与轻抖使用凭证，缺少时用新手能理解的方式引导购买和安全配置。","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fdbs-video-extract\u002FSKILL.md",[],[]]