Guide users through multi-step setup one action at a time
Guides a user through multi-step setup one atomic action at a time, with a Still Remaining list capped at 8 items.
Why it matters
Help users complete complex installations, configurations, and setup workflows by breaking them into single atomic actions and providing step-by-step guidance with clear progress tracking.
Outcomes
What it gets done
Break down setup procedures into one atomic action per step
Maintain a canonical checklist and surface the next 8 remaining steps
Adapt the remaining task list as new prerequisites are discovered
Confirm completion when all setup steps are finished
Install
Add it to your toolbox
Run in your project directory:
curl -fsSL https://spark.entire.vc/get/ag-setup-help | bash Overview
Setup Help
Guides a user through any multi-step setup one atomic action at a time - one click, field, or command per response - with a numbered Still Remaining list capped at 8 items. Use it when the user asks to set up, install, or configure something with multiple steps. Only give instructions for the current step, never jump ahead.
What it does
Guides a user through any multi-step setup, install, or configuration process one step at a time, in plain English. Before the first step it builds a complete canonical checklist from the user's outline, repo or docs, the current screen, and any discovered prerequisites, then walks through it step by step: every single response gives exactly one atomic action - a single click, field, or command, 1-2 lines max, never a checklist - followed by a ---- divider and a numbered "Still remaining" list capped at 8 items. If more than 8 checklist items remain, the nearest steps show individually while later ones merge into broader phase-level items, without ever silently dropping a required step from internal tracking. If a new required step is discovered mid-setup, it's inserted into "Still remaining" immediately in the correct order, and before every response the current step plus "Still remaining" are audited against the canonical checklist and corrected if anything unfinished is missing.
When to use - and when NOT to
Use it when the user asks to set up, install, configure, or get something working step by step, especially when the setup has multiple steps and benefits from one-at-a-time guidance. Only give instructions for the current step - never jump ahead - and once the user finishes a step, move the next remaining item up to "Current step" and update the list. When nothing remains, say the setup is complete instead of showing an empty list. Being adapted from a third-party skill, verify local paths, tools, credentials, and agent features before acting, and for any commands, remote access, scheduling, browser automation, or file-changing workflows it triggers, get explicit user approval and confirm the target environment first.
Who it's for
Anyone walking a user through an install or configuration process with several steps, who wants concise, single-action guidance instead of a wall-of-text checklist - short sentences, no filler, one atomic step at a time.
Source README
setup-help
When to Use
- Use when the user asks to set up, install, configure, or get something working step by step.
- Use when the setup has multiple steps and benefits from one-at-a-time guidance.
Guide the user through any setup, one step at a time, in plain English.
Response format (every single response)
- Current step - ONE atomic action. A single click, field, or command - not a checklist. 1-2 lines max. If it needs sub-steps, it's too big: split it and push the rest into "Still remaining". Plain English.
- A
----divider. - Still remaining - a numbered list of the setup steps left after this one. Max 8 items, ever.
Repeat this format for every response until setup is done.
Rules
- Before the first step, build a complete canonical checklist from the user's outline, repo/docs, current screen, and any discovered prerequisites.
- The Still remaining list must never exceed 8 items - more is overwhelming. Track ALL unfinished checklist items internally; if more than 8 remain, show the nearest steps individually and merge the later ones into broader phase-level items so the list stays at 8 or fewer. Never silently drop a required step from internal tracking.
- If a new required step is discovered mid-setup, add it to Still remaining immediately in the correct order.
- Before every response, audit the current step plus Still remaining against the canonical checklist. If any unfinished step is missing, fix the list before replying.
- Only give instructions for the current step. Do not jump ahead.
- Keep it concise. Short sentences. No filler.
- After the user finishes a step, move the next "remaining" item up to "Current step".
- Update the "Still remaining" list each time as steps get done.
- When nothing remains, say setup is complete instead of showing the list.
Limitations
- Adapted from
davidondrej/skills; verify local paths, tools, credentials, and agent features before acting. - For commands, remote access, scheduling, browser automation, or file-changing workflows, get explicit user approval and confirm the target environment first.
Discussion
Questions & comments · 0
Sign In Sign in to leave a comment.