setup-help
Skill1.5k starsChanged 6 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.
5 other projects use a version of this, 1 of them edited.
Adopted by
Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data
Most recently taken up by
- davidondrej/cloudroom-coreword for word, first seen Nov 1, 2026
- davidondrej/skillsword for word, first seen Oct 29, 2026
- cill-i-am/skillstheir own version, first seen Oct 20, 2026
- cyxar4uk/ya360-mcptheir own version, first seen Sep 27, 2026
- attentiondotnet/davidondrej-skillsedited, first seen Jul 7, 2026
Who's talking about davidondrej/cloudroom
- sudosubin/agents.nix“agent-skills.github.davidondrej.cloudroom: 03ddb1c → 112f097”GitHub · Nov 10, 2026
- sudosubin/agents.nix“agent-skills.github.davidondrej.cloudroom: 0-unstable-2026-11-08 → 0-unstable-2026-11-10”GitHub · Nov 10, 2026
- sudosubin/agents.nix“agent-skills.github.davidondrej.cloudroom: 99252ed → 2d0f828”GitHub · Nov 9, 2026
- sudosubin/agents.nix“agent-skills.github.davidondrej.cloudroom: 0-unstable-2026-11-07 → 0-unstable-2026-11-08”GitHub · Nov 8, 2026
- Ceoloo/aion-forge“Forge future UX — Safe code review, private previews and governed session transfer”GitHub · Nov 7, 2026
The biggest 5 of 25 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 25
Talked about on GitHub (25 times).
On GitHub · 25
- Nov 10, 2026agent-skills.github.davidondrej.cloudroom: 03ddb1c → 112f097 — sudosubin/agents.nix0 reactions
- Nov 10, 2026agent-skills.github.davidondrej.cloudroom: 0-unstable-2026-11-08 → 0-unstable-2026-11-10 — sudosubin/agents.nix0 reactions
- Nov 9, 2026agent-skills.github.davidondrej.cloudroom: 99252ed → 2d0f828 — sudosubin/agents.nix0 reactions
- Nov 8, 2026agent-skills.github.davidondrej.cloudroom: 0-unstable-2026-11-07 → 0-unstable-2026-11-08 — sudosubin/agents.nix0 reactions
- Nov 7, 2026Forge future UX — Safe code review, private previews and governed session transfer — Ceoloo/aion-forge0 reactions
20 more on GitHub
- Nov 7, 2026Forge v0.4 — Durable coding session lifecycle, queue and isolated Git workspaces — Ceoloo/aion-forge0 reactions
- Nov 7, 2026Forge Control Room v0.4 — Runtime-backed read-only session and workspace dashboard — Ceoloo/aion-forge0 reactions
- Nov 7, 2026agent-skills.github.davidondrej.cloudroom: e735f22 → becdfa7 — sudosubin/agents.nix0 reactions
- Nov 7, 2026agent-skills.github.davidondrej.cloudroom: 0-unstable-2026-11-06 → 0-unstable-2026-11-07 — sudosubin/agents.nix0 reactions
- Nov 6, 2026agent-skills.github.davidondrej.cloudroom: 0-unstable-2026-11-05 → 0-unstable-2026-11-06 — sudosubin/agents.nix0 reactions
- Nov 5, 2026agent-skills.github.davidondrej.cloudroom: 0-unstable-2026-11-04 → 0-unstable-2026-11-05 — sudosubin/agents.nix0 reactions
- Nov 4, 2026agent-skills.github.davidondrej.cloudroom: 0-unstable-2026-11-03 → 0-unstable-2026-11-04 — sudosubin/agents.nix0 reactions
- Nov 3, 2026Onde roda e ajudantes remotos (D235/D238) — gavasques/my-dexter-bot0 reactions
- Nov 3, 2026agent-skills.github.davidondrej.cloudroom: 0-unstable-2026-11-02 → 0-unstable-2026-11-03 — sudosubin/agents.nix0 reactions
- Nov 2, 2026agent-skills.github.davidondrej.cloudroom: 0.1.92 → 0-unstable-2026-11-02 — sudosubin/agents.nix0 reactions
- Nov 2, 2026execution model: Cloudroom options — what each feature would look like here (no adoption decision) — talos-hq/hermes-slim0 reactions
- Nov 2, 2026agent-skills.github.davidondrej.cloudroom: 0.1.91 → 0.1.92 — sudosubin/agents.nix0 reactions
- Nov 1, 2026agent-skills.github.davidondrej.cloudroom: 0.1.90 → 0.1.91 — sudosubin/agents.nix0 reactions
- Nov 1, 2026agent-skills.github.davidondrej.cloudroom: 0.1.89 → 0.1.90 — sudosubin/agents.nix0 reactions
- Oct 31, 2026agent-skills.github.davidondrej.cloudroom: 0.1.88 → 0.1.89 — sudosubin/agents.nix0 reactions
- Oct 31, 2026agent-skills.github.davidondrej.cloudroom: 0.1.87 → 0.1.88 — sudosubin/agents.nix0 reactions
- Oct 30, 2026agent-skills.github.davidondrej.cloudroom: 0.1.86 → 0.1.87 — sudosubin/agents.nix0 reactions
- Oct 30, 2026agent-skills.github.davidondrej.cloudroom: 0.1.85 → 0.1.86 — sudosubin/agents.nix0 reactions
- Oct 29, 2026agent-skills.github.davidondrej.cloudroom: 0.1.83 → 0.1.85 — sudosubin/agents.nix0 reactions
- Oct 29, 2026agent-skills.github.davidondrej.cloudroom: init at 0.1.83 — sudosubin/agents.nix0 reactions
Other versions5 projects use a version of this.
Word for word · 2
- davidondrej/skills★ 4.3k100% same
- davidondrej/cloudroom-core★ 1.5k100% same
Edited · 1
- attentiondotnet/davidondrej-skills★ 1168% same
Wrote their own version · 2
- cyxar4uk/ya360-mcp★ 2same name
- cill-i-am/skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository8 other files it gives its agents.
- AGENTS.mdAGENTS.md
- adr-verbatimSkill
- browser-harnessSkill
- create-loopSkill
- decisionsSkill
- file-treeSkill
- risky-changesSkill
- self-archiveSkill
The file
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
- Distinctive: line 21
Before the first step, build a complete canonical checklist from the user's outline, repo/docs, current screen, and any discovered …
- Distinctive: line 23
If a new required step is discovered mid-setup, add it to Still remaining immediately in the correct order.
- Distinctive: line 24
Before every response, audit the current step plus Still remaining against the canonical checklist.
- Distinctive: line 25
Only give instructions for the current step.
- Distinctive: line 26
Keep it concise. Short sentences.
- Distinctive: line 27
After the user finishes a step, move the next "remaining" item up to "Current step".
- Distinctive: line 28
Update the "Still remaining" list each time as steps get done.
- Distinctive: line 29
When nothing remains, say setup is complete instead of showing the list.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.
Files
setup-help
Guide the user through any setup, one step at a time, in plain English.
Response format (every single response)
- 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.
- A
----divider. - 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.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.

