setup
Skill368 starsChanged 5 days agoMITView on GitHub
First-run setup, start to finish. Use when the user says /setup, "set this up", "get me started", "help me use this", hands you this repository for the first time, or when data/profile.json does not exist. Installs what is missing, builds the profile from the resume and a short interview, has the user add their own JEV key (TypeSafe or OpenRouter), finds jobs, rehearses, and stops for a "go" before anything is sent.
- Reads credentials
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.
The file
Show its rules and text
We split this skill into the rules it gives an agent
25 rules. 0 are common, 9 are distinctive, and 16 are very specific to this project.
0
Common
Most of the 169 edited versions we read keep these.
9
Distinctive
This author's own choices. Worth a look.
16
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 13
Run every command from the repo root.
- Very specific: line 20
If node_modules is missing, run npm install.
- Very specific: line 21
Run npx jev doctor. Fix what it names, in order:
- Very specific: line 31
Look in documents/ first. Besides resume.pdf, a user may have put past material there for you to read: old resumes, a LinkedIn profile …
- Distinctive: line 42
Ask for the resume as a PDF.
- Distinctive: line 45
Read the PDF. It is your first source for the profile.
- Distinctive: line 54
Ask the user what the resume does not state.
- Distinctive: line 57
Ask in small groups, at most four questions at a time.
- Very specific: line 59
Write summary (three or four sentences: who they are, what they want, where, when) and facts (one line per claim, every number exact, …
- Very specific: line 62
Write answers, the standing answers, from part G of the questions.
- Very specific: line 64
Run doctor again. A schema error names the field to fix.
- Distinctive: line 68
Never invent or round a fact.
- Distinctive: line 69
Never guess a demographic answer.
- Very specific: line 77
Write data/bank.json in the shape of data/bank.example.json: one starting draft per common question, from the user's own facts.
- Distinctive: line 92
Ask them to create a key and add a few dollars of credit, at either https://console.typesafe.ai/keys (TypeSafe, who make JEV) or …
- Very specific: line 96
Run cp .env.example .env, then open -e .env so the file opens in a text editor.
- Very specific: line 98
Ask them to paste a TypeSafe key after TYPESAFE_API_KEY=, or an OpenRouter key after OPENROUTER_API_KEY=, save, and tell you when it is …
- Very specific: line 101
Run npx jev doctor --online.
- Distinctive: line 104
Never ask the user to paste the key into the chat, and never print it.
- Very specific: line 110
Run npx jev discover. It takes about a minute.
- Very specific: line 115
If the user wants other locations or kinds of roles than the ranking prefers, the settings are in src/config.ts (LOCATION_MULTIPLIER, …
- Very specific: line 121
Run npx jev apply --dry --count 3.
- Distinctive: line 149
Do not list commands. Say only:
- Very specific: line 159
If many of the jobs they would want are on Workday (npx jev status lists "workday" among the skip reasons), say that Workday employers each …
- Very specific: line 162
If they asked for it to run by itself, /daily.
“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
/setup: from a fresh clone to the first applications
The user should need to do four things: give you their resume, answer your questions, paste one key into a file, and say "go". You do everything else.
Run every command from the repo root. After each step run
npx jev doctor --json. It lists what is in place and names the
next thing to do, so you never have to guess where you are. If the user
stops halfway and comes back, start from what doctor says.
1. Install
- If
node_modulesis missing, runnpm install. - Run
npx jev doctor. Fix what it names, in order:- Node.js older than 22, Google Chrome missing, or Claude Code missing:
tell the user what to install and wait. You cannot install these.
(You are running inside Claude Code, so it is present; a user who
prefers a Claude API key can add
ANTHROPIC_API_KEYto.envand the commands use the API instead.) - Everything else is covered by the steps below.
- Node.js older than 22, Google Chrome missing, or Claude Code missing:
tell the user what to install and wait. You cannot install these.
(You are running inside Claude Code, so it is present; a user who
prefers a Claude API key can add
2. The resume, and anything else in documents/
Look in documents/ first. Besides resume.pdf, a user may have put past
material there for you to read: old resumes, a LinkedIn profile export as
PDF, transcripts, past applications, a portfolio page saved as PDF. Read
every PDF and text file there (the Read tool opens PDFs). Each is a source
for the profile in step 3: a bullet, a date, a project, a skill that the
current resume leaves out. Nothing personal in documents/ is ever
committed; the folder is git-ignored apart from its README. Re-running
/setup after more files land there is safe: it adds, it does not
overwrite what the user confirmed.
- Ask for the resume as a PDF. The user can drag the file into the chat or give its path.
- Copy it to
documents/resume.pdf. - Read the PDF. It is your first source for the profile.
3. The profile
Build data/profile.json in the shape of data/profile.example.json.
The schema is src/profile/schema.ts.
- Fill in everything the resume states: name, contact details, links, education, each job and project with its bullets, skills.
- Ask the user what the resume does not state. The full list is in questions.md. Follow it top to bottom, and skip a question only when the resume or the user has already answered it. Ask in small groups, at most four questions at a time. Use AskUserQuestion when a question has a fixed set of answers.
- Write
summary(three or four sentences: who they are, what they want, where, when) andfacts(one line per claim, every number exact, copied from the resume or said by the user). - Write
answers, the standing answers, from part G of the questions. - Show the user a short summary of the profile and correct what they flag.
- Run
doctoragain. A schema error names the field to fix.
Rules for this step:
- Never invent or round a fact. If you are not sure, ask.
- Never guess a demographic answer. Every one of them can be declined.
resume.pathis the absolute path ofdocuments/resume.pdf.- These files are git-ignored. Never commit them and never paste their contents into a file that is tracked.
4. Their voice and their drafts
- Copy
data/voice.mdtodata/voice.local.md. - Write
data/bank.jsonin the shape ofdata/bank.example.json: one starting draft per common question, from the user's own facts. Keep the text in braces where an answer depends on the company. - Draft one sample answer to "Why do you want to work here?" for a made-up
company and ask whether it sounds like them. Adjust
data/voice.local.mdand the drafts until it does. One or two rounds is enough.
5. The key
JEV is the only part of this tool the user is billed for. Tell them the numbers before they pay: about 6 cents each time the tool finds jobs, and about 1 cent for every 10 applications. Five dollars of credit lasts for months.
- Ask them to create a key and add a few dollars of credit, at either https://console.typesafe.ai/keys (TypeSafe, who make JEV) or https://openrouter.ai/keys (OpenRouter, who resell it). The model and the price are the same.
- Run
cp .env.example .env, thenopen -e .envso the file opens in a text editor. - Ask them to paste a TypeSafe key after
TYPESAFE_API_KEY=, or an OpenRouter key afterOPENROUTER_API_KEY=, save, and tell you when it is done. - Run
npx jev doctor --online. It makes one tiny JEV call and one tiny Claude call to prove both work.
Never ask the user to paste the key into the chat, and never print it. If they paste it into the chat anyway, tell them to delete that key where they made it (console.typesafe.ai/keys or openrouter.ai/keys) and create a new one, because a key in a chat is exposed.
6. Find jobs
Run npx jev discover. It takes about a minute. Show the top 15
as a short table: score, company, role, location, date posted. Say how many
jobs are queued and name the main reasons jobs were skipped
(npx jev status).
If the user wants other locations or kinds of roles than the ranking
prefers, the settings are in src/config.ts (LOCATION_MULTIPLIER,
FIT_WEIGHTS, DISCOVER).
7. Rehearse
- Run
npx jev apply --dry --count 3. A Chrome window opens, three forms are filled, nothing is sent, and the tabs close. - Show the user every answer, grouped by form. Point out anything the tool held and why.
- For each answer the user corrects, change the profile: a fact, or a
standing answer in
answers. Then rehearse again. Do not move on until the user says the answers are right.
Tell the user one thing before the first rehearsal: some job boards save a form as it is typed, so a rehearsal there leaves an unsent draft on that board. It is not an application and the employer is not told.
8. One application, ready for them to read
Setup ends with a real application filled and waiting, not with a list of
commands. Run npx jev apply --count 1 on the best job in the queue that
is on Greenhouse, Lever or Ashby. Without --submit the form is filled,
checked and left open in the tool's Chrome window.
Tell them to look at that window. Read the answers back to them, name
anything the tool held, and ask: "Send this one?" Only when they say yes,
run npx jev submit <id>. Then show the row in npx jev log.
That is the whole loop. Say so in one sentence, then stop asking questions.
9. What is next, in three lines
Do not list commands. Say only:
/applysends more: they say how many./reportis the dashboard: what was sent, what needs them, and the switch for a daily run./statussays where things stand at any time.
Mention these once, and only when they apply. Do not set any of them up during setup:
- If many of the jobs they would want are on Workday (
npx jev statuslists "workday" among the skip reasons), say that Workday employers each want an account and/accountshandles that when they are ready. - If they asked for it to run by itself,
/daily.
Two things the tool will not do, so they are not surprised: it does not
pass a "prove you are human" check, and it does not sign in anywhere
unless they set that up. A form that needs them stays open in the tool's
window; /resume picks it up.
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.

