guide
Skill4 starsChanged 4 months agoNo licenceView on GitHub
Walks the user through a known process step by step, the way a good mentor transfers a skill — not by explaining it, but by breaking it into a sequence the learner walks themselves. Use this skill whenever the user has a concrete destination in mind and needs the path there. Trigger on: "/guide", "how do I...", "walk me through...", "teach me...", "show me how to...", "what's the process for...", "guide me through...", or any prompt where the goal is doing something correctly, step by step, not deciding whether to do it or generating options for how. This is the behavioral counterpart to /brainstorm and /thinking: use /thinking when the prompt is "should I do X" (a decision to reason through), use /brainstorm when the prompt is "what are ways to do X" (multiple options to generate), use /guide when the prompt is "how do I do X" and there's one correct path to walk. When in doubt, if the user could physically or procedurally act on the output step by step, /guide is the right skill.
- Installs packages
20 other projects use a version of this.
Adopted by
Most recently taken up by
- cafe3310/public-agent-skillstheir own version, first seen Nov 8, 2026
- juanbermudez/skillstheir own version, first seen Nov 8, 2026
- Jasenpan1987/multi-codetheir own version, first seen Nov 8, 2026
- assisjp/specflowtheir own version, first seen Nov 1, 2026
- helderberto/agent-skillstheir own version, first seen Oct 13, 2026
- sangchane/claude-skillstheir own version, first seen Oct 13, 2026
Used with
Projects with it also use grill, plan and 5 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
renatorozasSkillgrill
Adversarial code review. Don't let me ship until the changes pass your scrutiny.
Also in 3 projects that use this
BlockSkillplan
Draft a TDD, PRD, or lightweight plan in the conversation without committing it.
Also in 3 projects that use this
SentrySkillreview
Fixture review skill.
Also in 4 projects that use this
Hugging FaceSkillimplement
Make tests pass. Invoke after /write-tests produces failing tests.
Also in 3 projects that use this
NVIDIASkillresearch
Before designing a feature, research how comparable libraries solve the problem, check best practices, known pitfalls, and upstream changes. Use when starting a new feature, investigating an unfamiliar area, or the user asks to research something.
Also in 3 projects that use this
VercelSkillsetup
Set up Vercel CLI and project configuration. Use when the user says "set up Vercel", "configure Vercel", "link to Vercel", or "vercel init".
Also in 3 projects that use this
Other versions20 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 20
- recharts/recharts★ 28ksame name
- cafe3310/public-agent-skills★ 256same name
- Senuto/nodeshub-seo-skills★ 40same name
- aleksander-dytko/ai-pm-workspace★ 34same name
- helderberto/agent-skills★ 19same name
- assisjp/specflow★ 17same name
- MEKO747/claude-code-skill★ 4same name
- NYTC69/review-loop★ 3same name
- leepokai/claude-code-guide★ 2same name
- spleenteo/maestro★ 2same name
10 more not listed
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.
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 6 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 15 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 15 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.
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
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.