agentleFS
Sign inStart free
davidondrejdavidondrej/cloudroom-core/skills/setup-help/SKILL.md

setup-help

Skill1.2k starsChanged 4 days agoApache-2.0View on GitHub

Guide setup one step at a time and show what remains. Use only when the user explicitly asks for it by name.

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 8 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    Distinctive · estimate

    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. Distinctive:

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

    line 21
  2. Distinctive:

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

    line 23
  3. Distinctive:

    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. Distinctive:

    Keep it concise. Short sentences.

    line 26
  6. Distinctive:

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

    line 27
  7. Distinctive:

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

    line 28
  8. Distinctive:

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

    line 29

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “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 coherent setup step. Group tightly related actions and fields from the same form or screen, and provide every value the user needs to complete them. Use 1–4 concise lines. Split only at a real decision, verification point, or screen change.
  2. A ---- divider.
  3. Still remaining — a numbered list of the setup steps left after this one. Max 8 items, ever. Each item is a HEADLINE only: a few words, easy to glance at. No commands, URLs, event names, values, or explanations — that detail appears only when the item becomes the Current step.

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. Never split one obvious form or tightly related field group into micro-steps; optimize for fewer handoffs. Keep the remaining list headline-only.
  • 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)

Trending

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Aug 30: 0 new projectsWeek of Sep 6: 0 new projectsWeek of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projects
Aug 2026Sep 2026Oct 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Who's talking about davidondrej/cloudroom-core

The biggest 5 of 32 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 32

Talked about on GitHub (32 times).

On GitHub · 32

27 more on GitHub

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