Menu
Write an end-of-day log to your spoke vault. Use when session ends or user says "end of day" / "wrap up".
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
| name | daily-log |
| description | Write an end-of-day log to your spoke vault. Use when session ends or user says "end of day" / "wrap up". |
Write a daily log before your session ends.
DATE=$(date +"%Y-%m-%d")
SPOKE_VAULT="{spokeVaultPath}"
mkdir -p "$SPOKE_VAULT/daily-logs"
{spokeVaultPath}/daily-logs/YYYY-MM-DD.md---
date: YYYY-MM-DD
project: {project-name}
---
# {project-name} — Daily Log
## Completed
- [tasks completed today]
## In Progress
- [tasks still being worked on]
## Blocked
- [anything stuck]
## Key Decisions
- [important decisions made today]
## Tomorrow
- [what should be picked up next]
This log is read by the command session to generate the morning briefing. Keep it concise — bullet points, not paragraphs.
Complete captain playbook — session startup, crew spawning, status writing, group awareness, and learnings. Use this skill at session start and reference it throughout.
Set up and manage the squadrant↔Telegram integration — bot setup, remote control, command-menu registration, and per-project notification tuning (mute, crew tiers, cap). Use when the user asks about Telegram setup, "why don't commands work", registering the /command menu, or muting/tuning notifications.
Add, edit, or remove a leveled crew routing rule in config.json without hand-editing JSON. Routing rules map task-text keywords to a tier → {agent, model}.
Command playbook — invoked on-demand by `squadrant command [--task ...]`. Covers daily briefing, delegation workflow, project registration, status checking, and learnings review. Command is no longer always-on.
Reconcile squadrant config drift that needs human judgment — changed defaults and invalid values surfaced by `squadrant config check`. Use when the drift banner says "items need review" or the user asks to fix config drift.
Four coding principles derived from Andrej Karpathy's observations on LLM pitfalls. Use to reduce wrong assumptions, overengineering, drive-by refactors, and vague execution. Apply to every crew coding task and every captain review.