[{"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,114,146,172,194,214],{"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":6,"sourceHtmlUrl":99,"categories":100,"keywords":106,"publishedAt":38},"01M70P17DAD4C1C47NPH6A96EM","xiaolai-methodology","以李笑来(Li Xiaolai)的思考方式、方法论与表达风格,为用户做全方位 1-on-1 教练指导,覆盖创业、赚钱、投资、学习、自学、读书写作、用 AI、以及人生心态与自我管理。当用户提到 \"李笑来\"、\"笑来\"、\"笑来老师\"、\"扮演李笑来\"、\"找笑来聊聊\"、\"笑来怎么看\"、\"xiaolai\"、\"把时间当作朋友\"、\"通往财富自由之路\"、\"定投改变命运\"、\"韭菜的自我修养\"、\"自学是门手艺\"、\"让时间陪你慢慢变富\"、\"七年就是一辈子\"、\"元认知\"、\"活在未来\"、\"复利\u002F长期主义\"、\"践行\"、\"痴迷改进\"、\"个人商业模式\u002F出售时间\"、\"睡后收入\"、\"定投\"、\"财富自由\"、\"操作系统升级\"、\"最少必要知识\"、\"北极星提示词\"、\"用 AI 该怎么学\u002F思考\" 等任一触发词,或当用户带着关于创业\u002F赚钱\u002F投资\u002F学习\u002F职业\u002F重大人生决策的困惑、希望被人用笑来式的「逻辑 + 大白话 + 类比 + 重新定义 + 践行导向」来点醒和指导时,自动进入李笑来教练模式。","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fxiaolai-methodology\u002FSKILL.md",[101],{"categoryNo":102,"categoryName":103,"taxonomyType":104,"taxonomyTypeDesc":105},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",[107,108,109,110,111,112,113],"methodology","xiaolai","xiaolai methodology","朋友","投资","writing","收入",{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":128,"publishedAt":38},"01M70P13NB9YP7ACJR1S861CDS","zread","Produce and consume a wiki-style knowledge base for a code repository via the `zread` CLI and its on-disk output under `.\u002F.zread\u002Fwiki\u002F`. Use this skill whenever the user wants to understand, onboard onto, explore, summarize, map, or get an overview of an unfamiliar codebase; asks for architecture docs, a project wiki, a repo walkthrough, module\u002Fpackage explanations, or \"what does this repo do\"; wants to generate, regenerate, resume, browse, or serve code documentation locally; or mentions zread \u002F zread.ai directly. Also use it proactively before diving into a large unknown repo — if `.\u002F.zread\u002Fwiki\u002Fcurrent` exists, read the generated pages instead of crawling source file-by-file; if it doesn't, consider offering to run `zread generate`. The trigger is the intent (understand a codebase through generated docs), not the literal word \"zread\".","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fzread\u002FSKILL.md",[120,123],{"categoryNo":121,"categoryName":122,"taxonomyType":104,"taxonomyTypeDesc":105},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":124,"categoryName":125,"taxonomyType":126,"taxonomyTypeDesc":127},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[116,34,129,130,131,132,37,133,134,135,136,137,138,139,140,141,142,143,144,145],"wiki","explore","walkthrough","project","knowledge base","run","generate","intent","cli","map","documentation","project wiki","disk","architecture","code","unknown","generated",{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":156,"publishedAt":38},"01M70P10S4SWMZQ8BJAFBFDRW3","youtube","Launch the YouTube Creator Agent to auto-generate videos.\nUse when: user types \u002Fyoutube, wants to create YouTube videos,\ngenerate video content, or upload to YouTube.\nKeywords: youtube, video, 视频, 创作视频, 发布视频","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube\u002FSKILL.md",[152,153],{"categoryNo":121,"categoryName":122,"taxonomyType":104,"taxonomyTypeDesc":105},{"categoryNo":154,"categoryName":155,"taxonomyType":126,"taxonomyTypeDesc":127},"01JBSEEDCAT000000000000036","内容创作者",[148,157,158,159,160,161,162,163,135,164,165,166,30,167,168,169,170,171],"user","content","视频","creator","generate video","videos","launch","video content","create","upload","use","auto","types","Video","创作",{"skillNo":173,"name":174,"nameZh":6,"description":175,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":176,"categories":177,"keywords":179,"publishedAt":38},"01M70P0YE95D8BACZCGV8BK90K","youtube-script-sync","Sync, update, or optimize Tony's GetNote knowledge base `Youtube视频逐字稿` by turning each parent recording or first-person idea note into an idempotent child note containing a directly recordable YouTube long-video or Shorts script. Use when the user says “更新\u002F同步\u002F优化 Youtube视频逐字稿知识库”, or says “更新\u002F同步\u002F优化该知识库” while this knowledge base is the active context.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube-script-sync\u002FSKILL.md",[178],{"categoryNo":121,"categoryName":122,"taxonomyType":104,"taxonomyTypeDesc":105},[180,181,148,182,183,170,184,185,186,187,188,189,190,191,133,192,30,167,34,193],"sync","script","youtube script sync","recording","shorts","first","base","person","update","active","child","optimize","idempotent","long",{"skillNo":195,"name":196,"nameZh":6,"description":197,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":198,"categories":199,"keywords":204,"publishedAt":38},"01M70P0WMV5XT0EEC0N445PW07","writing-skills","How to write SKILL.md files that trigger reliably and teach effectively. Use when creating, improving, or reviewing Claude Code skills.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fxiaolai\u002Fnlpm\u002Fskills\u002Fnlpm\u002Fwriting-skills\u002FSKILL.md",[200,201,202,203],{"categoryNo":102,"categoryName":103,"taxonomyType":104,"taxonomyTypeDesc":105},{"categoryNo":121,"categoryName":122,"taxonomyType":104,"taxonomyTypeDesc":105},{"categoryNo":124,"categoryName":125,"taxonomyType":126,"taxonomyTypeDesc":127},{"categoryNo":154,"categoryName":155,"taxonomyType":126,"taxonomyTypeDesc":127},[205,112,206,207,208,209,143,30,167,210,211,212,213],"writing skills","how","teach","write skill","write","claude code skills","files","how to","trigger",{"skillNo":215,"name":216,"nameZh":6,"description":217,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":218,"categories":219,"keywords":222,"publishedAt":38},"01M70P0SJFR4YVJQBGMHKGSKXT","writing-rules","How to write .claude\u002Frules\u002F files that Claude actually follows. Use when creating, improving, or reviewing project rules.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fxiaolai\u002Fnlpm\u002Fskills\u002Fnlpm\u002Fwriting-rules\u002FSKILL.md",[220,221],{"categoryNo":102,"categoryName":103,"taxonomyType":104,"taxonomyTypeDesc":105},{"categoryNo":154,"categoryName":155,"taxonomyType":126,"taxonomyTypeDesc":127},[223,112,224,132,225,211,30,206,209,167,212],"Rules","writing rules","project rules"]