Menu
This skill should be used when preparing a pickup checklist when starting a task, rehydrating context from the latest handoff note if available.
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
Use this skill when the user wants to test a business idea, strategy, or initiative against real-world risk. Triggers include: 'test my idea', 'what are the riskiest assumptions', 'help me validate this', 'run EMT on this', 'extract assumptions', 'assumption mapping', 'what could go wrong with this plan', 'pressure test this', 'validate this plan', 'what could go wrong with this strategy', 'identify hidden risk in this idea', or any request to pressure-test a business decision before committing resources. Runs a guided Extract → Map → Test system based on David J. Bland's Precoil methodology.
Calibrate an LLM judge against human labels using data splits, TPR/TNR, and bias correction. Use after writing a judge prompt (write-judge-prompt) when you need to verify alignment before trusting its outputs. Do NOT use for code-based evaluators (those are deterministic; test with standard unit tests).
Generate beautiful, self-contained HTML pages that visually explain systems, code changes, plans, and data. Use when the user asks for a diagram, architecture overview, diff review, plan review, project recap, comparison table, or any visual explanation of technical concepts. Also use proactively when you are about to render a complex ASCII table (4+ rows or 3+ columns) — present it as a styled HTML page instead.
This skill should be used when shaping a software change and needing to breadboard the solution at the right level of abstraction (places, affordances, connections), including mapping an existing system via UI + code affordances, producing a wiring diagram, a parts/BOM plan, a fit check, and (when relevant) an extract-vs-duplicate analysis.
Clarify requirements before implementing. Do not use automatically, only when invoked explicitly.
This skill should be used when a user needs a demo package that starts with a live demo (not slides) and produces both a demo script and a navigable single-file HTML runbook, including caveats, respectful competitive comparison, and LLM architecture details (RAG, evals, observability).
| name | pickup |
| description | This skill should be used when preparing a pickup checklist when starting a task, rehydrating context from the latest handoff note if available. |
Purpose: rehydrate context quickly when you start work.
<dossier>/tmp-handoffs/handoff_*.mddocs/04-projects/**/tmp-handoffs/handoff_*.mddocs/98-tmp/handoffs/handoff_*.mdpnpm run docs:list if present).git status -sb; check for local commits; confirm current branch/PR.gh pr view <num> --comments --files (or derive PR from branch) and note failing checks.tmux list-sessionstmux attach -t codex-shell or tmux capture-pane -p -J -t codex-shell:0.0 -S -200handoff, start a new thread, then run pickup.