Claude advisor tool strategy for cost-optimized quality retention. Sonnet executor + Opus advisor pattern reduces API cost by ~50% while maintaining near-Opus quality on complex judgment calls. Auto-activates when discussing model cost optimization, executor-advisor delegation, or advisor API integration. Triggers: advisor, cost optimization, model strategy, executor-advisor, advisor tool
Use when creating or editing a SKILL.md. 자연어 트리거: '스킬 만들어줘', '새 스킬 추가', '스킬 작성해줘', 'skill 만들기', '스킬 프론트매터 고쳐줘', 'create a skill', 'edit SKILL.md'.
로컬 관측성(observability) 스킬 — Claude Code hook 이벤트를 JSONL 큐로 fan-out하고 localhost WebSocket 브로드캐스트로 대시보드에 노출. 외부 전송 0건, Artibot 내부 전용. Auto-activates when: building a local hook monitor, an on-device agent dashboard, or an observability surface. Triggers: hook monitor, agent dashboard, event tap, local telemetry, claude code hooks, 훅 모니터, 이벤트 대시보드, 관측성.
Distill a person, role, or character into a reusable persona skill via the 6-layer schema. Use when the user wants to compile a colleague, an internal role archetype, or an authoring style into a persona-* skill — not when invoking an existing persona.
프롬프트 캐시 최적화 전략 — Dynamic Boundary 배치, 토큰 예산 관리, 정적·동적 영역 분리. 자연어 트리거: '프롬프트 캐시 최적화해줘', '토큰 예산 관리', '캐시 효율 높여줘', 'CLAUDE.md 레이아웃 정리'.
Dynamic tool approval predicates and the bash command allowlist. Use when the user asks about HITL approvals or tightening the pre-bash gate. Triggers: tool approval, approval predicate, bash allowlist, pre-bash, permission gate, HITL.
Coding standards and style guide enforcing immutability, error handling, file organization, and naming conventions. Auto-activates when: writing or modifying code, code review, creating new files or components. Triggers: code, write, edit, implement, component, function, class, style, 코드 작성, 코딩 스타일, 코드 리뷰, 구현, 컴포넌트, 함수
Auto-activates when the user asks to improve, enhance, audit, or propose changes without specifying a concrete problem — especially "개선", "보완", "발전방안", "제안", "감사", "전수조사", "업그레이드", "더 좋게", "추가하면 좋을", "enhance", "improve", "propose", "audit", "optimization", YAGNI, over-engineering, "필요한가", "어떻게 하면 더 좋아질까", "무엇을 더 보강할 수 있을까", "개선안 좀 찾아봐". Also fires when a candidate list of proposals exists and none has been cross-checked against live code evidence yet.