Post-deploy monitoring. Use when verifying a deployed app is healthy after deploy or launch — auto-fires from launch/deploy. Checks HTTP status, response times, error detection, and smoke test report.
中文简介正在准备中。当前显示原文说明。
查看安装方法安装前可以查看交给 AI 代理的指令内容。
Post-deploy monitoring. Receives a deployed URL and list of expected endpoints, runs health checks, measures response times, detects errors, and returns a structured smoke test report.
deploy (L2): post-deploy monitoring setuplaunch (L1): monitoring as part of launch pipelineincident (L2): current system state check during incident triageNone — pure L3 utility.
Accept input from calling skill:
base_url — deployed application URL (e.g. https://myapp.com)endpoints — list of paths to check (e.g. ["/", "/health", "/api/status"])If no endpoints provided, default to: ["/", "/health", "/ready"]
For each endpoint, run an HTTP status check using Bash:
curl -s -o /dev/null -w "%{http_code}" https://myapp.com/health
For each endpoint, measure latency using Bash:
curl -s -o /dev/null -w "%{time_total}" https://myapp.com/health
Thresholds:
2000ms → SLOW (flag as alert)
After collecting response times from Step 3, analyze for patterns that indicate root causes:
PERF_WARN — investigate N+1 query or missing DB indexPERF_WARN — connection pool saturation likelyPERF_REGRESSION — correlate with recent git diffIf no previous baseline exists, skip spike detection and note INFO: no baseline — first run.
Output performance signals into a perf_signals list (separate from alerts).
Scan responses for problems:
Collect all flagged issues into an alerts list.
Output the following report structure:
## Watchdog Report: [base_url]
### Smoke Test Results
- [endpoint] — [HTTP status] ([response_time]s) — [HEALTHY|REDIRECT|CLIENT_ERROR|SERVER_ERROR|UNREACHABLE]
### Alert Rules Applied
- Response time > 2s → alert
- Any 4xx on non-auth endpoint → alert
- Any 5xx → critical alert
- Unreachable → critical alert
### Alerts
- [CRITICAL|WARNING] [endpoint] — [reason]
### Performance Signals
- [PERF_WARN|PERF_REGRESSION|INFO] [endpoint] — [diagnosis]
### Summary
- Total endpoints checked: [n]
- Healthy: [n]
- Alerts: [n]
- Perf Signals: [n]
- Overall status: ALL_HEALTHY | DEGRADED | DOWN
If no alerts and no perf signals: output Overall status: ALL_HEALTHY.
## Watchdog Report: [base_url]
### Smoke Test Results
- / — 200 (0.231s) — HEALTHY
- /health — 200 (0.089s) — HEALTHY
- /api/status — 500 (1.203s) — SERVER_ERROR
### Alerts
- CRITICAL /api/status — HTTP 500
### Summary
- Total: 3 | Healthy: 2 | Alerts: 1
- Overall status: DEGRADED
perf skill — watchdog is a detector, not a diagnoserKnown failure modes for this skill. Check these before declaring done.
| Failure Mode | Severity | Mitigation |
|---|---|---|
| curl timeout treated as slow (not unreachable) | HIGH | Non-zero curl exit code = UNREACHABLE, not a response time measurement |
| PERF_REGRESSION reported without baseline | MEDIUM | Only flag regression if a previous run exists — otherwise INFO: first run |
| All endpoints flagged SLOW because test env is slow | MEDIUM | Note environment context — add ENV: non-production detected if URL contains dev/staging/localhost |
| Perf signal without actionable diagnosis | LOW | Every PERF_WARN must include a hypothesis (N+1, pool saturation, etc.) |
alerts list, all SLOW → alerts listperf_signals list (or INFO: first run)~500-1500 tokens input, ~300-800 tokens output. Sonnet for configuration quality.
还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
Pre-implementation red-team analysis. Use when a plan is high-risk, critical path, or expensive to reverse. Challenges plans before code is written — finds edge cases, security holes, scalability bottlenecks, error propagation risks, and integration conflicts. Catches flaws at plan time (10x cheaper than post-implementation).
中文简介正在准备中。当前显示原文说明。
Creates code-based visual assets — SVG icons, OG image HTML templates, social banners, and icon sets. Use when generating visuals as code (vector/HTML), NOT raster images — for raster generation see @rune-pro/media. Outputs files with usage instructions.
中文简介正在准备中。当前显示原文说明。
Comprehensive project audit — security, dependencies, code quality, architecture, performance, infra, docs, and mesh analytics. Use when needing a full 8-dimension health-score snapshot before a major release, M&A diligence, or quarterly review. Delegates to specialist skills (sentinel, dependency-doctor, perf, autopsy, etc.).
中文简介正在准备中。当前显示原文说明。
Full codebase health assessment. Use when diagnosing project health or starting a rescue workflow on legacy code — OR when evaluating an external GitHub repo for dependency / fork / contribution decisions (--external mode). Analyzes complexity, dependencies, dead code, tech debt, and git hotspots. Produces a health score and rescue plan.
中文简介正在准备中。当前显示原文说明。
Business Analyst agent. Use when starting a new feature requiring requirements elicitation BEFORE plan or cook. Asks probing questions, identifies hidden requirements, maps stakeholders, defines scope boundaries, and produces a structured Requirements Document that plan and cook consume.
中文简介正在准备中。当前显示原文说明。
Creative ideation and solution exploration. Generates multiple approaches with trade-offs, uses structured frameworks (SCAMPER, First Principles), and hands off to plan for structuring.
中文简介正在准备中。当前显示原文说明。