im-stuck
Skill2 starsChanged 15 days agoMITView on GitHub
Help a learner who is stuck or confused. Use when the learner types /im-stuck or seems lost or frustrated.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- Mozurok/fhorja.devtheir own version, first seen Oct 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- Mozurok/fhorja.dev★ 10same 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 repository4 other files it gives its agents.
- AGENTS.mdAGENTS.md
- my-progressSkill
- next-stepSkill
- start-courseSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Read workspace/progress.md and the current lesson script, including its Common sticking points section.
- Distinctive: line 10
Ask one short question to find out what they see on their screen right now.
- Distinctive: line 15
Never just do the step for them.
- Distinctive: line 17
If something broke (a file was deleted, a setting changed), help them recover calmly.
- Very specific: line 18
Add a line under "Notes" in progress.md recording where they got stuck.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
I'm stuck
- Read
workspace/progress.mdand the current lesson script, including its Common sticking points section. - Reassure them in one sentence. Getting stuck is normal and expected.
- Ask one short question to find out what they see on their screen right now.
- Give the smallest hint that gets them moving. Escalate only if needed:
- First: a hint ("look for the Explorer, the list of folders and files…"). Use labels from
lessons/SCREEN_GUIDE.md. - Then: the specific instruction.
- Last resort: walk them through it click by click.
Never just do the step for them.
If the screen itself is the problem ("I'm lost," "it's too much," "where did it go?"): tell them they only need three parts, the agent panel, the Explorer, and the editor, and that everything else can be ignored. Find the one they need. If they closed a panel, help them get it back using
lessons/SCREEN_GUIDE.md(for example, Ctrl+L / Cmd+L for the agent panel, the top icon on the edge strip for the Explorer).
- First: a hint ("look for the Explorer, the list of folders and files…"). Use labels from
- If something broke (a file was deleted, a setting changed), help them recover calmly.
- Add a line under "Notes" in
progress.mdrecording where they got stuck. Course authors use this to improve lessons.
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.

