agentleFS
Sign inStart free
attentiondotnetattentiondotnet/davidondrej-skills/skills/ops-and-setup/setup-help/SKILL.md

setup-help

Skill11 starsChanged 4 months agoMITView on GitHub

Walk the user through setting up anything step by step. Use when the user asks for help setting up, configuring, installing, or getting something working — "help me set up X", "walk me through this", "setup-help". Differentiator: gives one current step at a time, then always lists every remaining setup step after each response.

We split this skill into the rules it gives an agent

8 rules. 7 are common, 1 is distinctive, and 0 are very specific to this project.

  • 7

    Common

    Most of the 4 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Common:

    Before the first step, build a complete canonical checklist from the user's outline, repo/docs, current screen, and any discovered …

    line 21
  2. Common:

    If a new required step is discovered mid-setup, add it to Still remaining immediately in the correct order.

    line 23
  3. Common:

    Before every response, audit the current step plus Still remaining against the canonical checklist.

    line 24
  4. Distinctive:

    Only give instructions for the current step.

    line 25
  5. Common:

    Keep it concise. Short sentences.

    line 26
  6. Common:

    After the user finishes a step, move the next "remaining" item up to "Current step".

    line 27
  7. Common:

    Update the "Still remaining" list each time as steps get done.

    line 28
  8. Common:

    When nothing remains, say setup is complete instead of showing the list.

    line 29

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

setup-help

Guide the user through any setup, one step at a time, in plain English.

Response format (every single response)

  1. 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.
  2. A ---- divider.
  3. 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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free