agentleFS
Sign inStart free
muggl3mindmuggl3mind/career-manager/CLAUDE.md

career-manager

CLAUDE.md24 starsChanged 42 days agoMITView on GitHub

AI-assisted career management pipeline built as Claude Code skills. Scripts live per skill under <skill>/scripts/ (e.g. job-search/scripts/, cv-tailor/scripts/, evals/scripts/), plus shared utilities in the root scripts/. Run from the project root with the full prefixed path: SKILL.md files use paths relative to their skill directory. Always prefix with the skill folder. If config.yaml doesn't exist, or search-config.json is still the shipped stub (setup_required: true), run the onboarding skill first. See README for full setup steps. Before running workflows, the router…

  • Installs packages

The file

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use uv run to execute all Python scripts

    line 7
  2. Very specific:

    If .venv/ doesn't exist: uv venv && uv pip install -r requirements.txt

    line 8
  3. Distinctive:

    Never edit CSVs directly — use the tracker scripts

    line 26
  4. Very specific:

    If config.yaml doesn't exist, or search-config.json is still the shipped stub (setup_required: true), run the onboarding skill first.

    line 30
  5. Very specific:

    Before running workflows, the router calls scripts/generate_briefing.py for a status snapshot.

    line 34

≈ “Common” is an estimate: at least 1 in 5 of the 26,980 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

Career Manager

AI-assisted career management pipeline built as Claude Code skills.

Environment

  • Use uv run to execute all Python scripts
  • If .venv/ doesn't exist: uv venv && uv pip install -r requirements.txt

Script Paths

Scripts live per skill under <skill>/scripts/ (e.g. job-search/scripts/, cv-tailor/scripts/, evals/scripts/), plus shared utilities in the root scripts/. Run from the project root with the full prefixed path:

uv run job-search/scripts/ops/run_pipeline.py phase1   # correct
uv run scripts/ops/run_pipeline.py phase1              # WRONG — will fail

SKILL.md files use paths relative to their skill directory. Always prefix with the skill folder.

How This Works

  • Each skill has a SKILL.md — read it before executing that skill
  • search-config.json and config.yaml are generated by the onboarding skill — never edit pipeline scripts to change search queries or scoring
  • Data ownership: job-search/data/target-companies.csv and job-tracker/data/applications.csv are sources of truth
  • Never edit CSVs directly — use the tracker scripts

First-Time Setup

If config.yaml doesn't exist, or search-config.json is still the shipped stub (setup_required: true), run the onboarding skill first. See README for full setup steps.

Status Briefing

Before running workflows, the router calls scripts/generate_briefing.py for a status snapshot. This is automatic. Do not ask the user to run it.

Testing

uv run python3 scripts/smoke_test.py       # verify setup
uv run python3 -m pytest evals/tests/ -v   # run test suite

Provenance

This repository is exported from the maintainer's private workspace via an automated sanitization script. If you fork it, work in your fork directly — no sync step is needed.

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.

Check your setup, free