Application Monitoring

VerifiedCaution

Monitor application health, resource usage, and service availability after deployment.

Sby Skills Guide Bot
DevOpsBeginner
7/24/2026
Claude Code
#monitoring#health-checks#observability#kubernetes#docker

Recommended for

Automated summary

Runs diagnostic commands (HTTP endpoint, kubectl, docker, system logs) to check service health and resource usage, then produces a structured monitoring report.

Strengths

  • Covers several platforms: HTTP health endpoints, Kubernetes, Docker and systemd logs
  • Enforces a readable output format with service/resource tables, recent errors and recommendations
  • Explicit overall status classification as HEALTHY, DEGRADED or DOWN
  • Clearly bounded scope that defers to alert-handling, rollback, performance-analysis and security-auditor

Limitations

  • Read-only: it observes state but does not remediate, restart or page anyone
  • Example thresholds (80% CPU, 90% disk) are placeholders that must be tuned per environment
  • No history or trending — only a point-in-time snapshot from the commands it runs
When to use it

Use it right after a deployment or for a routine check to confirm services respond and resources stay within thresholds.

When not to use it

Don't use it to handle an active incident, fire alerts or roll back a bad release, since those belong to other skills.

Security analysis

Caution
Quality score88/100

The skill is read-only operational monitoring with legitimate diagnostic commands. It does not include destructive actions, secret exfiltration, obfuscated payloads, or safety-disabling instructions. Because it relies on Bash, Docker, Kubernetes, and network access, it warrants caution rather than safe.

Findings
  • •Uses Bash to run operational commands including curl, kubectl, docker, journalctl, df, and free.
  • •Monitoring commands may expose sensitive logs or infrastructure details if output is shared broadly.
  • •curl health checks depend on user-supplied URLs and could reach internal endpoints if misused.
How this analysis is made

Examples

Post-deploy check
Check the health of our staging services and give me a full monitoring report.
Is the app up?
Is the app up? Hit the /health endpoint and show me container CPU and memory usage for the running Docker containers.
Kubernetes error sweep
Monitor the api deployment in namespace prod: check pod status, resource usage, and any errors in the last hour of logs, then tell me if the system is HEALTHY, DEGRADED or DOWN.

name: monitoring description: >- Monitor application health, resource usage, and service availability. Triggers on 'check health', 'monitor services', 'check status', 'is the app up'. NOT for handling alerts (use alert-handling) or rolling back (use rollback). allowed-tools: Bash, Read

When to Use

  • Checking service health and availability after deployment
  • Reviewing resource usage (CPU, memory, disk)
  • Gathering metrics for status reports
  • Verifying services are running correctly

When NOT to Use

  • Responding to specific alerts or incidents -- use alert-handling
  • Rolling back a failed deployment -- use rollback
  • Deep performance profiling -- use performance-analysis
  • Security scanning -- use security-auditor

Instructions

1. Check service health

Run health check commands via Bash based on the deployment platform:

# HTTP health endpoint
curl -sf https://[app-url]/health && echo "HEALTHY" || echo "UNHEALTHY"

# Kubernetes
kubectl get pods -n [namespace]
kubectl get deployments -n [namespace]

# Docker
docker ps --format "table {{.Names}}\t{{.Status}}\t{{.Ports}}"
docker stats --no-stream

2. Check resource usage

# Container resources
docker stats --no-stream --format "table {{.Name}}\t{{.CPUPerc}}\t{{.MemUsage}}"

# Kubernetes resources
kubectl top pods -n [namespace]
kubectl top nodes

# System resources
df -h
free -m

3. Check logs for errors

# Kubernetes logs
kubectl logs -l app=[app] --tail=50 -n [namespace]

# Docker logs
docker logs [container] --tail=50 --since=1h

# System logs
journalctl -u [service] --since "1 hour ago" --no-pager | tail -50

4. Assess overall status

Classify the overall system status:

  • HEALTHY: All services up, resources within thresholds, no errors
  • DEGRADED: Some services impaired, elevated error rates, resource warnings
  • DOWN: Critical services unavailable, health checks failing

Output

## Monitoring Report

### Status: [HEALTHY / DEGRADED / DOWN]

### Services
| Service | Status | Latency | Error Rate |
|---------|--------|---------|------------|
| [name] | UP/DOWN | [ms] | [%] |

### Resources
| Resource | Current | Threshold | Status |
|----------|---------|-----------|--------|
| CPU | [%] | 80% | OK/WARN |
| Memory | [MB] | [limit] | OK/WARN |
| Disk | [%] | 90% | OK/WARN |

### Recent Errors (last 1h)
- [error summary from logs]

### Recommendations
- [actionable next steps if any issues found]

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/application-monitoring-mryiqi7v/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/application-monitoring-mryiqi7v' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/application-monitoring-mryiqi7v/download' --output '.skill-downloads/application-monitoring-mryiqi7v/SKILL.md.part' && mv '.skill-downloads/application-monitoring-mryiqi7v/SKILL.md.part' '.skill-downloads/application-monitoring-mryiqi7v/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

Tools declared by the author (check availability in your agent): Bash, Read

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/application-monitoring-mryiqi7v/SKILL.md' && test -s '.skill-downloads/application-monitoring-mryiqi7v/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/monitoring' && cp -R '.skill-downloads/application-monitoring-mryiqi7v' '.claude/skills/monitoring'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/application-monitoring-mryiqi7v'

openskills read 'application-monitoring-mryiqi7v'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/application-monitoring-mryiqi7v/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills