[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77MCZZJCWXXY96XNET0TC5V":3,"skill-same:01M77MCZZJCWXXY96XNET0TC5V":47},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M77MCZZJCWXXY96XNET0TC5V","map-domain-experts",null,"Use when a user wants to quickly learn a domain\u002Ffield\u002F领域 by mapping representative experts, scholars, practitioners, seminal works, core consensus, major disagreements, comparison tables, or an entry learning roadmap.","Lord1Egypt\u002Fawesome-skill-forge","Lord1Egypt","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F99746359?v=4","01M7592YDNT0XK9WJ0T2MQVPDN","Mohamed Mounir Ali AL Keshita","01M75GRFNHC8VZNWEB8DKDE433",3,"MIT","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fcommunity\u002Fclawhub\u002Fm\u002Fmap-domain-experts\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: map-domain-experts\ndescription: Use when a user wants to quickly learn a domain\u002Ffield\u002F领域 by mapping representative experts, scholars, practitioners, seminal works, core consensus, major disagreements, comparison tables, or an entry learning roadmap.\n---\n\n# Map Domain Experts\n\n## Overview\n\nUse this skill to turn \"I want to quickly learn X\" into a compact expert map: who matters, what they agree on, where they disagree, and how to start learning. Optimize for accuracy, intellectual structure, and traceable evidence rather than a generic reading list.\n\nDefault to answering in the user's language.\n\n## Workflow\n\n### 1. Scope the Field\n\nIf the user leaves the field as a placeholder, e.g. `【领域名称】`, ask for the field. If the field is broad, proceed with a clear scope assumption unless that would make the answer misleading.\n\nState the interpreted scope in 1-2 sentences before the main answer:\n\n- domain boundary, such as subfield, time period, region, or applied vs academic angle\n- whether \"expert\" includes scholars, builders, operators, critics, or public intellectuals\n\n### 2. Build an Evidence Base\n\nFor current, niche, contested, or high-stakes domains, verify with browsing or available primary sources. Prefer:\n\n- seminal papers\u002Fbooks and publisher pages\n- university, lab, institutional, or official biography pages\n- citation indexes, conference keynotes, standards bodies, widely adopted tools\u002Fframeworks\n- reputable interviews, lectures, debates, or essays when they clarify a living practitioner's view\n\nDo not fabricate expertise, works, citations, or consensus. If evidence is thin, say so and reduce confidence.\n\n### 3. Select 5-10 Representative People\n\nChoose people who collectively explain the field, not merely the most famous names. Balance:\n\n- founders\u002Fseminal theorists\n- method builders or empirical researchers\n- practitioners who changed real-world practice\n- critics or alternative schools that reveal fault lines\n- current voices if the field is active and changing\n\nFor each person, capture why they matter in one concrete sentence: concept introduced, method created, institution shaped, tool built, policy changed, or debate reframed.\n\n### 4. Extract Consensus and Disagreement\n\nCore consensus must be a small set of propositions that most selected experts would recognize, even if they phrase them differently. Tie each consensus point to multiple experts.\n\nDisagreements should be axes, not trivia. Look for:\n\n- theory: what explains the phenomenon?\n- method: what counts as valid evidence or good practice?\n- values: what outcomes should be optimized, protected, or avoided?\n- scope: where does the theory\u002Fmethod stop working?\n- strategy: what should beginners, organizations, or policymakers do first?\n\nFor each disagreement, name the sides, the stakes, and a concrete example of how the disagreement changes action.\n\n## Output Format\n\nUse this structure unless the user asks for another format:\n\n1. `范围说明`: State the scope assumption.\n2. `代表人物`: List 5-10 experts with 1-2 sentences each on why they matter.\n3. `核心共识`: Summarize 3-6 shared claims.\n4. `关键分歧`: Summarize the most important disagreements by axis.\n5. `对照表`: Include columns:\n   `专家 | 代表作品\u002F论文\u002F观点 | 核心主张 | 与其他人的分歧`\n6. `入门学习路线`: Give a staged path:\n   `先读\u002F先看` -> `再读\u002F再看` -> `对照阅读` -> `继续追踪的问题`\n7. `资料来源`: Include concise citations or links when sources were used.\n\n## Quality Bar\n\nThe result should feel like a map of the field's intellectual terrain. Avoid flat encyclopedia summaries. Make tradeoffs visible: why these people, why these disagreements, and why this learning order.\n","# Map Domain Experts\n\n## Overview\n\nUse this skill to turn \"I want to quickly learn X\" into a compact expert map: who matters, what they agree on, where they disagree, and how to start learning. Optimize for accuracy, intellectual structure, and traceable evidence rather than a generic reading list.\n\nDefault to answering in the user's language.\n\n## Workflow\n\n### 1. Scope the Field\n\nIf the user leaves the field as a placeholder, e.g. `【领域名称】`, ask for the field. If the field is broad, proceed with a clear scope assumption unless that would make the answer misleading.\n\nState the interpreted scope in 1-2 sentences before the main answer:\n\n- domain boundary, such as subfield, time period, region, or applied vs academic angle\n- whether \"expert\" includes scholars, builders, operators, critics, or public intellectuals\n\n### 2. Build an Evidence Base\n\nFor current, niche, contested, or high-stakes domains, verify with browsing or available primary sources. Prefer:\n\n- seminal papers\u002Fbooks and publisher pages\n- university, lab, institutional, or official biography pages\n- citation indexes, conference keynotes, standards bodies, widely adopted tools\u002Fframeworks\n- reputable interviews, lectures, debates, or essays when they clarify a living practitioner's view\n\nDo not fabricate expertise, works, citations, or consensus. If evidence is thin, say so and reduce confidence.\n\n### 3. Select 5-10 Representative People\n\nChoose people who collectively explain the field, not merely the most famous names. Balance:\n\n- founders\u002Fseminal theorists\n- method builders or empirical researchers\n- practitioners who changed real-world practice\n- critics or alternative schools that reveal fault lines\n- current voices if the field is active and changing\n\nFor each person, capture why they matter in one concrete sentence: concept introduced, method created, institution shaped, tool built, policy changed, or debate reframed.\n\n### 4. Extract Consensus and Disagreement\n\nCore consensus must be a small set of propositions that most selected experts would recognize, even if they phrase them differently. Tie each consensus point to multiple experts.\n\nDisagreements should be axes, not trivia. Look for:\n\n- theory: what explains the phenomenon?\n- method: what counts as valid evidence or good practice?\n- values: what outcomes should be optimized, protected, or avoided?\n- scope: where does the theory\u002Fmethod stop working?\n- strategy: what should beginners, organizations, or policymakers do first?\n\nFor each disagreement, name the sides, the stakes, and a concrete example of how the disagreement changes action.\n\n## Output Format\n\nUse this structure unless the user asks for another format:\n\n1. `范围说明`: State the scope assumption.\n2. `代表人物`: List 5-10 experts with 1-2 sentences each on why they matter.\n3. `核心共识`: Summarize 3-6 shared claims.\n4. `关键分歧`: Summarize the most important disagreements by axis.\n5. `对照表`: Include columns:\n   `专家 | 代表作品\u002F论文\u002F观点 | 核心主张 | 与其他人的分歧`\n6. `入门学习路线`: Give a staged path:\n   `先读\u002F先看` -> `再读\u002F再看` -> `对照阅读` -> `继续追踪的问题`\n7. `资料来源`: Include concise citations or links when sources were used.\n\n## Quality Bar\n\nThe result should feel like a map of the field's intellectual terrain. Avoid flat encyclopedia summaries. Make tradeoffs visible: why these people, why these disagreements, and why this learning order.\n",{"name":5,"description":7},"master","4aa004da461d820f4ea5499e58eb8d196cf99016","community\u002Fclawhub\u002Fm\u002Fmap-domain-experts",0,"https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge","https:\u002F\u002Fskill-explorer-rho.vercel.app","https:\u002F\u002Fgithub.com\u002FLord1Egypt","Unbreakable. Unstoppable. Unmatched⚡.\r\n Speaker of machine tongues 🤖  | World-builder of decentralized dreams 🌐 | Defender of the digital realm🛡️.","2026-06-10 08:21:01",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add Lord1Egypt\u002Fawesome-skill-forge --skill map-domain-experts",{"tool":39,"command":40},"bunx","bunx skills add Lord1Egypt\u002Fawesome-skill-forge --skill map-domain-experts",{"tool":42,"command":43},"pnpm","pnpm dlx skills add Lord1Egypt\u002Fawesome-skill-forge --skill map-domain-experts","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fcommunity\u002Fclawhub\u002Fm\u002Fmap-domain-experts\u002FSKILL.md",true,[],[48,55,62,69,76,83],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M785WKJB99G3STR1NF9NRTJW","youtube-content","YouTube transcripts to summaries, threads, blogs.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fyoutube-content\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M785WEFHB0G2S9YA6EPR3H0E","xurl","X\u002FTwitter via xurl CLI: post, search, DM, media, v2 API.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fxurl\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M785W98EDN4EFJXJPMQEHCRC","touchdesigner-mcp","Control a running TouchDesigner instance via twozero MCP — create operators, set parameters, wire connections, execute Python, build real-time visuals. 36 native tools.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Ftouchdesigner-mcp\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M785W5S9FP3QBH2V191E025P","test-driven-development","TDD: enforce RED-GREEN-REFACTOR, tests before code.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Ftest-driven-development\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M785W2AS08NSSH9YATCV6FJB","teams-meeting-pipeline","Operate the Teams meeting summary pipeline via Hermes CLI — summarize meetings, inspect pipeline status, replay jobs, manage Microsoft Graph subscriptions.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fteams-meeting-pipeline\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M785VXKW4T34BTP1SCHW1R7F","systematic-debugging","4-phase root cause debugging: understand bugs before fixing.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fsystematic-debugging\u002FSKILL.md",[],[]]