Help us improve
Share bugs, ideas, or general feedback.
From clotho
Use when the user says 'end of day', 'daily debrief', 'process today', 'what happened today', 'dump my day', 'debrief', or wants to capture everything from today into Clotho.
npx claudepluginhub colliery-io/clotho --plugin clothoHow this skill is triggered — by the user, by Claude, or both
Slash command
/clotho:daily-debriefThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
End-of-day ceremony. Your job is to get the user's entire day captured, structured, and linked in Clotho. You handle four phases: Intake, Status Update, Horizon Check, then launch the debrief-processor agent for extraction.
Mandates invoking relevant skills via tools before any response in coding sessions. Covers access, priorities, and adaptations for Claude Code, Copilot CLI, Gemini CLI.
Share bugs, ideas, or general feedback.
End-of-day ceremony. Your job is to get the user's entire day captured, structured, and linked in Clotho. You handle four phases: Intake, Status Update, Horizon Check, then launch the debrief-processor agent for extraction.
The workspace is set automatically. Use clotho_set_workspace if needed.
Scan .clotho/inbox/ for unprocessed files:
Use Bash to: ls -la <workspace_path>/.clotho/inbox/
If files exist, report what's there.
Query entities created today:
clotho_list_entities(entity_type: "Meeting")
clotho_list_entities(entity_type: "Transcript")
clotho_list_entities(entity_type: "Note")
Filter results to items with today's date in created_at.
Present to user:
"Here's what I already have from today: [list meetings/transcripts/notes]. Your inbox has N unprocessed files."
For each file in .clotho/inbox/:
clotho_capture(file_path, entity_type, title)Ask the user:
"Were there any other meetings or conversations today not captured above? You can:
- Paste a transcript or meeting summary
- Point me to a file
- Just tell me what happened and I'll capture it as a note"
For each material provided:
clotho_create_note(title, content) or clotho_create_entity(entity_type: "transcript", title, content)clotho_capture(file_path, entity_type)clotho_create_note(title: "EOD note: <topic>", content: <what they said>)Keep asking until the user says they're done.
Query active and pending tasks:
clotho_list_entities(state: "doing")
clotho_list_entities(state: "todo")
Present as a bulk list:
"Here are your active/pending tasks. What moved today?"
Doing:
- [title] (id)
- [title] (id)
Todo:
- [title] (id)
Tell me what changed: completed, blocked, started, or no change.
For each update the user provides:
clotho_update_entity(entity_id, state: "done")clotho_update_entity(entity_id, state: "blocked") + ask what's blocking, create Blocker entity + BLOCKED_BY relationclotho_update_entity(entity_id, state: "doing")Ask:
"Any decisions, risks, or blockers from outside meetings today?"
For each:
clotho_create_entity(entity_type: "decision", title)clotho_create_entity(entity_type: "risk", title)clotho_create_entity(entity_type: "blocker", title)Link to relevant programs if the user specifies context.
Query tasks with upcoming deadlines:
clotho_query(cypher: "MATCH (t:Task) RETURN t.id, t.title, t.entity_type")
Check metadata for deadline fields. Also:
clotho_list_entities(state: "todo")
Check created_at — flag any todo tasks older than 7 days as stale.
Check program health:
clotho_list_entities(entity_type: "Program")
For each program, check if it has any tasks updated in the last 2 weeks. Flag programs with no recent activity.
Present:
"Looking ahead:
- N items due this week
- M items due next week
- K tasks have been in todo for >7 days: [list]
- Program X has had no task activity in 2 weeks
Want to reprioritize anything or flag something?"
Handle any reprioritization the user requests.
Launch the debrief-processor agent. Pass it the context of which transcripts/notes from today haven't been extracted yet (no EXTRACTED_FROM relations pointing to them).
The agent will:
After the agent completes:
clotho_sync()