Setup Walkthrough
Use when the owner must do a setup by hand: walk them through it one step at a time, never a wall.
Install
npx skills add SamueleBassoli/hermes-fleet-apps --skill setup-walkthroughgit clone --depth 1 https://github.com/SamueleBassoli/hermes-fleet-apps.git /tmp/hermes-fleet-apps
mkdir -p ~/.claude/skills
cp -r /tmp/hermes-fleet-apps/roles/coder/skills/setup-walkthrough ~/.claude/skills/setup-walkthroughPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Setup Walkthrough Use when the owner has to do something themselves in a UI, a dashboard, an installer, or a config file — and specifically when they must type a key, token, or password, which the coder never handles. Assume the owner is busy and not a developer. A 20-step wall makes them close the window. One step at a time, with the end always in sight, does not. **Not this skill when the walk is repeatable.** If the owner will do this same setup again — on another machine, or after a rebuild — build a script with the `wizard` skill instead of walking it by hand a second time. ## Response format — every single response, no exceptions ``` <CURRENT STEP> One coherent step. 1-4 short lines. Every value they need, spelled out. Group fields from the same screen or form together - do not split one form into four micro-steps. ---- STILL REMAINING 1. <headline> 2. <headline> 3. <headline> ``` Remaining items are **headlines only** — a few words each. No commands, no URLs, no values, no explanation. That detail appears only when the item becomes the current step. ## Rules - Build the full checklist **before** the first step: from the owner's outline, the repo, the docs, the screen they are on, and any prerequisite you discover. Keep it internally; never show the whole thing. - **Never more than 8 items in STILL REMAINING.** More is a wall. If more than 8 remain, show the nearest steps individually and merge the later ones into
Details
- Skill name
setup-walkthrough- Repository
- SamueleBassoli/hermes-fleet-apps
- Path
roles/coder/skills/setup-walkthrough/SKILL.md- License
- MIT
- Repo updated
- 31 October 2026
FAQ
What does the Setup Walkthrough skill do?
Use when the owner must do a setup by hand: walk them through it one step at a time, never a wall.
How do I install the Setup Walkthrough skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add SamueleBassoli/hermes-fleet-apps --skill setup-walkthrough. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Setup Walkthrough popular?
It lives in SamueleBassoli/hermes-fleet-apps, which has 44 GitHub stars and 0 forks.
Related skills
Agent Facing CLI
44SamueleBassoli/hermes-fleet-apps
Use when an agent will drive a CLI. Contract test first.
Agent Fleet Design
44SamueleBassoli/hermes-fleet-apps
Use when adding, backing up, or driving the agent fleet.
Agent Identity Setup
44SamueleBassoli/hermes-fleet-apps
Use when setting up or resetting agent SOUL, memory, skills.
Wizard
44SamueleBassoli/hermes-fleet-apps
Use when setup needs human hands. Builds a bash wizard.
Production Install
44SamueleBassoli/hermes-fleet-apps
Use when a dev tool meets the owner's real data. Pin, isolate.
Ceo Review
430xranx/agentbrief
When reviewing product decisions, feature scope, or user-facing changes from a founder/CEO perspective. Use when the user says 'does this make sense,' 'should we build this,' 'review the product,' 'is this good enough,' 'founder review,' 'product sense check,' or before any significant launch. This is the strategic taste layer — not engineering quality, but product quality.
Browse the most popular Claude skills, all other skills, or write your own with the skills generator.