Menu
{{SKILL_DESCRIPTION}}
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Generates a complete eval.json for a Claude Code skill via 2-pass pipeline — local draft with Ollama (qwen2.5-coder:14b, $0, ~3min) then Sonnet refinement (claude -p headless, $0 via Max subscription). Launches final verify-eval for validation. Use when you want to cover a skill that doesn't yet have an eval.json, or in batch across multiple skills. Target: increase coverage of the skill auto-evaluation loop (ticket auto-evals-binaires-evaluateskills). Ex: /author-eval closeweek, /author-eval (no arg → interactive list), /author-eval --random 5 (batch).
End-of-day wrap-up — synthesize sessions, update daily note with observed patterns, detect WIP hobby in progress, verify essay-check overdue. Trigger when the user says one of these phrases: "closeday", "I'm stopping", "I'm done", "that's finished", "end of session", "good night", "good day", "stopping for today", "that's enough", "day finished", "I'm stopping now", "it's done" or via /closeday.
Guided commit on explicit request /commit — breaks changes into atomic commits ordered by layer, passes two validations (file selection, then message), handles branch (creation/switch with stash), then executes git add + git commit. Use whenever the user says /commit, 'commit that', 'make the commit', or wants to commit finished work. Never push, merge, rebase or reset EVER. Never commit outside this skill.
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
Scan the daily notes to extract ideas to capitalize on and links to process. Use when the user says "harvest", "do the harvest", "scan my notes", or when /harvest is late in the command-tracker, or at the end of a session if daily notes have been mentioned.
Complete vault scan over an extended period to detect emerging patterns, recurring ideas across different contexts, and deep connections. Use once a month or when the user says "harvest deep", "deep harvest", "analyze the vault".
| name | {"[object Object]":null} |
| description | {"[object Object]":null} |
{{SKILL_DESCRIPTION}}
<Describe what the skill does, step by step. Keep steps imperative and concrete.
Reference any sibling template file as template-*.md in this skill's folder.>
