菜单
Audit platform health — dependency updates, uptime, error rates, CI status, and deployment hygiene. Use for "dependency audit", "check Sentry errors", "platform health review", or scheduled maintenance. Do NOT use for feature implementation (implement) or debugging a single bug (debug).
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | platform-health |
| description | Audit platform health — dependency updates, uptime, error rates, CI status, and deployment hygiene. Use for "dependency audit", "check Sentry errors", "platform health review", or scheduled maintenance. Do NOT use for feature implementation (implement) or debugging a single bug (debug). |
| license | MIT |
| allowed-tools | Read Bash Glob Grep |
| argument-hint | [--focus deps|errors|ci|uptime] |
| metadata | {"author":"Carinya Parc","version":"0.1.0","owner":"web-development","review_cadence":"monthly","work_shape":"monitor-and-report","output_class":"tracking-update"} |
Dependency audit, error review, and deployment hygiene for webops workflows.
Optional focus: deps, errors, ci, uptime (default: all).
AGENTS.md / CLAUDE.md for commands and conventions..agency/target.json on the target repo, then instance config/ if
present.deps)pnpm outdated or equivalent from repo rootpnpm audit if available)errors)ci)gh run list)uptime)## Platform health — {date}
### Summary
(one paragraph — overall status: green / amber / red)
### Findings
| Area | Severity | Finding | Recommended action |
| ---- | -------- | ------- | ------------------ |
### Suggested issues
- [ ] {title} — squad:site, type:maintenance
Severity: critical · high · medium · low · info.
Instance bootstrap interview — detects existing instance state, guides repo creation (link-first), interviews business identity/services/cadence/targets, writes config/instance.json and target skeletons, then hands off to brand-creative setup. Use on first install, when the user says "set up my instance" or "bootstrap my agency workspace", or to re-check target bindings after config changes.
Create a competitive analysis brief for product strategy, feature prioritization, or sales enablement. Use when comparing competitors, mapping a feature area across rivals, or drafting battle cards. Do NOT use for user research synthesis (synthesize-research) or product strategy doc (product).
Run a weekly, monthly, or quarterly metrics review: scorecard, trends, bright spots, concerns, and recommended actions. Use when investigating a spike or drop, comparing performance against targets, or preparing a metrics readout. Do NOT use for stakeholder status updates (stakeholder-update) or product strategy (product).
Sparring partner for exploring a problem space, generating solutions, or stress-testing product thinking. Conversation, not a deliverable. Use when ideating, assumption-testing, or strategy exploration before a spec. Do NOT use for writing specs (write-spec) or product strategy doc (product).
Write a weekly or monthly status for leadership, announce a launch, escalate a risk, or tailor the same progress for exec, engineering, partner, customer, or board audiences. Use when drafting status updates or launch notes. Do NOT use for product strategy (product) or roadmap updates (roadmap).
Synthesize interview notes, survey data, or support tickets into themes, personas, opportunity areas, and roadmap recommendations. Use when turning raw research into structured findings. Do NOT use for competitive analysis (competitive-brief) or product strategy doc (product).