메뉴
End-of-day retrospective dashboard of today's commits, quality, work status, and next steps. Use when the user wants a daily recap or retrospective. Triggers: daily, recap, 회고, 일일 보고, 오늘 작업, 오늘 뭐 했지, retrospective, daily report, 오늘 뭐 했는지 정리해줘, 일일 리뷰 해줘, 오늘 작업 요약해줘
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
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.
| name | daily |
| context | fork |
| disable-model-invocation | true |
| description | End-of-day retrospective dashboard of today's commits, quality, work status, and next steps. Use when the user wants a daily recap or retrospective. Triggers: daily, recap, 회고, 일일 보고, 오늘 작업, 오늘 뭐 했지, retrospective, daily report, 오늘 뭐 했는지 정리해줘, 일일 리뷰 해줘, 오늘 작업 요약해줘 |
| lang | ["en","ko"] |
| platforms | ["claude-code","gemini-cli","codex-cli","cursor"] |
| level | 2 |
| category | workflow |
| tokens | 1500 |
| agents | ["orchestrator","doc-updater"] |
| triggers | ["daily","recap","회고","일일 보고","오늘 작업","오늘 뭐 했지","retrospective","daily report"] |
| source_hash | 057eb7d4 |
| whenNotToUse | Mid-session task execution or detailed technical investigation — the daily skill is for end-of-day retrospective summaries, not real-time work tracking. |
오늘의 작업 흐름을 짧고 구조적으로 정리하는 일일 회고 스킬입니다.
다음과 같은 요청에서 사용합니다.
다음 6개 섹션을 기본 골격으로 사용합니다.
Progress:
- [ ] 오늘의 커밋 수집
- [ ] 품질 상태 확인
- [ ] 작업 현황 정리
- [ ] 주요 결정/메모 반영
- [ ] 다음 단계 우선순위 정리
- [ ] 최종 대시보드 출력
The following table captures common excuses agents make to skip the rigor of this skill, paired with factual rebuttals.
| Excuse | Rebuttal |
|---|---|
| "I remember what I did today" | memory decays within 24h — write it down while it is fresh |
| "the standup covers this" | standups capture tasks, not decisions or context — daily worklog is the durable record |
| "nothing worth reporting happened" | if nothing happened, document why — blockers count as work |
| "I will batch the whole week Friday" | Friday-you has forgotten Monday-you; daily cadence is the point |
| "the commit log is my worklog" | commits show code changes; worklog shows why and what was learned |