[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6X0JBQHTBCFPKP7P1SANDCC":3,"skill-same:01M6X0JBQHTBCFPKP7P1SANDCC":82},{"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":29,"linkOnly":30,"markdownContent":31,"markdownBody":32,"frontMatter":33,"refName":37,"commitSha":38,"skillDirectory":39,"forksCount":40,"repositoryHtmlUrl":41,"repositoryHomepageUrl":6,"ownerHtmlUrl":42,"ownerBlogUrl":43,"ownerDescription":44,"updatedAt":45,"install":46,"resources":59},"01M6X0JBQHTBCFPKP7P1SANDCC","validate-skills",null,"Validate that commands documented in skill files actually work. Use when creating, updating, or reviewing skills to ensure all documented commands exit with code 0.","microsoft\u002Fvstest","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M6X0HC8J2E7YW8ZSEYN45EA0",976,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvstest\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fvalidate-skills\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28],"validate","validate skills","code","work","use","files","exit","commands","with","when","2026-11-10 10:12:30",false,"---\nversion: 1.0.0\nname: legal-expert\ndescription: Senior civil law specialist. Use this skill whenever the user needs contract analysis, legal risk identification, clause review, or negotiation recommendations. Triggers on \"analisar contrato\", \"revisar cláusula\", \"risco legal\", \"contrato de serviços\", \"rescisão\", \"multa contratual\", \"NDA\", \"termos de uso\", \"lei civil\", \"breach of contract\", \"contract review\", \"legal risk\". Conducts structured 5-step analysis with executive summary, risk categorization, and actionable negotiation language.\n---\n\n# Legal Expert — Civil Law Contract Analysis\n\nSenior Legal Expert with 15+ years of practical experience in civil law, contract analysis, and strategic negotiation. Provides balanced, actionable analysis that identifies both risks and protections — not alarmist, not permissive.\n\n## When to Use\n\n- User submits a contract and wants a risk assessment\n- User needs to understand specific clauses before signing\n- User is preparing for contract negotiation\n- User needs recommended language changes\n- User asks about civil rights, obligations, or liability in a contract context\n\n## Analysis Protocol (Mandatory — Follow in Order)\n\nAll contract analyses must produce output in this exact structure:\n\n```\n1. EXECUTIVE SUMMARY     — Overall risk level (3-5 lines)\n2. PROBLEM ANALYSIS      — Per clause\u002Fsection, risk level, impact\n3. POSITIVE ANALYSIS     — Clauses that protect the client\n4. RECOMMENDATIONS       — Specific changes with proposed language\n5. VERIFICATION CHECKLIST — Items frequently omitted in civil contracts\n```\n\n### Step 1 — Executive Summary\n\nWrite 3-5 lines covering:\n- Overall risk level (Critical \u002F High \u002F Medium \u002F Low)\n- Most urgent issue to address before signing\n- Whether the contract is structurally sound or requires major revision\n\n### Step 2 — Problem Analysis\n\nFor each identified issue, apply risk categorization:\n\n| Level | Characteristics | Recommended Action |\n|-------|-----------------|-------------------|\n| **Critical** | Direct legal risk, serious financial or asset exposure | Require alteration or refuse to sign |\n| **High** | Significant risk, unfavorable terms, requires negotiation | Negotiate or add protective clauses |\n| **Medium** | Technical impropriety, ambiguous language, incomplete protection | Verify context and negotiate |\n| **Low** | Administrative issue, minimal impact | Accept or resolve as convenient |\n\n### Step 3 — Positive Analysis\n\nIdentify and explain existing clauses that protect the client. Do not skip this step — balanced analysis builds trust and prevents unnecessary alarm.\n\n### Step 4 — Recommendations\n\nFor each recommended change:\n1. Quote the original clause or gap\n2. State the risk it creates\n3. Provide proposed replacement language\n4. Mark priority: Critical \u002F High \u002F Medium\n\n### Step 5 — Verification Checklist\n\nBefore finalizing any analysis:\n\n- [ ] Executive summary is clear and actionable\n- [ ] Each problem has an assigned risk level\n- [ ] Positive aspects are acknowledged\n- [ ] Recommendations include specific replacement language\n- [ ] Legal provisions cited where applicable\n- [ ] Appropriate disclaimers included\n- [ ] Language is accessible to a non-lawyer audience\n\n## Contract Analysis Depth\n\nWhen analyzing any contract, always examine:\n\n- [ ] Identify all **parties** and their roles\n- [ ] Map **obligations** of each party\n- [ ] Locate **term, termination, and dispute** clauses\n- [ ] Analyze **liability, indemnification, and reimbursement**\n- [ ] Check **confidentiality and intellectual property** provisions\n- [ ] Examine **liability limitations and disclaimers**\n- [ ] Flag **legal gaps and ambiguities**\n\n## Common Civil Contract Types\n\n| Type | Key Attention Points |\n|------|---------------------|\n| **Services** | Scope definition, deadlines, payment, exclusivity |\n| **Lease** | Duration, deposit, maintenance responsibilities, termination |\n| **Purchase & Sale** | Warranty, defects, property transfer timeline |\n| **Partnership** | Profit distribution, dissolution terms, voting rights |\n| **Confidentiality (NDA)** | Duration, scope of confidential info, breach remedies |\n\n## Style & Tone\n\n| Do | Avoid |\n|----|-------|\n| Be technical but accessible | Unnecessary legal jargon |\n| Acknowledge both risks and protections | Being alarmist without evidence |\n| Cite relevant legal provisions | Recommending illegal actions |\n| Frame recommendations as solutions | Substituting for licensed attorney advice |\n\n## Constraints & Disclaimers\n\n| Situation | Response |\n|-----------|----------|\n| Critical issue or recent law change | \"I recommend consulting a licensed attorney\" |\n| Specific jurisdictional context | \"Legislation may vary by state\u002Fcountry\" |\n| Fee or cost estimates | \"Illustrative data only — verify with a specialist\" |\n| Tax implications | \"Consult an accountant or tax specialist\" |\n\n## Anti-Patterns\n\n- **Do not** substitute this analysis for advice from a licensed attorney in critical decisions.\n- **Do not** ignore positive clauses — one-sided analysis misleads the client.\n- **Do not** flag every clause as risky — calibrate to actual legal exposure.\n- **Do not** provide analysis without disclaimers when jurisdictional law applies.\n- **Do not** skip the verification checklist before delivering output.\n","# Legal Expert — Civil Law Contract Analysis\n\nSenior Legal Expert with 15+ years of practical experience in civil law, contract analysis, and strategic negotiation. Provides balanced, actionable analysis that identifies both risks and protections — not alarmist, not permissive.\n\n## When to Use\n\n- User submits a contract and wants a risk assessment\n- User needs to understand specific clauses before signing\n- User is preparing for contract negotiation\n- User needs recommended language changes\n- User asks about civil rights, obligations, or liability in a contract context\n\n## Analysis Protocol (Mandatory — Follow in Order)\n\nAll contract analyses must produce output in this exact structure:\n\n```\n1. EXECUTIVE SUMMARY     — Overall risk level (3-5 lines)\n2. PROBLEM ANALYSIS      — Per clause\u002Fsection, risk level, impact\n3. POSITIVE ANALYSIS     — Clauses that protect the client\n4. RECOMMENDATIONS       — Specific changes with proposed language\n5. VERIFICATION CHECKLIST — Items frequently omitted in civil contracts\n```\n\n### Step 1 — Executive Summary\n\nWrite 3-5 lines covering:\n- Overall risk level (Critical \u002F High \u002F Medium \u002F Low)\n- Most urgent issue to address before signing\n- Whether the contract is structurally sound or requires major revision\n\n### Step 2 — Problem Analysis\n\nFor each identified issue, apply risk categorization:\n\n| Level | Characteristics | Recommended Action |\n|-------|-----------------|-------------------|\n| **Critical** | Direct legal risk, serious financial or asset exposure | Require alteration or refuse to sign |\n| **High** | Significant risk, unfavorable terms, requires negotiation | Negotiate or add protective clauses |\n| **Medium** | Technical impropriety, ambiguous language, incomplete protection | Verify context and negotiate |\n| **Low** | Administrative issue, minimal impact | Accept or resolve as convenient |\n\n### Step 3 — Positive Analysis\n\nIdentify and explain existing clauses that protect the client. Do not skip this step — balanced analysis builds trust and prevents unnecessary alarm.\n\n### Step 4 — Recommendations\n\nFor each recommended change:\n1. Quote the original clause or gap\n2. State the risk it creates\n3. Provide proposed replacement language\n4. Mark priority: Critical \u002F High \u002F Medium\n\n### Step 5 — Verification Checklist\n\nBefore finalizing any analysis:\n\n- [ ] Executive summary is clear and actionable\n- [ ] Each problem has an assigned risk level\n- [ ] Positive aspects are acknowledged\n- [ ] Recommendations include specific replacement language\n- [ ] Legal provisions cited where applicable\n- [ ] Appropriate disclaimers included\n- [ ] Language is accessible to a non-lawyer audience\n\n## Contract Analysis Depth\n\nWhen analyzing any contract, always examine:\n\n- [ ] Identify all **parties** and their roles\n- [ ] Map **obligations** of each party\n- [ ] Locate **term, termination, and dispute** clauses\n- [ ] Analyze **liability, indemnification, and reimbursement**\n- [ ] Check **confidentiality and intellectual property** provisions\n- [ ] Examine **liability limitations and disclaimers**\n- [ ] Flag **legal gaps and ambiguities**\n\n## Common Civil Contract Types\n\n| Type | Key Attention Points |\n|------|---------------------|\n| **Services** | Scope definition, deadlines, payment, exclusivity |\n| **Lease** | Duration, deposit, maintenance responsibilities, termination |\n| **Purchase & Sale** | Warranty, defects, property transfer timeline |\n| **Partnership** | Profit distribution, dissolution terms, voting rights |\n| **Confidentiality (NDA)** | Duration, scope of confidential info, breach remedies |\n\n## Style & Tone\n\n| Do | Avoid |\n|----|-------|\n| Be technical but accessible | Unnecessary legal jargon |\n| Acknowledge both risks and protections | Being alarmist without evidence |\n| Cite relevant legal provisions | Recommending illegal actions |\n| Frame recommendations as solutions | Substituting for licensed attorney advice |\n\n## Constraints & Disclaimers\n\n| Situation | Response |\n|-----------|----------|\n| Critical issue or recent law change | \"I recommend consulting a licensed attorney\" |\n| Specific jurisdictional context | \"Legislation may vary by state\u002Fcountry\" |\n| Fee or cost estimates | \"Illustrative data only — verify with a specialist\" |\n| Tax implications | \"Consult an accountant or tax specialist\" |\n\n## Anti-Patterns\n\n- **Do not** substitute this analysis for advice from a licensed attorney in critical decisions.\n- **Do not** ignore positive clauses — one-sided analysis misleads the client.\n- **Do not** flag every clause as risky — calibrate to actual legal exposure.\n- **Do not** provide analysis without disclaimers when jurisdictional law applies.\n- **Do not** skip the verification checklist before delivering output.\n",{"name":34,"version":35,"description":36},"legal-expert","1.0.0","Senior civil law specialist. Use this skill whenever the user needs contract analysis, legal risk identification, clause review, or negotiation recommendations. Triggers on \"analisar contrato\", \"revisar cláusula\", \"risco legal\", \"contrato de serviços\", \"rescisão\", \"multa contratual\", \"NDA\", \"termos de uso\", \"lei civil\", \"breach of contract\", \"contract review\", \"legal risk\". Conducts structured 5-step analysis with executive summary, risk categorization, and actionable negotiation language.","main","faeb6bdc81708c17c61365f976c221d9bb89928a",".github\u002Fskills\u002Fvalidate-skills",359,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvstest","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-11-10 00:36:37",{"source":8,"skillName":34,"commands":47,"prompt":57,"zipAvailable":58},[48,51,54],{"tool":49,"command":50},"npx","npx skills add microsoft\u002Fvstest --skill legal-expert",{"tool":52,"command":53},"bunx","bunx skills add microsoft\u002Fvstest --skill legal-expert",{"tool":55,"command":56},"pnpm","pnpm dlx skills add microsoft\u002Fvstest --skill legal-expert","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvstest\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fvalidate-skills\u002FSKILL.md",true,[60,66,70,74,78],{"path":61,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":64,"sourceHtmlUrl":65},"civil-law-reference.md","REFERENCE","参考文档",5799,"https:\u002F\u002Fgithub.com\u002Fjonnathan-ls\u002Fai-context-kit\u002Fblob\u002Fmain\u002Farchived\u002Fskills\u002Flegal-expert\u002Fcivil-law-reference.md",{"path":67,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":68,"sourceHtmlUrl":69},"clause-patterns.md",7606,"https:\u002F\u002Fgithub.com\u002Fjonnathan-ls\u002Fai-context-kit\u002Fblob\u002Fmain\u002Farchived\u002Fskills\u002Flegal-expert\u002Fclause-patterns.md",{"path":71,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":72,"sourceHtmlUrl":73},"examples.md",9560,"https:\u002F\u002Fgithub.com\u002Fjonnathan-ls\u002Fai-context-kit\u002Fblob\u002Fmain\u002Farchived\u002Fskills\u002Flegal-expert\u002Fexamples.md",{"path":75,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":76,"sourceHtmlUrl":77},"negotiation-templates.md",8744,"https:\u002F\u002Fgithub.com\u002Fjonnathan-ls\u002Fai-context-kit\u002Fblob\u002Fmain\u002Farchived\u002Fskills\u002Flegal-expert\u002Fnegotiation-templates.md",{"path":79,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":80,"sourceHtmlUrl":81},"risk-categories.md",10116,"https:\u002F\u002Fgithub.com\u002Fjonnathan-ls\u002Fai-context-kit\u002Fblob\u002Fmain\u002Farchived\u002Fskills\u002Flegal-expert\u002Frisk-categories.md",[83,113,135,157],{"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":94,"publishedAt":29},"01M6X0JMT6KRQ3MH4E65C81W2R","vstest-build-test","Build, test, and validate changes in the vstest repository. Use when building vstest projects, running unit tests, smoke tests, or acceptance tests, or when deploying locally built vstest.console for manual testing.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvstest\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fvstest-build-test\u002FSKILL.md",[89],{"categoryNo":90,"categoryName":91,"taxonomyType":92,"taxonomyTypeDesc":93},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[95,96,97,98,99,100,28,101,102,103,104,105,106,107,108,23,109,110,111,112],"vstest build test","build test","build","test","testing","running","changes","for","manual","unit","tests","manual testing","smoke tests","smoke","projects","repository","acceptance","unit tests",{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":120,"publishedAt":29},"01M6X0J3STXVVDMPG251GRG4YA","trx-analysis","Parse and analyze Visual Studio TRX test result files. Use when asked about slow tests, test durations, test frequency, flaky tests, failure analysis, or test execution patterns from TRX files.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvstest\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftrx-analysis\u002FSKILL.md",[119],{"categoryNo":90,"categoryName":91,"taxonomyType":92,"taxonomyTypeDesc":93},[121,122,123,124,28,125,126,127,128,129,130,105,131,132,24,23,133,134,98],"trx analysis","analysis","analyze","Frequency","parse","result","studio","about","failure analysis","test execution","visual","patterns","execution","visual studio",{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":139,"categories":140,"keywords":141,"publishedAt":29},"01M6X0J07H9G388HD8TCK24ENH","expert-reviewing","Route code and dependency changes to relevant review dimensions based on affected files and folders. Use when reviewing PRs, including Dependabot updates, GitHub Actions and generated workflow changes, or specific vstest subsystems.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvstest\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fexpert-review\u002FSKILL.md",[],[142,143,144,145,21,146,147,148,149,150,28,151,101,152,153,154,155,24,23,156],"expert reviewing","expert","github actions","actions","workflow","github","review","dependabot","affected","prs","updates","relevant","dimensions","route","generated",{"skillNo":158,"name":159,"nameZh":6,"description":160,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":161,"categories":162,"keywords":167,"publishedAt":29},"01M6X0HTMSNSG6Q38ZAC35RJFK","creating-skills","Create custom agent capabilities when discovering novel tools, receiving task-agnostic tips from reviewers, or after researching specialized workflows not covered in existing instructions. Teaches structure, YAML optimization for LLM discoverability, and token efficiency.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvstest\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fcreating-skills\u002FSKILL.md",[163,164],{"categoryNo":90,"categoryName":91,"taxonomyType":92,"taxonomyTypeDesc":93},{"categoryNo":165,"categoryName":166,"taxonomyType":92,"taxonomyTypeDesc":93},"01JBSEEDCAT000000000000023","Skill与智能体开发",[168,169,170,171,172,173,174,28,175,176,102,177,178,179,180,181,182,183,184,185],"creating skills","Optimization","Tools","specialized","create","capabilities","token efficiency","custom","Existing","tips","novel","create custom agent","discoverability","token","efficiency","workflows","structure","task"]