agentleFS
muggl3mindmuggl3mind/career-manager/evals/SKILL.md

evals

Skill24 starsChanged 42 days agoMITView on GitHub

Evaluate job-search pipeline code and outputs for correctness. Use when running code reviews, verifying pipeline outputs after a run, or checking ongoing pipeline health. Handles static analysis, runtime verification, and health monitoring.

7 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 7 edited versions we read keep these.

  • 1

    Distinctive

    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:

    Run the relevant eval script for your situation

    line 21
  2. Very specific:

    Does NOT evaluate: itself, other career-manager skills, or non-pipeline code

    line 46

“Common” is measured: kept by at least 6 in 10 of the 7 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

Evals

Independent evaluation suite for the job-search pipeline. Lives outside the pipeline it evaluates.

Evaluation Levels

LevelScriptWhen to Run
0. Test Suiteevals/tests/ (pytest)After any code change
1. Code Reviewevals/scripts/code_review.pyAfter building or changing pipeline code
2. Runtime Verifyevals/scripts/runtime_verify.pyAfter a pipeline run completes
3. Health Monitorevals/scripts/health_monitor.pyRecurring — every pipeline run or 2-3x/week

Process

  1. Run the relevant eval script for your situation
  2. Review the report output
  3. Fix issues (or flag for user approval if touching shared data)
  4. Re-run the eval to verify fixes

Usage

# Level 0: Full test suite
uv run python3 -m pytest evals/tests/ -v

# Level 1: Static code review of job-search pipeline
uv run evals/scripts/code_review.py

# Level 2: Validate outputs after a pipeline run
uv run evals/scripts/runtime_verify.py

# Level 3: Ongoing health monitoring
uv run evals/scripts/health_monitor.py
uv run evals/scripts/health_monitor.py --json

Scope

  • Evaluates: job-search/ (scripts, data, caches)
  • Does NOT evaluate: itself, other career-manager skills, or non-pipeline code
  • Also owns: the pytest suite in evals/tests/ and evals/schemas/eval-results.schema.json

Output Format

Each script prints a check-by-check report with pass/warn/fail status and returns non-zero exit code if critical checks fail.

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.