agentleFS
qbekaqbeka/jev-job-search/.claude/skills/profile/SKILL.md

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

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.
  • PydanticSkill

    coverage

    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

  • dragonflydbSkill

    benchmark

    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 AzureSkill

    docs

    Also in 3 projects that use this

  • GoogleSkill

    tdd

    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

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
  1. Very specific:

    If data/profile.json does not exist, this is a first run: use the /setup skill instead.

    line 10
  2. Very specific:

    Run npx jev doctor. A schema error names the field to fix.

    line 13
  3. Distinctive:

    Ask what the user wants to change, or which answer on a form was wrong.

    line 14
  4. Very specific:

    Run npx jev doctor again, then rehearse the form that was wrong: npx jev apply --dry <job id>.

    line 27

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

/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.

  1. Run npx jev doctor. A schema error names the field to fix.
  2. Ask what the user wants to change, or which answer on a form was wrong.
  3. Make the change in the right place:

    What was wrongWhere to change it
    A detail about the person: contact, education, dates, work authorizationthe matching field in data/profile.json
    A claim in a written answer, or a missing onefacts, experience or projects in data/profile.json
    How a recurring question is answered (relocation, text messages, notice period, pay, history)answers in data/profile.json
    How written answers sounddata/voice.local.md
    The starting draft for a common open questiondata/bank.json

    The full list of questions the profile answers is in ../setup/questions.md.

  4. Run npx jev doctor again, 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, projects or answers will never appear in an application.
  • These files are git-ignored. Never commit them.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.