메뉴
Telemetry/instrumentation design — RED/USE/golden-signals selection, metrics catalog, event taxonomy, SLO-derived alerts, dashboard design. Use at Phase 3 or when nobody can answer "is it working?" in production. NOT for deploying the stack (/devops) or spend (/cost).
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/bpmforge/attest --skill analytics명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
Doc-driven implementation engineer. Reads SDLC design docs first, verifies all library APIs via Context7, then writes clean production code. Enforces anti-slop rules — no over-engineering, no defensive bloat, no hallucinated APIs. Use after design docs exist.
Gauntlet loop — multi-agent quality harness: a lead sets a real reference bar (a named product, test suite, or baseline to match or beat), splits the goal into gradeable units, builders produce artifacts in clean context, and blind fresh-per-round critics grade each artifact against the bar with evidence; failures loop until every unit passes, two rounds stall, or budget runs out. NOT /challenge (verifies factual claims); NOT /review (one-pass verdict) — this rebuilds until the work beats something real.
Image-quality gating and single-annotation tooling for captured screenshots (img-gate.mjs, annotate.mjs). Placeholder skill front door — T21.2 scope only.
SOC 직업 분류 기준
SKILL.md 표시 중
| name | analytics |
| description | Telemetry/instrumentation design — RED/USE/golden-signals selection, metrics catalog, event taxonomy, SLO-derived alerts, dashboard design. Use at Phase 3 or when nobody can answer "is it working?" in production. NOT for deploying the stack (/devops) or spend (/cost). |
Load and follow the instructions in the analytics-architect agent.
Usage:
/analytics — Full observability spec → docs/OBSERVABILITY.md/analytics --events — Product event taxonomy (object_action, versioned schemas)/analytics --dashboards — Per-audience dashboard plansRule: Methodology first — name RED, USE, or golden signals per service before listing any metric; every metric needs an owner-question.
Workflow: Classify services → Assign methodology → Derive metrics + budget cardinality → Define SLOs → Derive alerts → Design dashboards → Validate against validate-observability.sh