Loading...
Loading...
Found 4 Skills
Monitor and debug Eve jobs with CLI follow, logs, wait, and diagnose commands. Use when work is stuck, failing, or you need fast status.
Use this skill for proactive backend health audits in an InsForge project — security misconfigurations, performance regressions, and system health issues surfaced by `diagnose advisor`, plus the backend-side deep-dives that pair with each advisor issue. Also use this skill when a user reports backend-wide performance degradation (high CPU/memory, all responses slow, connection pool exhaustion, lock contention) without a single failing request. Trigger on requests like "health check", "audit my backend", "review security", "check RLS policies", "find slow queries", "backend performance review", "high CPU/memory", "everything is slow", "EC2/database/system health", or pre-launch readiness audits. For reactive runtime errors with a single concrete failing request (SDK error objects, HTTP 4xx/5xx, function failures, deploy failures), use `insforge-debug` instead.
Home Assistant integrations, add-ons, updates, and system operations. Use when the user asks about config entries, add-ons, updates, reloads/restarts, or system health, and when mapping those needs to ha-mcp tools.
Used to check the system health status of ECS instances, identify anomalies such as memory, disk, CPU, load and resource leaks, and automatically supplement in-depth diagnosis results when critical memory issues are detected. Suitable for instance inspection, troubleshooting and risk warning scenarios. Trigger words: SysOM, inspection, instance diagnosis, memory_usage_rate, memory usage rate.