status
Skill368 starsChanged 5 days agoMITView on GitHub
Say where the job search stands in a few lines. Use when the user says /status, "where am I", "what happened", "how many did I send", "what is waiting for me", or "what does this cost".
188 other projects use a version of this.
Adopted by
Most recently taken up by
- deg/beads-utilstheir own version, first seen Nov 16, 2026
- mahirhacks/mstacktheir own version, first seen Nov 16, 2026
- arxdsilva/ai-loopstheir own version, first seen Nov 16, 2026
- mategog/dev-teamtheir own version, first seen Nov 16, 2026
- ibra-zhan/reazontheir own version, first seen Nov 16, 2026
- kele-dev/Claude-Orchestrator-Skilltheir own version, first seen Nov 16, 2026
Used with
Projects with it also use off, list and 9 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.
StakeholderSenseiSkilloff
Disable polygraph for this repo (user-only escape hatch; all hooks no-op)
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 8 projects that use this
kennethleungtySkillpause
Pause — stop the music (alias for /stop)
Also in 7 projects that use this
MistralSkillimport
Import the user's setup from other coding CLIs (Claude Code, Codex, OpenCode) into Vibe — instructions, skills, subagents, commands, hooks, MCP servers, permissions, and plugins. Load when the user wants to switch to Vibe, import or reuse another CLI's configuration, or asks whether a file from another CLI works in Vibe.
Also in 6 projects that use this
codebycoreySkillnew
Start a new change with a proposal. Use when starting a feature, creating a proposal, or beginning planned work.
Also in 7 projects that use this
VercelSkillnext
Next.js renderer for json-render that turns JSON specs into full Next.js applications with routes, layouts, SSR, and metadata. Use when working with @json-render/next, building Next.js apps from JSON specs, or creating AI-generated multi-page applications.
Also in 11 projects that use this
Other versions188 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 188
- anthropics/claude-for-legal★ 9.5ksame name
- microsoft/TokenEconomizer★ 6.2ksame name
- zereight/gitlab-mcp★ 2.1ksame name
- indranilbanerjee/digital-marketing-pro★ 934same name
- H-mmer/pentest-agents★ 815same name
- emotixco/claude-skills-founder★ 796same name
- me2resh/apexyard★ 542same name
- dsifry/metaswarm★ 432same name
- ffroliva/gflow-cli★ 396same name
- serithemage/serverless-openclaw★ 196same name
178 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
2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.
0
Common
Most of the 157 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Run these and give one short answer, not four dumps:
- Very specific: line 34
Never print a path, an id or a number they did not ask for when a sentence will do.
“Common” is measured: kept by at least 6 in 10 of the 157 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
/status
Run these and give one short answer, not four dumps:
npx jev status
npx jev doctor
npx jev cost
npx jev schedule statusSay, in this order and only what applies:
- Sent: today and in total.
- Waiting for you: each form, what it asks for, and that
/resumepicks it up after they have done it in the tool's Chrome window. - Left for you: how many are on the by-hand list, and the two or
three most common reasons.
npx jev log --manuallists them. - Queue: how many jobs are ready to apply to, and how old the search
is. Offer
/discoverwhen it is more than a day old. - Accounts and the daily run: one line each, only if set up.
- Cost: what JEV has cost. Claude runs on their subscription.
- Next step: the one thing
doctornames, as a slash command where there is one (/setup,/discover,/apply,/accounts,/daily,/resume,/report).
Never print a path, an id or a number they did not ask for when a sentence
will do. /report is the full picture, in a page.
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.

