Claude Skill

profile

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.

LLM Mart · 0 points · 1 views 0 listing impressions 0 install-command copies
Download qbeka-jev-job-search-.claude_skills_profile-0f99505.zip · 0 KB

Install

skills CLI npx skills add https://github.com/qbeka/jev-job-search/tree/main/.claude/skills/profile
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install qbeka-jev-job-search@llmmart
Git git clone https://github.com/qbeka/jev-job-search.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole qbeka/jev-job-search collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

/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 wrong Where to change it
    A detail about the person: contact, education, dates, work authorization the matching field in data/profile.json
    A claim in a written answer, or a missing one facts, 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 sound data/voice.local.md
    The starting draft for a common open question data/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.
Files (jev-job-search)
  • SKILL.md 1.7 KB
    ---
    name: profile
    description: 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.
    model: claude-sonnet-5-5
    effort: high
    ---
    
    # /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 wrong | Where to change it |
       |---|---|
       | A detail about the person: contact, education, dates, work authorization | the matching field in `data/profile.json` |
       | A claim in a written answer, or a missing one | `facts`, `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 sound | `data/voice.local.md` |
       | The starting draft for a common open question | `data/bank.json` |
    
       The full list of questions the profile answers is in
       [../setup/questions.md](../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.
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.