vigil-check
安装方式
先用 Prompt 核对来源,也可切换到安装命令或下载可用的安装包。
用 AI 助手安装
复制提示词,让助手先核对固定版本和依赖。
查看 Prompt收起 Prompt
先检查当前 Agent 是否已安装 SkillPI Skill Finder。如果尚未安装,请按官方仓库的说明安装并启用:https://github.com/Findskills/skillpi。然后使用 Skill Finder 打开此 SkillPI 详情页并定位 "vigil-check":https://skillpi.com/zh/skills/deepskill-70a2e5b5e3de357e1d58f9a27efab3dc09e4ae18285d35c9f69a7d8a56f9e6d7。安装前核对上游来源和版本:https://github.com/jeremylongshore/tons-of-skills-marketplace/blob/6ea46b08dce892944db7c16f28d0b5308d402402/plugins/ai-agency/tonone/skills/vigil-check/SKILL.md。来源不一致时停止并说明差异。核对通过后,用 Skill Finder 安装目标 Skill,并报告安装路径和来源版本。
此命令从 GitHub 来源仓库获取指定技能。运行前请先查看源文件。
npx skills add https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/6ea46b08dce892944db7c16f28d0b5308d402402/plugins/ai-agency/tonone/skills/vigil-check --skill vigil-check来源与配置
查看 GitHub 源码jeremylongshore/tons-of-skills-marketplace固定提交 6ea46b08dce892944db7c16f28d0b5308d402402
配置方式待核实
请查看原始来源中的适用工具、依赖和权限要求。
安装实测待补充
本条目收录公开技能“vigil-check”,按来源分类归入「系统管理」使用场景、「软件开发与 IT」职业。目录标签:ai-lab、监控覆盖、可观测性、SLO审计。此页用于按主题发现相关资源;请通过固定原站版本核对实际能力、依赖环境和所需权限。本站仅提供独立目录介绍与原站入口,原始文件和附件依各自许可开放。
文件浏览
--- name: vigil-check description: Verify observability posture — audit monitoring coverage, find blind spots, prioritize gaps. Use when asked "is monitoring sufficient", "observability review", "are we covered", or "pre-launch monitoring check". allowed-tools: Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion version: 0.6.4 author: tonone-ai <hello@tonone.ai> license: MIT --- # Verify Observability Posture You are Vigil — the observability and reliability engineer from the Engineering Team. ## Steps ### Step 0: Detect Environment Discover the project's full monitoring stack: - Check for metrics: Prometheus configs, Datadog agent, Cloud Monitoring, CloudWatch, New Relic, StatsD - Check for tracing: OpenTelemetry configs, Jaeger, Cloud Trace, X-Ray, Honeycomb, Datadog APM - Check for logging: logging library configs, Cloud Logging, ELK, Loki, Datadog Logs, Axiom - Check for alerting: PagerDuty, Opsgenie, Grafana alerts, CloudWatch alarms, Betterstack - Check for error tracking: Sentry DSN, Bugsnag, Rollbar configs - Identify all services: scan for service definitions, Docker Compose, Kubernetes manifests, deployment configs Build a list of all services and the monitoring stack available. ### Step 1: Audit Each Service For each service discovered, check the following: **RED Metrics:** - Are request rate, error rate, and duration metrics being collected? - Search for: prometheus middleware, metrics handlers, OpenTelemetry metric instrumentation, StatsD calls - Check: are metrics exported to a collector/platform? **SLOs:** - Are SLOs defined for the service? - Search for: SLO definitions in config files, docs, or monitoring platform configs - Check: is there an error budget tracking mechanism? **Alerts:** - Are alerts configured for this service? - Search for: alert rules in Prometheus/Grafana configs, CloudWatch alarm definitions, Datadog monitor configs - Check: are alerts tied to SLOs or just arbitrary thresholds? **Runbooks:** - Do runbooks exist for each alert? - Search for: runbook files, links in alert annotations, docs/runbooks directory - Check: are runbooks actionable (diagnosis steps, fix commands) or just descriptions? **Tracing:** - Is distributed tracing configured? - Search for: OpenTelemetry SDK initialization, trace context propagation, span creation - Check: do traces connect across service boundaries? **Structured Logging:** - Are logs structured (JSON) with correlation IDs? - Search for: structured logging library configuration, JSON log format, request ID propagation - Check: are logs shipped to a centralized platform? ### Step 2: Report Gaps Present results as a coverage matrix: ``` ## Observability Posture ### Coverage Matrix | Service | RED Metrics | SLOs | Alerts | Runbooks | Tracing | Logging | |---------|------------|------|--------|----------|---------|---------| | [name] | yes/no | yes/no| yes/no | yes/no | yes/no | yes/no | ### Critical Gaps (fix before launch) - [gap] — [service] — [why it matters] ### Important Gaps (fix soon) - [gap] — [service] — [why it matters] ### Nice to Have - [gap] — [service] — [why it matters] ``` ### Step 3: Prioritize by Blast Radius Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose. Order recommendations by impact: 1. **Customer-facing services first** — if the user can see it, it must be monitored 2. **Revenue-critical paths** — payment, checkout, auth — zero blind spots 3. **Data integrity** — anything that writes to a database needs error tracking 4. **Internal services** — important but lower priority than user-facing 5. **Batch jobs and cron** — often forgotten, monitor for failure and duration drift For each gap, provide a concrete recommendation: what to add, which library/tool, and estimated effort (small/medium/large). ## Delivery If output exceeds the 40-line CLI budget, invoke `/atlas-report` with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.
当前收录版本
0.6.4
质量评测
满分 100。前四项来自 DeepSkill 收录的质量报告。
评分依据
解决可观测性审计这一工程刚需,适用于发布前监控检查、监控充分性审查等高频场景
评分依据
触发词精准覆盖多种变体(如“监控是否充分”、“可观测性审查”),边界清晰
评分依据
步骤划分清晰,包含环境探测、服务审计、缺口报告、优先级排序四个阶段
评分依据
工具来源明确,参数合理,覆盖主要异常场景
计算方式
取前四项原始分值的算术平均,四舍五入取整。可通过收录报告核对各项评分与说明,运行记录需单独查证。
权限与使用前检查
根据当前主文档自动整理,命中内容可能是示例或防护说明;不是实际权限声明,也未覆盖附件、外部依赖或运行行为。
未从主文档识别到上述常见操作,不能据此判断无需权限或没有风险。
安全评级与访问范围
risk · 静态证据核验,不代表运行安全保证。
使用前请由宿主核对并授权实际文件读写、外部服务和联网目的地;本站的核验不会授予任何运行权限。
用户讨论
还没有已核实的点评。