profile
Skill368 starsChanged 5 days agoMITView on GitHub
Check or change the candidate profile, the standing answers, the drafts and the voice guide. Use when the user says /profile, when a form answer looked wrong, or when their details changed. For a first run use /setup instead.
30 other projects use a version of this.
Adopted by
Most recently taken up by
- DataDog/dd-trace-pytheir own version, first seen Nov 16, 2026
- rafaym1/scholarship-desktheir own version, first seen Nov 16, 2026
- baekenough/oh-my-customcodetheir own version, first seen Nov 14, 2026
- galiprandi/job-seekertheir own version, first seen Nov 14, 2026
- nockawa/NockMontheir own version, first seen Nov 8, 2026
- cismontane-harris2642/signal-prospecting-kittheir own version, first seen Nov 1, 2026
Used with
Projects with it also use coverage, benchmark and 2 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.
PydanticSkillcoverage
Fetch coverage diff from Codecov for the current branch or a specific PR. Shows uncovered lines, patch coverage, and overall coverage change.
Also in 3 projects that use this
dragonflydbSkillbenchmark
Benchmark Dragonfly (and compare against Valkey/Redis) on local or remote cloud instances, then produce a performance + memory report with charts and a raw-data appendix. Use this whenever the user runs /benchmark, or asks to benchmark / load-test / measure throughput, QPS, latency, or memory efficiency of Dragonfly or another Redis-compatible server, to compare Dragonfly vs Valkey or Redis, or to generate a benchmark report. Trigger it even when the user just describes the goal ("see how fast Dragonfly is on this box", "compare memory per key vs Valkey") without saying the word "benchmark".
Also in 3 projects that use this
Microsoft AzureSkilldocs
Also in 3 projects that use this
GoogleSkilltdd
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
Also in 3 projects that use this
Other versions30 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 30
- ccusage/ccusage★ 19ksame name
- ryoppippi/ccusage★ 19ksame name
- FalkorDB/FalkorDB★ 11ksame name
- pytorch/executorch★ 5.2ksame name
- verl-project/verl-omni★ 1.5ksame name
- DataDog/dd-trace-py★ 655same name
- nockawa/Typhon★ 253same name
- galiprandi/job-seeker★ 136same name
- the-void-ia/void-box★ 88same name
- DataWithBaraa/claude-code-data-engineering-skills★ 84same name
20 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
4 rules. 0 are common, 1 is distinctive, and 3 are very specific to this project.
0
Common
Most of the 24 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
If data/profile.json does not exist, this is a first run: use the /setup skill instead.
- Very specific: line 13
Run npx jev doctor. A schema error names the field to fix.
- Distinctive: line 14
Ask what the user wants to change, or which answer on a form was wrong.
- Very specific: line 27
Run npx jev doctor again, then rehearse the form that was wrong: npx jev apply --dry <job id>.
“Common” is measured: kept by at least 6 in 10 of the 24 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
/profile: check or change the candidate's data
If data/profile.json does not exist, this is a first run: use the
/setup skill instead.
- Run
npx jev doctor. A schema error names the field to fix. - Ask what the user wants to change, or which answer on a form was wrong.
Make the change in the right place:
What was wrong Where to change it A detail about the person: contact, education, dates, work authorization the matching field in data/profile.jsonA claim in a written answer, or a missing one facts,experienceorprojectsindata/profile.jsonHow a recurring question is answered (relocation, text messages, notice period, pay, history) answersindata/profile.jsonHow written answers sound data/voice.local.mdThe starting draft for a common open question data/bank.jsonThe full list of questions the profile answers is in ../setup/questions.md.
- Run
npx jev doctoragain, then rehearse the form that was wrong:npx jev apply --dry <job id>.
Things to know:
- Any change to the profile, the drafts or the voice guide makes the tool forget its remembered answers, so the next run asks Claude again with the corrected facts. That is on purpose.
- Anything not in
facts,experience,projectsoranswerswill never appear in an application. - These files are git-ignored. Never commit them.
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.

