[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6PERBQNQ0F40HFRNFQJ4WD4":3,"skill-same:01M6PERBQNQ0F40HFRNFQJ4WD4":91},{"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":26,"publishedAt":47,"linkOnly":48,"markdownContent":49,"markdownBody":50,"frontMatter":51,"refName":52,"commitSha":53,"skillDirectory":54,"forksCount":55,"repositoryHtmlUrl":56,"repositoryHomepageUrl":6,"ownerHtmlUrl":57,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":58,"install":59,"resources":72},"01M6PERBQNQ0F40HFRNFQJ4WD4","deploying-monitoring-stacks",null,"This skill deploys monitoring stacks, including Prometheus, Grafana, and Datadog. It is used when the user needs to set up or configure monitoring infrastructure for applications or systems. The skill generates production-ready configurations, implements best practices, and supports multi-platform deployments. Use this when the user explicitly requests to deploy a monitoring stack, or mentions Prometheus, Grafana, or Datadog in the context of infrastructure setup.","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\u002Fmonitoring-stack-deployer\u002Fskills\u002Fmonitoring-stack-deployer\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46],"monitoring","Deploying Monitoring Stacks","ready","for","production-ready","requests","multi","systems","platform","deployments","up","best practices","use","stack","configure","datadog","applications","SET","grafana","prometheus","2026-11-10 10:12:30",false,"---\nname: deploying-monitoring-stacks\ndescription: |\n  This skill deploys monitoring stacks, including Prometheus, Grafana, and Datadog. It is used when the user needs to set up or configure monitoring infrastructure for applications or systems. The skill generates production-ready configurations, implements best practices, and supports multi-platform deployments. Use this when the user explicitly requests to deploy a monitoring stack, or mentions Prometheus, Grafana, or Datadog in the context of infrastructure setup.\n---\n\n## Overview\n\nThis skill empowers Claude to automate the deployment of comprehensive monitoring solutions. It simplifies the setup of Prometheus, Grafana, and Datadog, ensuring best practices and production-ready configurations.\n\n## How It Works\n\n1. **Configuration Gathering**: Claude gathers the specific requirements for the monitoring stack, including the desired platform and tools.\n2. **Stack Generation**: Based on the requirements, Claude generates the necessary configuration files and deployment scripts for the selected monitoring stack.\n3. **Deployment Instructions**: Claude provides clear, step-by-step instructions for deploying the generated configuration to the target environment.\n\n## When to Use This Skill\n\nThis skill activates when you need to:\n- Deploy a new monitoring stack (Prometheus, Grafana, Datadog).\n- Configure an existing monitoring stack.\n- Generate production-ready monitoring configurations.\n\n## Examples\n\n### Example 1: Setting up Prometheus and Grafana on Kubernetes\n\nUser request: \"I need to set up Prometheus and Grafana on my Kubernetes cluster to monitor my application.\"\n\nThe skill will:\n1. Generate Kubernetes manifests for deploying Prometheus and Grafana.\n2. Provide instructions for configuring Prometheus to scrape application metrics and Grafana to visualize them.\n\n### Example 2: Deploying Datadog Agent\n\nUser request: \"Deploy Datadog agent to monitor our servers.\"\n\nThe skill will:\n1. Generate configuration files for the Datadog agent based on the target environment.\n2. Provide instructions for installing and configuring the Datadog agent on the specified servers.\n\n## Best Practices\n\n- **Security**: Always follow security best practices when deploying monitoring stacks, including using secure credentials and limiting access to sensitive data.\n- **Scalability**: Design your monitoring stack to be scalable to handle increasing data volumes and traffic.\n- **Documentation**: Thoroughly document your monitoring setup, including configuration details and deployment procedures.\n\n## Integration\n\nThis skill works seamlessly with other Claude Code skills for infrastructure provisioning and application deployment. It can be integrated into automated CI\u002FCD pipelines for continuous monitoring.\n","## Overview\n\nThis skill empowers Claude to automate the deployment of comprehensive monitoring solutions. It simplifies the setup of Prometheus, Grafana, and Datadog, ensuring best practices and production-ready configurations.\n\n## How It Works\n\n1. **Configuration Gathering**: Claude gathers the specific requirements for the monitoring stack, including the desired platform and tools.\n2. **Stack Generation**: Based on the requirements, Claude generates the necessary configuration files and deployment scripts for the selected monitoring stack.\n3. **Deployment Instructions**: Claude provides clear, step-by-step instructions for deploying the generated configuration to the target environment.\n\n## When to Use This Skill\n\nThis skill activates when you need to:\n- Deploy a new monitoring stack (Prometheus, Grafana, Datadog).\n- Configure an existing monitoring stack.\n- Generate production-ready monitoring configurations.\n\n## Examples\n\n### Example 1: Setting up Prometheus and Grafana on Kubernetes\n\nUser request: \"I need to set up Prometheus and Grafana on my Kubernetes cluster to monitor my application.\"\n\nThe skill will:\n1. Generate Kubernetes manifests for deploying Prometheus and Grafana.\n2. Provide instructions for configuring Prometheus to scrape application metrics and Grafana to visualize them.\n\n### Example 2: Deploying Datadog Agent\n\nUser request: \"Deploy Datadog agent to monitor our servers.\"\n\nThe skill will:\n1. Generate configuration files for the Datadog agent based on the target environment.\n2. Provide instructions for installing and configuring the Datadog agent on the specified servers.\n\n## Best Practices\n\n- **Security**: Always follow security best practices when deploying monitoring stacks, including using secure credentials and limiting access to sensitive data.\n- **Scalability**: Design your monitoring stack to be scalable to handle increasing data volumes and traffic.\n- **Documentation**: Thoroughly document your monitoring setup, including configuration details and deployment procedures.\n\n## Integration\n\nThis skill works seamlessly with other Claude Code skills for infrastructure provisioning and application deployment. It can be integrated into automated CI\u002FCD pipelines for continuous monitoring.\n",{"name":5,"description":7},"master","be156301b65e301887f327d08190ed4f17ba08d2","docs\u002Fnot-mcp-related\u002Fclaude-skills\u002Ftemp\u002Fcode-plugins\u002Fplugins\u002Fdevops\u002Fmonitoring-stack-deployer\u002Fskills\u002Fmonitoring-stack-deployer",0,"https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp","https:\u002F\u002Fgithub.com\u002Fsandraschi","2026-11-11 11:02:01",{"source":8,"skillName":5,"commands":60,"prompt":70,"zipAvailable":71},[61,64,67],{"tool":62,"command":63},"npx","npx skills add sandraschi\u002Fdocumentation-mcp --skill deploying-monitoring-stacks",{"tool":65,"command":66},"bunx","bunx skills add sandraschi\u002Fdocumentation-mcp --skill deploying-monitoring-stacks",{"tool":68,"command":69},"pnpm","pnpm dlx skills add sandraschi\u002Fdocumentation-mcp --skill deploying-monitoring-stacks","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp\u002Fblob\u002Fmaster\u002Fdocs\u002Fnot-mcp-related\u002Fclaude-skills\u002Ftemp\u002Fcode-plugins\u002Fplugins\u002Fdevops\u002Fmonitoring-stack-deployer\u002Fskills\u002Fmonitoring-stack-deployer\u002FSKILL.md",true,[73,79,85],{"path":74,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":77,"sourceHtmlUrl":78},"assets\u002FREADME.md","ASSET","资产文件",528,"https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp\u002Fblob\u002Fmaster\u002Fdocs\u002Fnot-mcp-related\u002Fclaude-skills\u002Ftemp\u002Fcode-plugins\u002Fplugins\u002Fdevops\u002Fmonitoring-stack-deployer\u002Fskills\u002Fmonitoring-stack-deployer\u002Fassets\u002FREADME.md",{"path":80,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002FREADME.md","REFERENCE","参考文档",574,"https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp\u002Fblob\u002Fmaster\u002Fdocs\u002Fnot-mcp-related\u002Fclaude-skills\u002Ftemp\u002Fcode-plugins\u002Fplugins\u002Fdevops\u002Fmonitoring-stack-deployer\u002Fskills\u002Fmonitoring-stack-deployer\u002Freferences\u002FREADME.md",{"path":86,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":89,"sourceHtmlUrl":90},"scripts\u002FREADME.md","SCRIPT","脚本",510,"https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp\u002Fblob\u002Fmaster\u002Fdocs\u002Fnot-mcp-related\u002Fclaude-skills\u002Ftemp\u002Fcode-plugins\u002Fplugins\u002Fdevops\u002Fmonitoring-stack-deployer\u002Fskills\u002Fmonitoring-stack-deployer\u002Fscripts\u002FREADME.md",[92,114,141,149,173,198],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":102,"publishedAt":47},"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",[98,101],{"categoryNo":99,"categoryName":100,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[103,104,105,106,39,107,108,109,110,111,112,113],"docs research","docs","research","standards","packaging","ask","server","search","fastmcp","documentation","MCP",{"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":120,"publishedAt":47},"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",[],[121,122,123,124,125,126,127,128,129,130,131,132,133,134,135,136,137,138,139,140],"drift","wrappee drift","api","data","audit","capabilities","training","memory","features","repo audit","competitors","fleet","now","software","tool list","only","never","coverage","list","read",{"skillNo":142,"name":143,"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":144,"categories":145,"keywords":148,"publishedAt":47},"01M6PFADA3X031SK3W3T6X0N6H","modules","https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp\u002Fblob\u002Fmaster\u002Fdocs\u002Fskills\u002Fwindsurf-mcp-standards\u002Fmodules\u002FSKILL.md",[146,147],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[143],{"skillNo":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":153,"categories":154,"keywords":159,"publishedAt":47},"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",[155,158],{"categoryNo":156,"categoryName":157,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[160,113,106,39,27,161,162,163,164,165,30,166,167,168,169,170,112,171,172,107],"mcp standards","sampling","scaffolding","servers","cd","error","CI\u002FCD","access","ci","mcp servers","error handling","workflows","testing",{"skillNo":174,"name":175,"nameZh":6,"description":176,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":177,"categories":178,"keywords":181,"publishedAt":47},"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",[179,180],{"categoryNo":156,"categoryName":157,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[182,183,184,185,186,113,187,188,189,30,190,191,192,193,194,40,195,196,109,197],"webapp","test","webapp cua test","playwright","mcp server","dev","dom","assertions","trigger","click","app","tauri","repo","e2e","ocr","browser",{"skillNo":199,"name":200,"nameZh":6,"description":201,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":202,"categories":203,"keywords":205,"publishedAt":47},"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",[204],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[200,194,30,190,206,207,208,209,210,211,212,109,213,187,214,215,216,186,217,113],"gates","ship it","artifact","done","say","work","publish","push","shipping","quality gates","commit","github"]