setup
Skill1 starsChanged 3 months agoMITView on GitHub
Configure jobkit for a new user - a six-question interview, then write their profile, search config and CV, generate the trackers, and prove it works on one real job. Use when someone asks to set this up, install it, onboard, configure it, get started, or says it is their first time using this repo.
192 other projects use a version of this.
Adopted by
Most recently taken up by
- openstory-so/openstorytheir own version, first seen Nov 16, 2026
- furkandvrc/conductortheir own version, first seen Nov 16, 2026
- futorio/red-greentheir own version, first seen Nov 16, 2026
- JCodesMore/jobs-for-ai-agentstheir own version, first seen Nov 16, 2026
- finolabs/finolabs-vibecodetheir own version, first seen Nov 16, 2026
- vincentventalon/claude-code-video-editing-skilltheir own version, first seen Nov 15, 2026
Used with
Projects with it also use add-atomic-chat-tool, add-dashboard and 10 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.
MicrosoftSkilladd-atomic-chat-tool
Add Atomic Chat MCP server so the container agent can call local models served by the Atomic Chat desktop app via its OpenAI-compatible API.
Also in 8 projects that use this
MicrosoftSkilladd-dashboard
Add a monitoring dashboard to NanoClaw. Installs @nanoco/nanoclaw-dashboard and a pusher that sends periodic JSON snapshots.
Also in 8 projects that use this
- +10 more from microsoft
Other versions192 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 192
- anthropics/knowledge-work-plugins★ 36ksame name
- garrytan/gbrain★ 33ksame name
- gavrielc/nanoclaw★ 31ksame name
- nanocoai/nanoclaw★ 31ksame name
- qwibitai/nanoclaw★ 31ksame name
- Q00/ouroboros★ 6.4ksame name
- pytorch/executorch★ 5.2ksame name
- aws/agent-toolkit-for-aws★ 3.5ksame name
- agenticnotetaking/arscontexta★ 3.5ksame name
- spotify/portal-ai-plugins★ 2.8ksame name
182 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.
In this repository4 other files it gives its agents.
- apply-to-jobSkill
- filter-jobsSkill
- find-jobsSkill
- follow-upsSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 169 edited versions we read keep these.
2
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 8
Follow BOOTSTRAP.md at the repo root.
- Distinctive: line 17
Show your work once, then go: After the questions, print one compact summary of everything you extracted and everything they told you, and …
- Distinctive: line 19
Not a confirmation per field.
- Very specific: line 26
If anything in BOOTSTRAP.md cannot be completed — a missing dependency they decline to install, a job board with no usable export — say so …
“Common” is measured: kept by at least 6 in 10 of the 169 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
Set up jobkit for this person
Follow BOOTSTRAP.md at the repo root. It is the full script and the single source of
truth for onboarding — read it now and work through its phases in order.
Three things that matter more than the rest, so they are repeated here:
Six questions, no more. Their CV carries their name, contact details, history, seniority, skills and often their languages. Read it and extract all of that. Asking someone to retype what you are already holding is what makes setup feel like paperwork.
Show your work once, then go. After the questions, print one compact summary of everything you extracted and everything they told you, and ask a single "anything wrong?". Not a confirmation per field.
Finish on a working example. The setup is not done when the files are written. It is done when a real job they chose has produced a one-page PDF and a list of contacts. A configured pipeline with nothing in it is a failed setup, and they will not find out until tomorrow.
If anything in BOOTSTRAP.md cannot be completed — a missing dependency they decline to
install, a job board with no usable export — say so plainly at hand-over and tell them what
still needs doing. Do not report success over a gap.
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.

