[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AE93Q1D3B5FMEN36A8W293":3,"skill-same:01M6AE93Q1D3B5FMEN36A8W293":160},{"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":31,"publishedAt":54,"linkOnly":55,"markdownContent":56,"markdownBody":57,"frontMatter":58,"refName":60,"commitSha":61,"skillDirectory":62,"forksCount":63,"repositoryHtmlUrl":64,"repositoryHomepageUrl":65,"ownerHtmlUrl":66,"ownerBlogUrl":67,"ownerDescription":68,"updatedAt":69,"install":70,"resources":83},"01M6AE93Q1D3B5FMEN36A8W293","technical-job-search",null,"Use this skill when a software engineer asks for help with job search tasks: parsing or analyzing a job description, tailoring a CV\u002Fresume, writing a cover letter, evaluating a job offer, or drafting a post-interview follow-up email. Do not activate for general career advice unrelated to an active job search action.","github\u002Fawesome-copilot","github","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F9919?v=4","01M6AC83DS133TPXFSP1DHNCC6","GitHub","01M6AD3PBDYPK7NVFJNJ66Y8RS",41046,"MIT","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Ftechnical-job-search\u002FSKILL.md",[18,23,28],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",{"categoryNo":29,"categoryName":30,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000038","人力资源",[32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53],"search","Job Search","technical job search","technical","up","drafting","when","cover","action","software engineer","software","active","activate","engineer","unrelated","writing","write","analyze","analyzing","email","help","tasks","2026-11-10 10:12:30",false,"---\nname: technical-job-search\ndescription: 'Use this skill when a software engineer asks for help with job search tasks: parsing or analyzing a job description, tailoring a CV\u002Fresume, writing a cover letter, evaluating a job offer, or drafting a post-interview follow-up email. Do not activate for general career advice unrelated to an active job search action.'\nlicense: MIT\nargument-hint: 'Optional: the specific task — e.g. \"analyze this JD\", \"tailor my CV\", \"write cover letter\", \"evaluate this offer\"'\n---\n\n# Technical Job Search\n\nHelps software engineers with discrete job search tasks: job description analysis, CV tailoring, cover letter writing, offer evaluation, and follow-up emails.\n\n---\n\n## Job Description Analysis\n\nWhen given a job description, extract and structure:\n\n**Must-haves** (explicitly required or repeated multiple times):\n- Technical skills, years of experience, specific domain knowledge\n\n**Nice-to-haves** (preferred, a bonus, or mentioned once):\n- List these separately. Candidates often disqualify themselves over requirements that are actually optional.\n\n**What the role actually solves** (inferred from the description):\n- Summarize in 2-3 sentences what business problem this hire addresses\n\n**Red flags to surface**:\n- \"Wear many hats\" with no clarity on scope — risk of undefined ownership\n- 10+ must-have technologies for a single role — unrealistic bar or poor team planning\n- No mention of team size, tech stack, or what the role ships — may indicate disorganization\n\n---\n\n## CV \u002F Resume Tailoring\n\nWhen tailoring a CV to a specific job description:\n\n1. **Match language exactly** — use the same terminology as the JD, not synonyms. If the JD says \"distributed systems\", do not write \"large-scale systems\".\n2. **Lead with impact** — every bullet should have a result: \"Reduced P99 latency by 40%\" not \"Worked on performance improvements\".\n3. **Quantify everything possible** — users, QPS, team size, cost saved, revenue impact.\n4. **Cut what does not match** — a two-page CV tailored to the role beats a four-page generic one.\n5. **Mirror the seniority signals** — entry roles want \"built\", senior roles want \"designed\", staff and principal roles want \"drove\" or \"defined\".\n\nDo not keyword-stuff. Write for the hiring manager reading it, not for an ATS parser.\n\n---\n\n## Cover Letter Writing\n\nA cover letter should answer three questions in under 300 words:\n\n1. **Why this company?** Something specific — a product, a technical challenge they have written about, a problem space you care about. Not \"I admire your mission.\"\n2. **Why you?** One or two concrete things from your background that directly match what they need. Link to the specific role, not your full career history.\n3. **Why now?** What is your motivation at this point in your career? One sentence.\n\nFormat: three short paragraphs. No preamble (\"I am writing to apply for...\"). No summary of your CV.\n\nAvoid:\n- Restating your CV in prose form\n- \"I am passionate about...\"\n- Generic company praise (\"a leader in the industry\", \"innovative company\")\n- Going longer than one page\n\n---\n\n## Offer Evaluation\n\nWhen evaluating a job offer, compare across these dimensions:\n\n**Compensation**\n- Base salary: check against market rate for role, level, and location (levels.fyi, Glassdoor, Blind, Comprehensive.io)\n- Equity: current valuation, vesting schedule (4-year with 1-year cliff is standard), dilution risk for early-stage companies\n- Bonus: target percentage vs actual historical payout\n- Total comp = base + expected bonus + annualized equity value\n\n**Role clarity**\n- Scope: what does \"owning\" this role actually mean vs what is already decided?\n- Team: size, structure, who you report to, tenure of the team\n- Growth: what does the next level look like and how long do people typically take to get there?\n\n**Company health**\n- Stage: runway, revenue, growth rate — ask directly if not public\n- Engineering culture signals: PR review process, incident postmortem culture, on-call burden\n- Remote or hybrid reality: written policy vs actual practice\n\n**Red flags in an offer**\n- Pressure to decide in under 48 hours — a reasonable window is one to two weeks\n- Equity with no clear liquidity path for a company that has been private for 10+ years\n- A role described as greenfield that turns out to have 6 months of existing unmaintained code\n\nGet everything in writing before accepting.\n\n---\n\n## Follow-up Emails\n\nAfter an interview, send a follow-up within 24 hours:\n- One sentence thanking them for the time\n- One sentence referencing something specific from the conversation (a problem discussed, a question they asked)\n- One sentence reaffirming interest, if genuine\n\nDo not write multiple paragraphs. Do not restate your qualifications. Do not follow up more than once if there is no reply.\n","# Technical Job Search\n\nHelps software engineers with discrete job search tasks: job description analysis, CV tailoring, cover letter writing, offer evaluation, and follow-up emails.\n\n---\n\n## Job Description Analysis\n\nWhen given a job description, extract and structure:\n\n**Must-haves** (explicitly required or repeated multiple times):\n- Technical skills, years of experience, specific domain knowledge\n\n**Nice-to-haves** (preferred, a bonus, or mentioned once):\n- List these separately. Candidates often disqualify themselves over requirements that are actually optional.\n\n**What the role actually solves** (inferred from the description):\n- Summarize in 2-3 sentences what business problem this hire addresses\n\n**Red flags to surface**:\n- \"Wear many hats\" with no clarity on scope — risk of undefined ownership\n- 10+ must-have technologies for a single role — unrealistic bar or poor team planning\n- No mention of team size, tech stack, or what the role ships — may indicate disorganization\n\n---\n\n## CV \u002F Resume Tailoring\n\nWhen tailoring a CV to a specific job description:\n\n1. **Match language exactly** — use the same terminology as the JD, not synonyms. If the JD says \"distributed systems\", do not write \"large-scale systems\".\n2. **Lead with impact** — every bullet should have a result: \"Reduced P99 latency by 40%\" not \"Worked on performance improvements\".\n3. **Quantify everything possible** — users, QPS, team size, cost saved, revenue impact.\n4. **Cut what does not match** — a two-page CV tailored to the role beats a four-page generic one.\n5. **Mirror the seniority signals** — entry roles want \"built\", senior roles want \"designed\", staff and principal roles want \"drove\" or \"defined\".\n\nDo not keyword-stuff. Write for the hiring manager reading it, not for an ATS parser.\n\n---\n\n## Cover Letter Writing\n\nA cover letter should answer three questions in under 300 words:\n\n1. **Why this company?** Something specific — a product, a technical challenge they have written about, a problem space you care about. Not \"I admire your mission.\"\n2. **Why you?** One or two concrete things from your background that directly match what they need. Link to the specific role, not your full career history.\n3. **Why now?** What is your motivation at this point in your career? One sentence.\n\nFormat: three short paragraphs. No preamble (\"I am writing to apply for...\"). No summary of your CV.\n\nAvoid:\n- Restating your CV in prose form\n- \"I am passionate about...\"\n- Generic company praise (\"a leader in the industry\", \"innovative company\")\n- Going longer than one page\n\n---\n\n## Offer Evaluation\n\nWhen evaluating a job offer, compare across these dimensions:\n\n**Compensation**\n- Base salary: check against market rate for role, level, and location (levels.fyi, Glassdoor, Blind, Comprehensive.io)\n- Equity: current valuation, vesting schedule (4-year with 1-year cliff is standard), dilution risk for early-stage companies\n- Bonus: target percentage vs actual historical payout\n- Total comp = base + expected bonus + annualized equity value\n\n**Role clarity**\n- Scope: what does \"owning\" this role actually mean vs what is already decided?\n- Team: size, structure, who you report to, tenure of the team\n- Growth: what does the next level look like and how long do people typically take to get there?\n\n**Company health**\n- Stage: runway, revenue, growth rate — ask directly if not public\n- Engineering culture signals: PR review process, incident postmortem culture, on-call burden\n- Remote or hybrid reality: written policy vs actual practice\n\n**Red flags in an offer**\n- Pressure to decide in under 48 hours — a reasonable window is one to two weeks\n- Equity with no clear liquidity path for a company that has been private for 10+ years\n- A role described as greenfield that turns out to have 6 months of existing unmaintained code\n\nGet everything in writing before accepting.\n\n---\n\n## Follow-up Emails\n\nAfter an interview, send a follow-up within 24 hours:\n- One sentence thanking them for the time\n- One sentence referencing something specific from the conversation (a problem discussed, a question they asked)\n- One sentence reaffirming interest, if genuine\n\nDo not write multiple paragraphs. Do not restate your qualifications. Do not follow up more than once if there is no reply.\n",{"name":5,"license":15,"description":7,"argument-hint":59},"Optional: the specific task — e.g. \"analyze this JD\", \"tailor my CV\", \"write cover letter\", \"evaluate this offer\"","main","5269f7ea2d6c3a9bfda5ed878b6726cf509121fd","skills\u002Ftechnical-job-search",5340,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot","https:\u002F\u002Fawesome-copilot.github.com\u002F","https:\u002F\u002Fgithub.com\u002Fgithub","https:\u002F\u002Fgithub.com\u002Fabout","How people build software.","2026-11-11 13:41:32",{"source":8,"skillName":5,"commands":71,"prompt":81,"zipAvailable":82},[72,75,78],{"tool":73,"command":74},"npx","npx skills add github\u002Fawesome-copilot --skill technical-job-search",{"tool":76,"command":77},"bunx","bunx skills add github\u002Fawesome-copilot --skill technical-job-search",{"tool":79,"command":80},"pnpm","pnpm dlx skills add github\u002Fawesome-copilot --skill technical-job-search","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Ftechnical-job-search\u002FSKILL.md",true,[84,90,94,98,104,110,114,120,124,128,132,136,140,144,148,152,156],{"path":85,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":88,"sourceHtmlUrl":89},"agents\u002Fanalyzer.md","REFERENCE","参考文档",10376,"https:\u002F\u002Fgithub.com\u002Fhareki\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002F.agents\u002Fskills\u002Fskill-creator\u002Fagents\u002Fanalyzer.md",{"path":91,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":92,"sourceHtmlUrl":93},"agents\u002Fcomparator.md",7287,"https:\u002F\u002Fgithub.com\u002Fhareki\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002F.agents\u002Fskills\u002Fskill-creator\u002Fagents\u002Fcomparator.md",{"path":95,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":96,"sourceHtmlUrl":97},"agents\u002Fgrader.md",9049,"https:\u002F\u002Fgithub.com\u002Fhareki\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002F.agents\u002Fskills\u002Fskill-creator\u002Fagents\u002Fgrader.md",{"path":99,"resourceType":100,"resourceTypeDesc":101,"sizeBytes":102,"sourceHtmlUrl":103},"assets\u002Feval_review.html","ASSET","资产文件",7058,"https:\u002F\u002Fgithub.com\u002Fhareki\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002F.agents\u002Fskills\u002Fskill-creator\u002Fassets\u002Feval_review.html",{"path":105,"resourceType":106,"resourceTypeDesc":107,"sizeBytes":108,"sourceHtmlUrl":109},"eval-viewer\u002Fgenerate_review.py","SCRIPT","脚本",16365,"https:\u002F\u002Fgithub.com\u002Fhareki\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002F.agents\u002Fskills\u002Fskill-creator\u002Feval-viewer\u002Fgenerate_review.py",{"path":111,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":112,"sourceHtmlUrl":113},"eval-viewer\u002Fviewer.html",44998,"https:\u002F\u002Fgithub.com\u002Fhareki\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002F.agents\u002Fskills\u002Fskill-creator\u002Feval-viewer\u002Fviewer.html",{"path":115,"resourceType":116,"resourceTypeDesc":117,"sizeBytes":118,"sourceHtmlUrl":119},"LICENSE.txt","LICENSE","许可证",11345,"https:\u002F\u002Fgithub.com\u002Fhareki\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002F.agents\u002Fskills\u002Fskill-creator\u002FLICENSE.txt",{"path":121,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":122,"sourceHtmlUrl":123},"references\u002Fschemas.md",12061,"https:\u002F\u002Fgithub.com\u002Fhareki\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002F.agents\u002Fskills\u002Fskill-creator\u002Freferences\u002Fschemas.md",{"path":125,"resourceType":106,"resourceTypeDesc":107,"sizeBytes":126,"sourceHtmlUrl":127},"scripts\u002F__init__.py",0,"https:\u002F\u002Fgithub.com\u002Fhareki\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002F.agents\u002Fskills\u002Fskill-creator\u002Fscripts\u002F__init__.py",{"path":129,"resourceType":106,"resourceTypeDesc":107,"sizeBytes":130,"sourceHtmlUrl":131},"scripts\u002Faggregate_benchmark.py",14386,"https:\u002F\u002Fgithub.com\u002Fhareki\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002F.agents\u002Fskills\u002Fskill-creator\u002Fscripts\u002Faggregate_benchmark.py",{"path":133,"resourceType":106,"resourceTypeDesc":107,"sizeBytes":134,"sourceHtmlUrl":135},"scripts\u002Fgenerate_report.py",12847,"https:\u002F\u002Fgithub.com\u002Fhareki\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002F.agents\u002Fskills\u002Fskill-creator\u002Fscripts\u002Fgenerate_report.py",{"path":137,"resourceType":106,"resourceTypeDesc":107,"sizeBytes":138,"sourceHtmlUrl":139},"scripts\u002Fimprove_description.py",11116,"https:\u002F\u002Fgithub.com\u002Fhareki\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002F.agents\u002Fskills\u002Fskill-creator\u002Fscripts\u002Fimprove_description.py",{"path":141,"resourceType":106,"resourceTypeDesc":107,"sizeBytes":142,"sourceHtmlUrl":143},"scripts\u002Fpackage_skill.py",4234,"https:\u002F\u002Fgithub.com\u002Fhareki\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002F.agents\u002Fskills\u002Fskill-creator\u002Fscripts\u002Fpackage_skill.py",{"path":145,"resourceType":106,"resourceTypeDesc":107,"sizeBytes":146,"sourceHtmlUrl":147},"scripts\u002Fquick_validate.py",3972,"https:\u002F\u002Fgithub.com\u002Fhareki\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002F.agents\u002Fskills\u002Fskill-creator\u002Fscripts\u002Fquick_validate.py",{"path":149,"resourceType":106,"resourceTypeDesc":107,"sizeBytes":150,"sourceHtmlUrl":151},"scripts\u002Frun_eval.py",11464,"https:\u002F\u002Fgithub.com\u002Fhareki\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002F.agents\u002Fskills\u002Fskill-creator\u002Fscripts\u002Frun_eval.py",{"path":153,"resourceType":106,"resourceTypeDesc":107,"sizeBytes":154,"sourceHtmlUrl":155},"scripts\u002Frun_loop.py",13605,"https:\u002F\u002Fgithub.com\u002Fhareki\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002F.agents\u002Fskills\u002Fskill-creator\u002Fscripts\u002Frun_loop.py",{"path":157,"resourceType":106,"resourceTypeDesc":107,"sizeBytes":158,"sourceHtmlUrl":159},"scripts\u002Futils.py",1661,"https:\u002F\u002Fgithub.com\u002Fhareki\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002F.agents\u002Fskills\u002Fskill-creator\u002Fscripts\u002Futils.py",[161,192,220,248,281,298],{"skillNo":162,"name":163,"nameZh":6,"description":164,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":165,"categories":166,"keywords":173,"publishedAt":54},"01M70KXZNX9ES38N2A8M58ZZMZ","supabase-rls-policies","Write, review, and test Supabase Row Level Security (RLS) policies so that one user cannot read or change another user's rows. Use when creating or changing tables, policies, views, or security definer functions in a Supabase project, when reviewing a migration that touches RLS, or when asked to prove user isolation with pgTAP tests that sign in as two users.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fsupabase-rls-policies\u002FSKILL.md",[167,170],{"categoryNo":168,"categoryName":169,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":171,"categoryName":172,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[174,175,176,177,178,38,179,180,181,48,182,183,184,185,186,187,188,189,190,191],"supabase","rls","supabase rls","supabase rls policies","project","review","change","read","security","isolation","tables","as","tests","prove","use","users","functions","with",{"skillNo":193,"name":194,"nameZh":6,"description":195,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":196,"categories":197,"keywords":199,"publishedAt":54},"01M70KWA5YWXDV6V8DZ19E3T2Y","skill-distribution-audit","Audit a skill collection before release or investigate installer omissions, archived\u002Ftemplate leakage, duplicate identities, and manifest drift. Reconcile the intended public source set, distribution manifest, and actual discovery output for a specified consumer version. Includes a deterministic set-comparison helper.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fskill-distribution-audit\u002FSKILL.md",[198],{"categoryNo":171,"categoryName":172,"taxonomyType":21,"taxonomyTypeDesc":22},[200,201,202,203,204,205,206,207,208,209,210,211,212,213,214,215,216,217,218,219],"distribution","skill distribution audit","audit","SET","deterministic","installer","for","discovery","comparison","helper","manifest","version","collection","drift","output","investigate","duplicate","template","release","reconcile",{"skillNo":221,"name":222,"nameZh":6,"description":223,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":224,"sourceHtmlUrl":225,"categories":226,"keywords":230,"publishedAt":54},"01M70KCJPFVW7PPQ49CC5R8JGK","logicapps-custom-code-net10-migration","Migrate Azure Logic Apps Standard local-function custom-code projects from .NET 8 to .NET 10. Use for legacy Logic Apps custom-code workspace upgrades, project\u002Fpackage configuration, custom-worker settings, publication, and integrated VS Code debugging. Not for ordinary .NET applications, standalone Azure Functions, Consumption workflows, or cloud deployment.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Flogicapps-custom-code-net10-migration\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Flogicapps-custom-code-net10-migration\u002FSKILL.md",[227],{"categoryNo":228,"categoryName":229,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师",[231,232,233,234,235,236,206,178,237,238,239,240,241,242,243,188,244,245,246,247],"custom","code","logicapps custom code net10 migration","migration","projects","standalone","deployment","applications","local","azure","worker","upgrades","package","apps","Legacy","debugging","workflows",{"skillNo":249,"name":250,"nameZh":6,"description":251,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":252,"sourceHtmlUrl":253,"categories":254,"keywords":259,"publishedAt":54},"01M6AEBN37RQMXJ3298PEY7PG1","winmd-api-search","Find and explore Windows desktop APIs. Use when building features that need platform capabilities — camera, file access, notifications, UI controls, AI\u002FML, sensors, networking, etc. Discovers the right API for a task and retrieves full type details (methods, properties, events, enumeration values).","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fwinmd-api-search\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fwinmd-api-search\u002FSKILL.md",[255,258],{"categoryNo":256,"categoryName":257,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":228,"categoryName":229,"taxonomyType":26,"taxonomyTypeDesc":27},[260,32,261,262,263,264,265,266,267,268,269,270,271,272,273,38,274,275,276,277,278,206,279,280],"winmd api search","api","windows","desktop","file access","enumeration","ui","ml","file","networking","capabilities","notifications","explore","access","features","full","camera","events","platform","methods","controls",{"skillNo":282,"name":283,"nameZh":6,"description":284,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":285,"licenseFileUrl":286,"sourceHtmlUrl":287,"categories":288,"keywords":294,"publishedAt":54},"01M6AE571R3SC1ZGE202B3NB5S","resemble-detect","Deepfake detection and media safety — detect AI-generated audio, images, video, and text, trace synthesis sources, apply watermarks, verify speaker identity, and analyze media intelligence using Resemble AI","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fresemble-detect\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fresemble-detect\u002FSKILL.md",[289,290,293],{"categoryNo":256,"categoryName":257,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":291,"categoryName":292,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":171,"categoryName":172,"taxonomyType":21,"taxonomyTypeDesc":22},[295,203,268,296,297],"resemble detect","https","identity",{"skillNo":299,"name":300,"nameZh":6,"description":301,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":285,"licenseFileUrl":302,"sourceHtmlUrl":303,"categories":304,"keywords":309,"publishedAt":54},"01M6AE30BSK2HCY4TQQ22Z8JRD","quality-playbook","Run a complete quality engineering audit on any codebase. Derives behavioral requirements from the code, generates spec-traced functional tests, runs a three-pass code review with regression tests, executes a multi-model spec audit (Council of Three), and produces a consolidated bug report with TDD-verified patches. Finds the 35% of real defects that structural code review alone cannot catch. Works with any language. Trigger on 'quality playbook', 'spec audit', 'Council of Three', 'fitness-to-purpose', or 'coverage theater'.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fquality-playbook\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fquality-playbook\u002FSKILL.md",[305,308],{"categoryNo":306,"categoryName":307,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":171,"categoryName":172,"taxonomyType":21,"taxonomyTypeDesc":22},[310,311,312,313,232,179,9,202,314,315,296,316,317,318,319,320,321,322,323,324,325,326,186,327,328,329,330],"playbook","quality playbook","quality","code review","tdd","run","report","spec","bug report","council","engineering","functional","spec audit","bug","verified","multi-model","three","coverage","model","regression","structural"]