Framework for production server operations covering process management, monitoring, logging, and scaling decisions.
Works with
Covers seven core operational areas: process management tool selection (PM2, systemd, Docker, Kubernetes), monitoring strategy with severity-based alerting, and structured log rotation practices
Provides decision matrices for scaling (vertical vs. horizontal vs. auto-scaling), health check depth, and troubleshooting priority order
Emphasizes principles over commands: au
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionserver-managementExecute the skills CLI command in your project's root directory to begin installation:
Fetches server-management from sickn33/antigravity-awesome-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate server-management. Access via /server-management in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
31.1K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
31.1K
stars
Server management principles for production operations. Learn to THINK, not memorize commands.
| Scenario | Tool |
|---|---|
| Node.js app | PM2 (clustering, reload) |
| Any app | systemd (Linux native) |
| Containers | Docker/Podman |
| Orchestration | Kubernetes, Docker Swarm |
| Goal | What It Means |
|---|---|
| Restart on crash | Auto-recovery |
| Zero-downtime reload | No service interruption |
| Clustering | Use all CPU cores |
| Persistence | Survive server reboot |
| Category | Key Metrics |
|---|---|
| Availability | Uptime, health checks |
| Performance | Response time, throughput |
| Errors | Error rate, types |
| Resources | CPU, memory, disk |
| Level | Response |
|---|---|
| Critical | Immediate action |
| Warning | Investigate soon |
| Info | Review daily |
| Need | Options |
|---|---|
| Simple/Free | PM2 metrics, htop |
| Full observability | Grafana, Datadog |
| Error tracking | Sentry |
| Uptime | UptimeRobot, Pingdom |
| Log Type | Purpose |
|---|---|
| Application logs | Debug, audit |
| Access logs | Traffic analysis |
| Error logs | Issue detection |
| Symptom | Solution |
|---|---|
| High CPU | Add instances (horizontal) |
| High memory | Increase RAM or fix leak |
| Slow response | Profile first, then scale |
| Traffic spikes | Auto-scaling |
| Type | When to Use |
|---|---|
| Vertical | Quick fix, single instance |
| Horizontal | Sustainable, distributed |
| Auto | Variable traffic |
| Check | Meaning |
|---|---|
| HTTP 200 | Service responding |
| Database connected | Data accessible |
| Dependencies OK | External services reachable |
| Resources OK | CPU/memory not exhausted |
| Area | Principle |
|---|---|
| Access | SSH keys only, no passwords |
| Firewall | Only needed ports open |
| Updates | Regular security patches |
| Secrets | Environment vars, not files |
| Audit | Log access and changes |
When something's wrong:
| ❌ Don't | ✅ Do |
|---|---|
| Run as root | Use non-root user |
| Ignore logs | Set up log rotation |
| Skip monitoring | Monitor from day one |
| Manual restarts | Auto-restart config |
| No backups | Regular backup schedule |
Remember: A well-managed server is boring. That's the goal.
This skill is applicable to execute the workflow or actions described in the overview.
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
sickn33/antigravity-awesome-skills
sickn33/antigravity-awesome-skills
sickn33/antigravity-awesome-skills
sickn33/antigravity-awesome-skills
sickn33/antigravity-awesome-skills
sickn33/antigravity-awesome-skills
server-management fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
I recommend server-management for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
We added server-management from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Registry listing for server-management matched our evaluation — installs cleanly and behaves as described in the markdown.
Solid pick for teams standardizing on skills: server-management is focused, and the summary matches what you get after install.
server-management has been reliable in day-to-day use. Documentation quality is above average for community skills.
server-management has been reliable in day-to-day use. Documentation quality is above average for community skills.
Registry listing for server-management matched our evaluation — installs cleanly and behaves as described in the markdown.
server-management has been reliable in day-to-day use. Documentation quality is above average for community skills.
Keeps context tight: server-management is the kind of skill you can hand to a new teammate without a long onboarding doc.
showing 1-10 of 70