Use when the work-journal app asks to write the end-of-day journal entry from the day's hour summaries, meetings, and category totals.
68
86%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
The canonical home for this skill is close-day in chandler767/WorkJournal
Headless skill for the work-journal app. The prompt names one input file.
JSON with day, hours, meetings, and totals (category to minutes).
{hour, narrative_lines, notes, main_focus, action_items}. narrative_lines is a short account of the hour, split into pieces to join with spaces; it may be absent or [] for older hours. notes carry the specifics.{id, title, start, end, participants, summary_lines, decisions, action_items}; join summary_lines with spaces to get its summary.notes (files, tickets, people, decisions) over generic phrasing when writing the Summary and Timeline.markdown must contain exactly these headings, in this order, each as ## level: ## Summary, ## Timeline, ## Time by category, ## Meetings, ## Action items, ## Open threads.totals only.None.None. under any section with no data. Add no other headings.{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"title": "close-day output",
"type": "object",
"additionalProperties": false,
"required": [
"markdown"
],
"properties": {
"markdown": {
"type": "string"
}
}
}chandler767/WorkJournal
28df817
Canonical home
since Oct 14, 2026
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.