[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6PEQRXMMDS6TXVSCWRAZ9FH":3,"skill-same:01M6PEQRXMMDS6TXVSCWRAZ9FH":70},{"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":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":52,"repositoryHtmlUrl":53,"repositoryHomepageUrl":6,"ownerHtmlUrl":54,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":55,"install":56,"resources":69},"01M6PEQRXMMDS6TXVSCWRAZ9FH","detecting-infrastructure-drift",null,"This skill enables Claude to detect infrastructure drift from a desired state. It uses the `drift-detect` command to identify discrepancies between the current infrastructure configuration and the intended configuration, as defined in infrastructure-as-code tools like Terraform. Use this skill when the user asks to check for infrastructure drift, identify configuration changes, or ensure that the current infrastructure matches the desired state. It is particularly useful in DevOps workflows for maintaining infrastructure consistency and preventing configuration errors. Trigger this skill when the user mentions \"drift detection,\" \"infrastructure changes,\" \"configuration drift,\" or requests a \"drift report.\"","sandraschi\u002Fdocumentation-mcp","sandraschi","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F34750307?v=4","01M6C42H9WE5EC9CK3N5RGZP8S","Sandra Schipal","01M6PE1X2FZP8KR5GANPPFTHA8",2,"MIT","https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp\u002Fblob\u002Fmaster\u002Fdocs\u002Fnot-mcp-related\u002Fclaude-skills\u002Ftemp\u002Fcode-plugins\u002Fplugins\u002Fdevops\u002Finfrastructure-drift-detector\u002Fskills\u002Finfrastructure-drift-detector\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"infrastructure","detecting infrastructure drift","drift","detecting","drift detection","workflows","changes","for","consistency","infrastructure-as","errors","detect","trigger","as","use","code tools","check","infrastructure-as-code","state","code","2026-11-10 10:12:30",false,"---\nname: detecting-infrastructure-drift\ndescription: |\n  This skill enables Claude to detect infrastructure drift from a desired state. It uses the `drift-detect` command to identify discrepancies between the current infrastructure configuration and the intended configuration, as defined in infrastructure-as-code tools like Terraform. Use this skill when the user asks to check for infrastructure drift, identify configuration changes, or ensure that the current infrastructure matches the desired state. It is particularly useful in DevOps workflows for maintaining infrastructure consistency and preventing configuration errors. Trigger this skill when the user mentions \"drift detection,\" \"infrastructure changes,\" \"configuration drift,\" or requests a \"drift report.\"\n---\n\n## Overview\n\nThis skill empowers Claude to identify and report on deviations between the current state of your infrastructure and its defined desired state. By leveraging the `drift-detect` command, it provides insights into configuration inconsistencies, helping maintain infrastructure integrity and prevent unexpected issues.\n\n## How It Works\n\n1. **Invocation**: The user requests drift detection.\n2. **Drift Analysis**: Claude executes the `drift-detect` command.\n3. **Report Generation**: The command analyzes the infrastructure and identifies any deviations from the defined configuration.\n4. **Result Presentation**: Claude presents a report detailing the detected drift, including affected resources and configuration differences.\n\n## When to Use This Skill\n\nThis skill activates when you need to:\n- Identify infrastructure drift in your environment.\n- Ensure that your infrastructure configuration matches the desired state.\n- Generate a report detailing discrepancies between the current and desired infrastructure configurations.\n\n## Examples\n\n### Example 1: Checking for Infrastructure Drift\n\nUser request: \"Check for infrastructure drift in my production environment.\"\n\nThe skill will:\n1. Execute the `drift-detect` command.\n2. Present a report detailing any detected drift, including resource changes and configuration differences.\n\n### Example 2: Identifying Configuration Changes\n\nUser request: \"Are there any configuration changes that haven't been applied to my infrastructure?\"\n\nThe skill will:\n1. Execute the `drift-detect` command.\n2. Provide a summary of configuration changes that are present in the desired state but not reflected in the current infrastructure.\n\n## Best Practices\n\n- **Regular Monitoring**: Schedule regular drift detection checks to proactively identify and address configuration inconsistencies.\n- **Version Control**: Ensure your infrastructure-as-code configurations are version-controlled to track changes and facilitate rollbacks.\n- **Automated Remediation**: Implement automated remediation workflows to automatically correct detected drift and maintain infrastructure consistency.\n\n## Integration\n\nThis skill can be integrated with other DevOps tools and plugins to automate infrastructure management workflows. For example, it can be used in conjunction with configuration management tools like Ansible or Puppet to automatically remediate detected drift. It also complements infrastructure-as-code tools like Terraform by providing a mechanism for verifying that the deployed infrastructure matches the defined configuration.\n","## Overview\n\nThis skill empowers Claude to identify and report on deviations between the current state of your infrastructure and its defined desired state. By leveraging the `drift-detect` command, it provides insights into configuration inconsistencies, helping maintain infrastructure integrity and prevent unexpected issues.\n\n## How It Works\n\n1. **Invocation**: The user requests drift detection.\n2. **Drift Analysis**: Claude executes the `drift-detect` command.\n3. **Report Generation**: The command analyzes the infrastructure and identifies any deviations from the defined configuration.\n4. **Result Presentation**: Claude presents a report detailing the detected drift, including affected resources and configuration differences.\n\n## When to Use This Skill\n\nThis skill activates when you need to:\n- Identify infrastructure drift in your environment.\n- Ensure that your infrastructure configuration matches the desired state.\n- Generate a report detailing discrepancies between the current and desired infrastructure configurations.\n\n## Examples\n\n### Example 1: Checking for Infrastructure Drift\n\nUser request: \"Check for infrastructure drift in my production environment.\"\n\nThe skill will:\n1. Execute the `drift-detect` command.\n2. Present a report detailing any detected drift, including resource changes and configuration differences.\n\n### Example 2: Identifying Configuration Changes\n\nUser request: \"Are there any configuration changes that haven't been applied to my infrastructure?\"\n\nThe skill will:\n1. Execute the `drift-detect` command.\n2. Provide a summary of configuration changes that are present in the desired state but not reflected in the current infrastructure.\n\n## Best Practices\n\n- **Regular Monitoring**: Schedule regular drift detection checks to proactively identify and address configuration inconsistencies.\n- **Version Control**: Ensure your infrastructure-as-code configurations are version-controlled to track changes and facilitate rollbacks.\n- **Automated Remediation**: Implement automated remediation workflows to automatically correct detected drift and maintain infrastructure consistency.\n\n## Integration\n\nThis skill can be integrated with other DevOps tools and plugins to automate infrastructure management workflows. For example, it can be used in conjunction with configuration management tools like Ansible or Puppet to automatically remediate detected drift. It also complements infrastructure-as-code tools like Terraform by providing a mechanism for verifying that the deployed infrastructure matches the defined configuration.\n",{"name":5,"description":7},"master","be156301b65e301887f327d08190ed4f17ba08d2","docs\u002Fnot-mcp-related\u002Fclaude-skills\u002Ftemp\u002Fcode-plugins\u002Fplugins\u002Fdevops\u002Finfrastructure-drift-detector\u002Fskills\u002Finfrastructure-drift-detector",0,"https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp","https:\u002F\u002Fgithub.com\u002Fsandraschi","2026-11-09 11:03:27",{"source":8,"skillName":5,"commands":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add sandraschi\u002Fdocumentation-mcp --skill detecting-infrastructure-drift",{"tool":62,"command":63},"bunx","bunx skills add sandraschi\u002Fdocumentation-mcp --skill detecting-infrastructure-drift",{"tool":65,"command":66},"pnpm","pnpm dlx skills add sandraschi\u002Fdocumentation-mcp --skill detecting-infrastructure-drift","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp\u002Fblob\u002Fmaster\u002Fdocs\u002Fnot-mcp-related\u002Fclaude-skills\u002Ftemp\u002Fcode-plugins\u002Fplugins\u002Fdevops\u002Finfrastructure-drift-detector\u002Fskills\u002Finfrastructure-drift-detector\u002FSKILL.md",true,[],[71,93,119,129,153,178],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":81,"publishedAt":44},"01M6PFAWAHEJJCKKVNXEWNK87W","Docs Research","Use MCP Central Docs server to search, ask, and retrieve documentation (FastMCP, standards, packaging).","https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp\u002Fblob\u002Fmaster\u002Fsrc\u002Fdocs_mcp\u002Fskills\u002Fdocs-research\u002FSKILL.md",[77,80],{"categoryNo":78,"categoryName":79,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[82,83,84,85,38,86,87,88,89,90,91,92],"docs research","docs","research","standards","packaging","ask","server","search","fastmcp","documentation","MCP",{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":44},"01M6PFAN4DAENMY574Q7Q3CB3H","wrappee-drift","Read-only, single-repo audit of a repo's tool coverage against the software it wraps (its current real API\u002Fdocs, not training-data memory) and against comparable\u002Fcompeting wrappers. Trigger when the user says \"wrappee drift\" followed by a repo name, \"capability audit\" followed by a repo name, or asks whether a repo is missing features the wrapped software or a competitor now has. Always scoped to one named repo per invocation -- never trigger this fleet-wide or unprompted; that is explicitly against the SOP. Do NOT trigger for internal fleet-standard compliance (that is drift-scan) or strategic worth\u002Farchive decisions (that is quality-check) -- this is specifically about the gap between the repo's tool list and the wrapped software's\u002Fcompetitors' actual current capabilities.","https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp\u002Fblob\u002Fmaster\u002Fdocs\u002Fskills\u002Fwrappee-drift\u002FSKILL.md",[],[26,100,101,102,103,104,105,106,107,108,109,110,111,112,113,114,115,116,117,118],"wrappee drift","api","data","audit","capabilities","training","memory","features","repo audit","competitors","fleet","now","software","tool list","only","never","coverage","list","read",{"skillNo":120,"name":121,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":128,"publishedAt":44},"01M6PFADA3X031SK3W3T6X0N6H","modules","https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp\u002Fblob\u002Fmaster\u002Fdocs\u002Fskills\u002Fwindsurf-mcp-standards\u002Fmodules\u002FSKILL.md",[124,127],{"categoryNo":125,"categoryName":126,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[121],{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":133,"categories":134,"keywords":139,"publishedAt":44},"01M6PFA8YA029N68TW0X31FB1W","mcp-standards","Use when developing MCP servers to access comprehensive standards for scaffolding, packaging, sampling, documentation, testing, error handling, monitoring, and CI\u002FCD workflows.","https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp\u002Fblob\u002Fmaster\u002Fdocs\u002Fskills\u002Fwindsurf-mcp-standards\u002FSKILL.md",[135,138],{"categoryNo":136,"categoryName":137,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[140,92,85,38,141,142,143,144,145,146,31,147,148,149,150,151,91,29,152,86],"mcp standards","monitoring","sampling","scaffolding","servers","cd","error","CI\u002FCD","access","ci","mcp servers","error handling","testing",{"skillNo":154,"name":155,"nameZh":6,"description":156,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":157,"categories":158,"keywords":161,"publishedAt":44},"01M6PFA1XX344WX57B0DJZY94Q","webapp-cua-test","Run the pre-Tauri CUA click-through test (real browser, dev stack, OCR \"Connected\" wait, sidebar nav walk) for a fleet MCP server repo under D:\\Dev\\repos. Trigger when the user says \"cua webapp test\" or \"webapp clickthrough\" followed by a repo name, asks for an e2e click-through of a webapp, or asks whether a webapp boots and connects in a real browser. Not for the installed NSIS app (that is the nsis-build skill \u002F cua-nsis-test) and not for DOM assertions (Playwright), and not for hunting fake data or dead buttons (fakefind).","https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp\u002Fblob\u002Fmaster\u002Fdocs\u002Fskills\u002Fwebapp-cua-test\u002FSKILL.md",[159,160],{"categoryNo":136,"categoryName":137,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[162,163,164,165,166,92,167,168,169,31,36,170,171,172,173,174,175,176,88,177],"webapp","test","webapp cua test","playwright","mcp server","dev","dom","assertions","click","app","tauri","repo","stack","e2e","ocr","browser",{"skillNo":179,"name":180,"nameZh":6,"description":181,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":182,"categories":183,"keywords":185,"publishedAt":44},"01M6PF9WYF6NWJR7WVN38TT0WH","ship","Final release gate for a fleet MCP server repo under D:\\Dev\\repos -- run all quality gates, build the release artifact, verify it, commit, push, and cut a GitHub release. Trigger this whenever the user says \"ship it\", \"ship\" followed by a repo name, \"release\" followed by a repo name, or asks to finalize and publish work that's already been done in a repo. This is the terminal step after assfix\u002Fnsis-build, not a substitute for them -- if the repo hasn't been assessed recently, say so before shipping rather than shipping blind.","https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp\u002Fblob\u002Fmaster\u002Fdocs\u002Fskills\u002Fship\u002FSKILL.md",[184],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[180,173,31,36,186,187,188,189,190,191,192,88,193,167,194,195,196,166,197,92],"gates","ship it","artifact","done","say","work","publish","push","shipping","quality gates","commit","github"]