[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79WM3AXVZ0JMBNCD2MB67AF":3,"skill-same:01M79WM3AXVZ0JMBNCD2MB67AF":44},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":13,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M79WM3AXVZ0JMBNCD2MB67AF","server-management",null,"Server management principles and decision-making. Process management, monitoring strategy, and scaling decisions. Teaches thinking, not commands.","KrismithReddy12\u002Fclaude-code-templates","KrismithReddy12","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F182916557?v=4","01M79T8DNGJRHG48G3H3Q02MK8","01M79TA8ZWV2PP7R4ARWVYWZFE",0,"MIT","https:\u002F\u002Fgithub.com\u002FKrismithReddy12\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fserver-management\u002FSKILL.md",[],[],"2026-11-15 14:19:17",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":23},"Read, Write, Edit, Glob, Grep, Bash","main","e3744adb7654df443f12927f3e001252b3a26b6d","cli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fserver-management","https:\u002F\u002Fgithub.com\u002FKrismithReddy12\u002Fclaude-code-templates","https:\u002F\u002Fgithub.com\u002FKrismithReddy12","2026-07-29 08:15:10",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add KrismithReddy12\u002Fclaude-code-templates --skill server-management",{"tool":36,"command":37},"bunx","bunx skills add KrismithReddy12\u002Fclaude-code-templates --skill server-management",{"tool":39,"command":40},"pnpm","pnpm dlx skills add KrismithReddy12\u002Fclaude-code-templates --skill server-management","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FKrismithReddy12\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fserver-management\u002FSKILL.md",true,[],[45,52,61,68,75,82],{"skillNo":46,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":49,"categories":50,"keywords":51,"publishedAt":18},"01M79YMXJ07S2BQVB7JAM3657Q","zapier-make-patterns","No-code automation democratizes workflow building. Zapier and Make (formerly Integromat) let non-developers automate business processes without writing code. But no-code doesn't mean no-complexity - these platforms have their own patterns, pitfalls, and breaking points.  This skill covers when to use which platform, how to build reliable automations, and when to graduate to code-based solutions. Key insight: Zapier optimizes for simplicity and integrations (7000+ apps), Make optimizes for power","https:\u002F\u002Fgithub.com\u002FKrismithReddy12\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fzapier-make-patterns\u002FSKILL.md",[],[],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":56,"licenseFileUrl":57,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":18},"01M79YMVPMK3Y4JDP2KDJKQ2ZD","yeet","Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).","Apache-2.0","https:\u002F\u002Fgithub.com\u002FKrismithReddy12\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FKrismithReddy12\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":18},"01M79YMMQ4XXMPJHDQHY8FR7ME","workflow-automation","Workflow automation is the infrastructure that makes AI agents reliable. Without durable execution, a network hiccup during a 10-step payment flow means lost money and angry customers. With it, workflows resume exactly where they left off.  This skill covers the platforms (n8n, Temporal, Inngest) and patterns (sequential, parallel, orchestrator-worker) that turn brittle scripts into production-grade automation.  Key insight: The platforms make different tradeoffs. n8n optimizes for accessibility","https:\u002F\u002Fgithub.com\u002FKrismithReddy12\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fworkflow-automation\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":18},"01M79YMHQY3CP1XXMQ00TGQFAW","trigger-dev","Trigger.dev expert for background jobs, AI workflows, and reliable async execution with excellent developer experience and TypeScript-first design. Use when: trigger.dev, trigger dev, background task, ai background job, long running task.","https:\u002F\u002Fgithub.com\u002FKrismithReddy12\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Ftrigger-dev\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":18},"01M79YME4Z3DRW0MT6BNYW1D7P","slack-automation","Automate Slack workspace operations including messaging, search, channel management, and reaction workflows through Composio's Slack toolkit.","https:\u002F\u002Fgithub.com\u002FKrismithReddy12\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fslack-automation\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":18},"01M79YMAX7NFYDFXFZH2TJS7SS","planning-with-files","Transforms workflow to use Manus-style persistent markdown files for planning, progress tracking, and knowledge storage. Use when starting complex tasks, multi-step projects, research tasks, or when the user mentions planning, organizing work, tracking progress, or wants structured output.","https:\u002F\u002Fgithub.com\u002FKrismithReddy12\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fplanning-with-files\u002FSKILL.md",[],[]]