Monitor监控创建器

Data Storage

CODEBLOCK0

Create on first use: INLINECODE0

Scope

This skill:

• - ✅ Stores monitor definitions in ~/monitor/
• ✅ Runs checks at specified intervals
• ✅ Alerts user on status changes

Execution model:

• - User explicitly defines WHAT to monitor
• User grants any permissions/tools needed
• Skill only handles WHEN and ALERTING

This skill does NOT:

• - ❌ Assume access to any service or endpoint
• ❌ Run checks without user-defined instructions
• ❌ Store credentials (user provides via environment or other skills)

Requirements

Required:

• - curl — for HTTP checks

Optional (for alerts):

• - PUSHOVER_TOKEN / PUSHOVER_USER — for push notifications
• Webhook URL — user provides their own endpoint

Used if available:

• - openssl — for SSL certificate checks
• INLINECODE5 — for process checks
• INLINECODE6 — for disk space checks
• INLINECODE7 — for port checks

Quick Reference

Core Rules

1. User Defines Everything

1. 1. WHAT: User specifies what to check
2. HOW: User provides method or grants tool access
3. WHEN: This skill handles interval
4. ALERT: This skill handles notifications

Example flow:
CODEBLOCK1

2. Monitor Definition

3. Common Check Types

4. Confirmation Format

5. Alert on Change

• - Alert when status changes (ok→fail, fail→ok)
• Include failure count
• Recovery message when back to OK
• Never spam repeated same-status

6. Permissions

• - Empty = basic checks only (curl, df, pgrep)
• INLINECODE12 = user granted SSH access
• INLINECODE13 = user granted Docker access

Agent asks before assuming any access.