From Kestral
Use when the user asks for an end-of-day review, what got done or not done today, Kestral project updates, tomorrow priorities, or invokes /kestral:end-day-review or $kestral-end-day-review.
How this skill is triggered — by the user, by Claude, or both
Slash command
/kestral:end-day-reviewThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Produce an evidence-backed close-out for today and a practical priority list for tomorrow. Gather current context first,
Produce an evidence-backed close-out for today and a practical priority list for tomorrow. Gather current context first,
then ask before writing anything back to Kestral or local project files, except .kestral/preferences.md memory updates
covered by the User preferences rules.
The Kestral MCP server must be in this session (/mcp). Call whoami first — if it fails, ask the user to
reconnect or authenticate the Kestral MCP server in their app's MCP settings (a browser should open for sign-in).
Do not call other tools until authenticated.
Calendar access is optional, but use it when tomorrow prioritization depends on schedule realism.
Keep Kestral IDs internal unless the user asks for them. In user-facing output:
slug - title when a slug is available, linked with url when the host can render links.url when the host can render links.Unknown member (id: <rawId>).Unknown <entity type> (id: <rawId>).Expected invocations include:
/kestral:end-day-review$kestral-end-day-reviewDefault order:
~/.codex/sessions, Claude Code uses ~/.claude/projects, and other agents may use their
own local or hosted transcript stores..kestral/preferences.md by checking the current workspace folder and then parent folders. Use the first match
as the source for durable user close-out and tomorrow-planning preferences, not as task or project state.get_daily_brief.overview.md
or repo plan file.Do not treat one source as authoritative when it conflicts with fresher live state. Prefer exact Kestral entity state over generated summaries, and call out stale or unavailable sources.
Kestral searches to run when close-out needs verification:
tasks updated today <project name>urgent open tasks in <project name>blocked tasks <project name>documents updated today <project name>search_content (type: "knowledge") for current blockers, next steps, and progressCalendar searches should use explicit local-day RFC3339 bounds for tomorrow. If calendar access is missing or empty, do not infer a free day; state the gap.
Run independent reads in parallel whenever the host supports it: local preferences, daily brief, agent session searches, remote GitHub reads, broad Kestral searches, and tomorrow's calendar query do not need to block one another. Do not parallelize dependent lookups; fetch exact entities only after search results identify the relevant IDs.
Treat .kestral/preferences.md as a local memory file for durable review and prioritization preferences. Find it by
walking upward from the current workspace folder and using the first match.
.kestral/preferences.md silently when a durable preference is clear. This is local memory maintenance, not a
Kestral write-back..kestral/ and preferences.md in the current workspace folder if no parent preference file exists and a
preference write is needed. Keep the file short, in Markdown, and update existing bullets instead of appending
duplicates.Build a compact evidence list before summarizing:
overview.md or project docs that are relevant to surfaced projects or updates.Keep raw session review targeted. Search for today's user messages, final answers, tool calls, project names, task IDs, PR URLs, commit SHAs, branch names, and write-back actions instead of reading every token linearly. If transcript search or session context is unavailable, state the gap and continue from live Kestral, git, GitHub, and available local project evidence.
Separate confirmed outcomes from attempted or pending work:
Use concrete project/task/document names and dates. Avoid vague claims like "made progress" unless the specific artifact is named.
For each relevant project:
overview.md
maintenance.If generated Project Brain knowledge appears stale, say that explicitly and base recommendations on live entities.
Rank tomorrow's work by impact, urgency, unblock value, and calendar realism:
If Calendar is available, fit priorities around known meetings and preserve buffer. If Calendar is unavailable, label the plan as task-priority-only and ask for fixed commitments if needed.
Never write back automatically. Present a specific write-back plan and wait for user approval.
Valid write-backs:
overview.md in the relevant project folder.overview.md if the target project folder has no overview file and the folder is a local draft/project
workspace.For each proposed write, include target, action, and exact content summary. For task changes, include priority/status/due
date values. For document or overview.md edits, include the section names that will be changed.
After approval, apply only the approved writes. Return links for Kestral mutations and file paths for local edits.
Preference-memory updates to .kestral/preferences.md are separate from Kestral/local write-backs. Apply them silently
under the User preferences rules when durable preferences are clear; mention the local file path only if useful.
Use this structure unless the user asks for something else:
## Done Today
- ...
## Not Done
- ...
## Project Brain / Project Updates
- ...
## Tomorrow Priorities
1. ...
2. ...
3. ...
## Recommended Write-Backs
- [human-readable target] [action] - [summary]
Approve these write-backs?
If the user already approved a specific write-back plan, replace the final question with a concise result list.
slug - title for tasks and readable names/titles for projects, documents, feedback, customers, statuses, tags, and members..kestral/preferences.md memory
updates covered by the User preferences rules.overview.md structure when updating local project folders.Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.
npx claudepluginhub kestral-team/kestral-plugins --plugin kestral