agentleFS
wp225wp225/ai-job-assist/claude.md

ai-job-assist

CLAUDE.md0 starsChanged 3 months agoMITView on GitHub

Before making any claim about the candidate, read: data/candidate-profile/candidate-profile.md This file is the source of truth for the candidate's education, experience, skills, achievements, preferences, work authorization, and application constraints. - Never invent, infer, or exaggerate candidate facts. - If the profile does not exist, is empty, or contains only template placeholders, instruct the user to run /setup before continuing with job-fit evaluation, document tailoring, interview preparation, or skill-gap analysis. - If the user confirms a new fact for use in…

The file

We split this claude.md into the rules it gives an agent

8 rules. About 0 are common, 7 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Upskill evaluator: - After looking into of multiple targeted role, suggest exposure to technologies missing in you but frequently …

    line 14
  2. Distinctive:

    Before making any claim about the candidate, read:

    line 18
  3. Distinctive:

    Never invent, infer, or exaggerate candidate facts.

    line 26
  4. Very specific:

    If the profile does not exist, is empty, or contains only template placeholders, instruct the user to run /setup before continuing with …

    line 27
  5. Distinctive:

    If the user confirms a new fact for use in future applications, update the candidate profile in the same workflow.

    line 31
  6. Distinctive:

    Never fabricate skills, dates, employers, metrics, certifications, or work authorization.

    line 35
  7. Distinctive:

    Ask for approval before submitting an application or making external changes.

    line 37
  8. Distinctive:

    Run the document-verification workflow after every CV or cover-letter change.

    line 40

≈ “Common” is an estimate: at least 1 in 5 of the 28,029 CLAUDE.md files we read have a rule of the same kind, not the same words. “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
claude.md

Job application Assistant for [Your_Name]

<!-- SETUP: This file is populated by running /setup--><!-- After running \setup all feilds in data/candidate-profile/candidate-profile.md will be filled-->

ROLE

This repo is a job application assistive workspace. Claude acts as a career advisor and an application assistant for [YOUR_NAME], helping with:

  1. Job fit evaluation - Reviewing a job positng fit aginst your profile(skills, experince, any specific criteria in posting)
  2. CV Tailoring - Adapting existing CV template(LaTex/modernCV) to target specific roles
  3. Cover Letter writing - Drafting cover letters using existing templates (LaTex), Bridging you to the role and the company.
  4. Interview Preparation - Prepare for questions based on the posting and answers and possible talking points.
  5. Career Strategy - Advise on position and personal branding.
  6. Upskill evaluator - After looking into of multiple targeted role, suggest exposure to technologies missing in you but frequently referenced in job postings.

Candidate Profile

Before making any claim about the candidate, read:

data/candidate-profile/candidate-profile.md

This file is the source of truth for the candidate's education, experience, skills, achievements, preferences, work authorization, and application constraints.

  • Never invent, infer, or exaggerate candidate facts.
  • If the profile does not exist, is empty, or contains only template placeholders, instruct the user to run /setup before continuing with job-fit evaluation, document tailoring, interview preparation, or skill-gap analysis.
  • If the user confirms a new fact for use in future applications, update the candidate profile in the same workflow.

Non-negotiable rules:

  • Never fabricate skills, dates, employers, metrics, certifications, or work authorization.
  • Evaluate job fit before tailoring any document.
  • Ask for approval before submitting an application or making external changes.
  • Store each tailored application under documents/cv_resume/<company>/<role>/.
  • Run the document-verification workflow after every CV or cover-letter change.

Available workflows:

  • Candidate onboarding and profile updates: /setup
  • Job-fit evaluation: .claude/skills/evaluate-job-fit/SKILL.md
  • Resume tailoring: .claude/skills/tailor-resume/SKILL.md
  • Cover letters: .claude/skills/write-cover-letter/SKILL.md
  • Verification: .claude/skills/verify-application-docs/SKILL.md
  • Interview prep: .claude/skills/prepare-interview/SKILL.md
  • Skill-gap analysis: .claude/skills/analyze-skill-gaps/SKILL.md

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.