context restore

Other Community v1.0.0

Skill notes

When to invoke this skill

Loads the most recent saved state (preferring the current branch, falling back across branches) so you can pick up where you left off — even across Conductor workspace handoffs. Use when asked to "resume", "restore context", "where was I", or "pick up where I left off". Pair with /context-save.

First-run guidance (one-time)

If ACTIVATED is no (first skill run on this machine) AND the preamble printed a non-empty FIRST_TASK: value that is NOT nongit: show ONE short, project-specific line mapped from the token, as a heads-up, then CONTINUE with whatever the user actually asked — do NOT halt their task.

Tool resolution (read first)

"AskUserQuestion" can resolve to two tools at runtime: the host MCP variant (e.g. mcp__conductor__AskUserQuestion — appears in your tool list when the host registers it) or the native Claude Code tool.

Format

Every AskUserQuestion is a decision brief and must be sent as tool_use, not prose — unless the documented failure fallback above applies (interactive session + the call is unavailable/erroring), in which case the prose fallback is the correct output. D-numbering: first question in a skill invocation is D1; increment yourself. This is a model-level instruction, not a runtime counter. ELI10 is always present, in plain English, not function names. Recommendation is ALWAYS present. Keep the (recommended) label; AUTO_DECIDE depends on it.

Handling 5+ options — split, never drop

AskUserQuestion caps every call at 4 options. With 5+ real options, NEVER drop, merge, or silently defer one to fit. Pick a compliant shape: Batch into ≤4-groups — for coherent alternatives (e.g. version bumps, layout variants). One call, 5th surfaced only if first 4 don't fit. Split per-option — for independent scope items (e.g. "ship E1..E6?").

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Other
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
92 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@garrytan · v1.0.0 · no license declared
Token usage
Heavy
Setup complexity
Guided setup
External API key
Not required
Operating systems
macOS
Runtime requirements
Bun
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
External requests
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Output preview context-restore.preview
# Writing Style (skip entirely if EXPLAINLEVEL: terse appears in the preamble echo OR the user's current message explicitly requests terse / no-explanations output)

- Gloss curated jargon on first use per skill invocation, even if the user pasted the term.
- Frame questions in outcome terms: what pain is avoided, what capability unlocks, what user experience changes.
- Use short sentences, concrete nouns, active voice.
- Close decisions with user impact: what the user sees, waits for, loses, or gains.
- User-turn override wins: if the current message asks for terse / no explanations / just the answer, skip this section.
- Terse mode (EXPLAIN_LEVEL: terse): no glosses, no outcome-framing layer, shorter responses.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.