[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71C6029Y2DW676T8FH4N25G":3,"skill-same:01M71C6029Y2DW676T8FH4N25G":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":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":14,"repositoryHtmlUrl":52,"repositoryHomepageUrl":6,"ownerHtmlUrl":53,"ownerBlogUrl":6,"ownerDescription":54,"updatedAt":55,"install":56,"resources":69},"01M71C6029Y2DW676T8FH4N25G","server-management",null,"Server management principles and decision-making. Process management, monitoring strategy, and scaling decisions. Teaches thinking, not commands.","yqecea\u002Fgem-swarm","yqecea","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F196189405?v=4","01M71C12KWH5QPTE12J69335KF","Yusuf","01M71C12MFS3BRGNE5SSHB4DY9",1,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fyqecea\u002Fgem-swarm\u002Fblob\u002Fmain\u002Fsrc\u002Fskills\u002Fdomain\u002Fserver-management\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"server","management","server management","grep","commands","edit","write","read","process","principles","monitoring","Bash","decisions","decision-making","strategy","decision","process management","scaling","thinking","2026-11-10 10:12:30",false,"---\nname: server-management\ndescription: Server management principles and decision-making. Process management, monitoring strategy, and scaling decisions. Teaches thinking, not commands.\nallowed-tools: Read, Write, Edit, Glob, Grep, Bash\n---\n\n# Server Management\n\n> Server management principles for production operations.\n> **Learn to THINK, not memorize commands.**\n\n---\n\n## 1. Process Management Principles\n\n### Tool Selection\n\n| Scenario | Tool |\n|----------|------|\n| **Node.js app** | PM2 (clustering, reload) |\n| **Any app** | systemd (Linux native) |\n| **Containers** | Docker\u002FPodman |\n| **Orchestration** | Kubernetes, Docker Swarm |\n\n### Process Management Goals\n\n| Goal | What It Means |\n|------|---------------|\n| **Restart on crash** | Auto-recovery |\n| **Zero-downtime reload** | No service interruption |\n| **Clustering** | Use all CPU cores |\n| **Persistence** | Survive server reboot |\n\n---\n\n## 2. Monitoring Principles\n\n### What to Monitor\n\n| Category | Key Metrics |\n|----------|-------------|\n| **Availability** | Uptime, health checks |\n| **Performance** | Response time, throughput |\n| **Errors** | Error rate, types |\n| **Resources** | CPU, memory, disk |\n\n### Alert Severity Strategy\n\n| Level | Response |\n|-------|----------|\n| **Critical** | Immediate action |\n| **Warning** | Investigate soon |\n| **Info** | Review daily |\n\n### Monitoring Tool Selection\n\n| Need | Options |\n|------|---------|\n| Simple\u002FFree | PM2 metrics, htop |\n| Full observability | Grafana, Datadog |\n| Error tracking | Sentry |\n| Uptime | UptimeRobot, Pingdom |\n\n---\n\n## 3. Log Management Principles\n\n### Log Strategy\n\n| Log Type | Purpose |\n|----------|---------|\n| **Application logs** | Debug, audit |\n| **Access logs** | Traffic analysis |\n| **Error logs** | Issue detection |\n\n### Log Principles\n\n1. **Rotate logs** to prevent disk fill\n2. **Structured logging** (JSON) for parsing\n3. **Appropriate levels** (error\u002Fwarn\u002Finfo\u002Fdebug)\n4. **No sensitive data** in logs\n\n---\n\n## 4. Scaling Decisions\n\n### When to Scale\n\n| Symptom | Solution |\n|---------|----------|\n| High CPU | Add instances (horizontal) |\n| High memory | Increase RAM or fix leak |\n| Slow response | Profile first, then scale |\n| Traffic spikes | Auto-scaling |\n\n### Scaling Strategy\n\n| Type | When to Use |\n|------|-------------|\n| **Vertical** | Quick fix, single instance |\n| **Horizontal** | Sustainable, distributed |\n| **Auto** | Variable traffic |\n\n---\n\n## 5. Health Check Principles\n\n### What Constitutes Healthy\n\n| Check | Meaning |\n|-------|---------|\n| **HTTP 200** | Service responding |\n| **Database connected** | Data accessible |\n| **Dependencies OK** | External services reachable |\n| **Resources OK** | CPU\u002Fmemory not exhausted |\n\n### Health Check Implementation\n\n- Simple: Just return 200\n- Deep: Check all dependencies\n- Choose based on load balancer needs\n\n---\n\n## 6. Security Principles\n\n| Area | Principle |\n|------|-----------|\n| **Access** | SSH keys only, no passwords |\n| **Firewall** | Only needed ports open |\n| **Updates** | Regular security patches |\n| **Secrets** | Environment vars, not files |\n| **Audit** | Log access and changes |\n\n---\n\n## 7. Troubleshooting Priority\n\nWhen something's wrong:\n\n1. **Check if running** (process status)\n2. **Check logs** (error messages)\n3. **Check resources** (disk, memory, CPU)\n4. **Check network** (ports, DNS)\n5. **Check dependencies** (database, APIs)\n\n---\n\n## 8. Anti-Patterns\n\n| ❌ Don't | ✅ Do |\n|----------|-------|\n| Run as root | Use non-root user |\n| Ignore logs | Set up log rotation |\n| Skip monitoring | Monitor from day one |\n| Manual restarts | Auto-restart config |\n| No backups | Regular backup schedule |\n\n---\n\n> **Remember:** A well-managed server is boring. That's the goal.\n","# Server Management\n\n> Server management principles for production operations.\n> **Learn to THINK, not memorize commands.**\n\n---\n\n## 1. Process Management Principles\n\n### Tool Selection\n\n| Scenario | Tool |\n|----------|------|\n| **Node.js app** | PM2 (clustering, reload) |\n| **Any app** | systemd (Linux native) |\n| **Containers** | Docker\u002FPodman |\n| **Orchestration** | Kubernetes, Docker Swarm |\n\n### Process Management Goals\n\n| Goal | What It Means |\n|------|---------------|\n| **Restart on crash** | Auto-recovery |\n| **Zero-downtime reload** | No service interruption |\n| **Clustering** | Use all CPU cores |\n| **Persistence** | Survive server reboot |\n\n---\n\n## 2. Monitoring Principles\n\n### What to Monitor\n\n| Category | Key Metrics |\n|----------|-------------|\n| **Availability** | Uptime, health checks |\n| **Performance** | Response time, throughput |\n| **Errors** | Error rate, types |\n| **Resources** | CPU, memory, disk |\n\n### Alert Severity Strategy\n\n| Level | Response |\n|-------|----------|\n| **Critical** | Immediate action |\n| **Warning** | Investigate soon |\n| **Info** | Review daily |\n\n### Monitoring Tool Selection\n\n| Need | Options |\n|------|---------|\n| Simple\u002FFree | PM2 metrics, htop |\n| Full observability | Grafana, Datadog |\n| Error tracking | Sentry |\n| Uptime | UptimeRobot, Pingdom |\n\n---\n\n## 3. Log Management Principles\n\n### Log Strategy\n\n| Log Type | Purpose |\n|----------|---------|\n| **Application logs** | Debug, audit |\n| **Access logs** | Traffic analysis |\n| **Error logs** | Issue detection |\n\n### Log Principles\n\n1. **Rotate logs** to prevent disk fill\n2. **Structured logging** (JSON) for parsing\n3. **Appropriate levels** (error\u002Fwarn\u002Finfo\u002Fdebug)\n4. **No sensitive data** in logs\n\n---\n\n## 4. Scaling Decisions\n\n### When to Scale\n\n| Symptom | Solution |\n|---------|----------|\n| High CPU | Add instances (horizontal) |\n| High memory | Increase RAM or fix leak |\n| Slow response | Profile first, then scale |\n| Traffic spikes | Auto-scaling |\n\n### Scaling Strategy\n\n| Type | When to Use |\n|------|-------------|\n| **Vertical** | Quick fix, single instance |\n| **Horizontal** | Sustainable, distributed |\n| **Auto** | Variable traffic |\n\n---\n\n## 5. Health Check Principles\n\n### What Constitutes Healthy\n\n| Check | Meaning |\n|-------|---------|\n| **HTTP 200** | Service responding |\n| **Database connected** | Data accessible |\n| **Dependencies OK** | External services reachable |\n| **Resources OK** | CPU\u002Fmemory not exhausted |\n\n### Health Check Implementation\n\n- Simple: Just return 200\n- Deep: Check all dependencies\n- Choose based on load balancer needs\n\n---\n\n## 6. Security Principles\n\n| Area | Principle |\n|------|-----------|\n| **Access** | SSH keys only, no passwords |\n| **Firewall** | Only needed ports open |\n| **Updates** | Regular security patches |\n| **Secrets** | Environment vars, not files |\n| **Audit** | Log access and changes |\n\n---\n\n## 7. Troubleshooting Priority\n\nWhen something's wrong:\n\n1. **Check if running** (process status)\n2. **Check logs** (error messages)\n3. **Check resources** (disk, memory, CPU)\n4. **Check network** (ports, DNS)\n5. **Check dependencies** (database, APIs)\n\n---\n\n## 8. Anti-Patterns\n\n| ❌ Don't | ✅ Do |\n|----------|-------|\n| Run as root | Use non-root user |\n| Ignore logs | Set up log rotation |\n| Skip monitoring | Monitor from day one |\n| Manual restarts | Auto-restart config |\n| No backups | Regular backup schedule |\n\n---\n\n> **Remember:** A well-managed server is boring. That's the goal.\n",{"name":5,"description":7,"allowed-tools":48},"Read, Write, Edit, Glob, Grep, Bash","main","923c514d4d5e15bbfd65ec7eaf949a997679aa3e","src\u002Fskills\u002Fdomain\u002Fserver-management","https:\u002F\u002Fgithub.com\u002Fyqecea\u002Fgem-swarm","https:\u002F\u002Fgithub.com\u002Fyqecea","15 y.o Data Science,Student","2026-04-26 20:00:27",{"source":8,"skillName":5,"commands":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add yqecea\u002Fgem-swarm --skill server-management",{"tool":62,"command":63},"bunx","bunx skills add yqecea\u002Fgem-swarm --skill server-management",{"tool":65,"command":66},"pnpm","pnpm dlx skills add yqecea\u002Fgem-swarm --skill server-management","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fyqecea\u002Fgem-swarm\u002Fblob\u002Fmain\u002Fsrc\u002Fskills\u002Fdomain\u002Fserver-management\u002FSKILL.md",true,[],[71,85,98,109,121,144],{"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":77,"publishedAt":43},"01M71C74XVPP23ST10E8MYJZA0","validation","Cross-cutting validation methodology for verifying phase outputs and project integrity","https:\u002F\u002Fgithub.com\u002Fyqecea\u002Fgem-swarm\u002Fblob\u002Fmain\u002Fsrc\u002Fskills\u002Fshared\u002Fvalidation\u002FSKILL.md",[],[73,78,79,80,81,82,83,84],"validation methodology","for","project","outputs","phase","methodology","integrity",{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":43},"01M71C72PTKRV481M975R3QDDE","session-management","Manages orchestration session state, tracking, and resumption","https:\u002F\u002Fgithub.com\u002Fyqecea\u002Fgem-swarm\u002Fblob\u002Fmain\u002Fsrc\u002Fskills\u002Fshared\u002Fsession-management\u002FSKILL.md",[],[92,93,25,94,95,96,97],"session management","session","session state","orchestration","state","tracking",{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":43},"01M71C6ZY1EGM4SGVYT4B2HHD7","implementation-planning","Generates detailed implementation plans from finalized designs","https:\u002F\u002Fgithub.com\u002Fyqecea\u002Fgem-swarm\u002Fblob\u002Fmain\u002Fsrc\u002Fskills\u002Fshared\u002Fimplementation-planning\u002FSKILL.md",[],[105,106,107,108],"planning","implementation","implementation planning","plans",{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":43},"01M71C6XQVGMDFJ50BP5SBDS76","execution","Phase execution methodology for orchestration workflows with error handling and completion protocols","https:\u002F\u002Fgithub.com\u002Fyqecea\u002Fgem-swarm\u002Fblob\u002Fmain\u002Fsrc\u002Fskills\u002Fshared\u002Fexecution\u002FSKILL.md",[],[111,79,83,116,117,95,82,118,119,120],"error","workflows","protocols","error handling","with",{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":135,"publishedAt":43},"01M71C6VY8APWMNK1XEJ3WP7A2","design-dialogue","Guides structured design conversations for complex engineering tasks","https:\u002F\u002Fgithub.com\u002Fyqecea\u002Fgem-swarm\u002Fblob\u002Fmain\u002Fsrc\u002Fskills\u002Fshared\u002Fdesign-dialogue\u002FSKILL.md",[127,130],{"categoryNo":128,"categoryName":129,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":131,"categoryName":132,"taxonomyType":133,"taxonomyTypeDesc":134},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[136,137,138,139,140,79,141,142,143],"dialogue","design","design dialogue","guides","conversations","tasks","engineering","structured",{"skillNo":145,"name":146,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":154,"publishedAt":43},"01M71C6R4RJWG3S2R26778TPD8","delegation","Agent delegation best practices for constructing effective subagent prompts with proper scoping","https:\u002F\u002Fgithub.com\u002Fyqecea\u002Fgem-swarm\u002Fblob\u002Fmain\u002Fsrc\u002Fskills\u002Fshared\u002Fdelegation\u002FSKILL.md",[150,151],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":152,"categoryName":153,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[146,155,156,79,157,120,158],"subagent","scoping","best practices","prompts"]