resume
Skill368 starsChanged 5 days agoMITView on GitHub
Pick up the forms that wait for the user and settle the ones that were clicked but not confirmed. Use when the user says /resume, "I typed the code", "I passed the check", "I signed in", "continue", or after a run that said forms are waiting.
64 other projects use a version of this.
Adopted by
Most recently taken up by
- optiflowic/keyturntheir own version, first seen Nov 16, 2026
- theraihanrakibb/agent-skillstheir own version, first seen Nov 16, 2026
- DeepExtrema/Tesseracttheir own version, first seen Nov 16, 2026
- kele-dev/Claude-Orchestrator-Skilltheir own version, first seen Nov 16, 2026
- netarz/gisoo-skills-registrytheir own version, first seen Nov 15, 2026
- kuldeep-jadeja/claude-handoff-plugintheir own version, first seen Nov 15, 2026
Used with
Projects with it also use pause, list and 8 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.
kennethleungtySkillpause
Pause — stop the music (alias for /stop)
Also in 6 projects that use this
SuShuhengSkilllist
Use when checking obshare-cli upload history, finding document tokens, or reviewing previous upload URLs and permission snapshots.
Also in 3 projects that use this
sahinSkillexecute
Also in 4 projects that use this
MicrosoftSkillnote
Use this skill to record progress, partial findings, hypotheses, and page-anchored evidence while investigating a long document. Call Note aggressively — any time you read a page and confirm, narrow, or update your understanding of the user's question. Triggers include "jot that down", "save this finding", "note that page 7 says X", or (more often) implicit internal signals — you just learned something and want it recoverable later. Notes persist in the session and Review can select among them. Never paraphrase notes back from memory; write them as you go.
Also in 3 projects that use this
GitHubSkillstate-management
CoreAI Sandbox's TanStack Query + mock-JSON data layer. USE WHEN: editing data-fetching hooks (`app/hooks/use*.ts`), adding mock data in `app/data/`, or wiring a component to query state.
Also in 3 projects that use this
u9401066Skillbug-fix
Structured bug fixing workflow with root cause analysis and regression prevention. Triggers: BF, 修 bug, fix bug, debug, 除錯, 錯誤, error, 問題, issue, 修復, fix, 故障, fault, 異常, exception, 失敗, failure, 不能用, broken, 壞掉.
Also in 3 projects that use this
Other versions64 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 64
- H-mmer/pentest-agents★ 815same name
- bitwize-music-studio/claude-ai-music-skills★ 668same name
- thesun4sky/jobstack★ 216same name
- EmeaAppGbb/spec2cloud★ 100same name
- saksham10arora-dotcom/everything-claude-codex★ 96same name
- thiagofinch/mega-brain★ 95same name
- nimadorostkar/Claude-Skills-collection★ 37same name
- junjiezhou1122/ideascientist-claude-code★ 35same name
- wrg32786/aigent-os★ 26same name
- Hassaan146/claude-skills★ 18same name
54 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
3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.
0
Common
Most of the 56 edited versions we read keep these.
1
Distinctive
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 16
Run npx jev status. If nothing waits and nothing is unconfirmed, say so and stop.
- Distinctive: line 46
Never read or type a code, never pass a check, never sign in.
- Very specific: line 48
Never use mark --status applied unless the user saw the confirmation.
“Common” is measured: kept by at least 6 in 10 of the 56 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.
Files
/resume
A form waits for the user when only they can do the next thing: type a code the board emailed, pass a robot check, finish a sign-in. It stays open in the tool's own Chrome window. They do that one thing there; this skill does the rest.
- Run
npx jev status. If nothing waits and nothing is unconfirmed, say so and stop. For forms that wait at a human check (a code, a robot check), run:
npx jev resumeIt watches each form while they finish it and records the application when the confirmation shows. Tell them which form it is on.
- For forms whose Submit was clicked with no confirmation seen, run
npx jev reconcile. If it cannot tell, ask them to look for the employer's confirmation email, then mark it withnpx jev mark <id> --status applied, or--status queuedto try again. A form that waits at a sign-in (the reason mentions a sign-in, a password, account terms or a verification link) is different: carrying on means the tool signs in at that employer. You do not start that. Show the command, which has a Run button:
npx jev resume --submit- Say what was sent, what still waits and why.
What you never do
- Never read or type a code, never pass a check, never sign in. The user does that in the tool's window; you only watch and record.
- Never use
mark --status appliedunless the user saw the confirmation.
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.

