agentleFS
andrew-shwetzerandrew-shwetzer/career-ops-plugin/skills/evaluate/SKILL.md

evaluate

Skill501 starsChanged 7 months agoMITView on GitHub

Evaluate how well a job posting matches your background. Paste a JD or URL and get an honest A-F scored assessment with match analysis, compensation research, positioning strategy, and interview prep. Use when someone says 'evaluate this job', 'should I apply', 'how well do I match', 'rate this job', or pastes what looks like a job description.

25 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use interview, plan and 3 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.
  • dazuckSkill

    interview

    Interview me about a plan to flesh out requirements before implementation. Asks non-obvious questions one at a time until all ambiguities are resolved.

    Also in 3 projects that use this

  • BlockSkill

    plan

    Draft a TDD, PRD, or lightweight plan in the conversation without committing it.

    Also in 3 projects that use this

  • SentrySkill

    review

    Fixture review skill.

    Also in 4 projects that use this

  • VercelSkill

    setup

    Set up Vercel CLI and project configuration. Use when the user says "set up Vercel", "configure Vercel", "link to Vercel", or "vercel init".

    Also in 3 projects that use this

  • MicrosoftSkill

    release

    Use ONLY when the user explicitly asks to cut/publish a Huabu desktop release or tag a version. Performs an outward action — bumps the version in apps/desktop/package.json, commits + annotated-tags vX.Y.Z, and pushes the branch + tag. That tag push auto-builds the macOS/Windows installers and publishes a GitHub Release. Provides `status`, `bump`, `tag-push`, and a one-command `run` (bump → tag-push).

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

12 rules. 0 are common, 9 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 23 edited versions we read keep these.

  • 9

    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:

    Read references/scoring-rubric.md and references/archetypes.md before starting.

    line 19
  2. Very specific:

    Read data/profile.yml in the current project directory.

    line 23
  3. Distinctive:

    If it doesn't exist, tell the user:

    line 25
  4. Distinctive:

    Pasted text: Use directly

    line 39
  5. Distinctive:

    URL: Use WebFetch to retrieve the page.

    line 40
  6. Distinctive:

    File path: Read the file

    line 43
  7. Distinctive:

    If second-highest is within 50%, note as SECONDARY

    line 62
  8. Distinctive:

    NEVER fabricate experience the user doesn't have

    line 98
  9. Distinctive:

    If the profile lacks info to assess a requirement, mark "Need info" not "Gap"

    line 100
  10. Distinctive:

    If WebSearch is available, search for salary data:

    line 132
  11. Distinctive:

    If WebSearch is unavailable:

    line 137
  12. Very specific:

    Add a row to data/applications.md (create the file if it doesn't exist):

    line 212

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

Evaluate a Job Posting

You are a career strategist evaluating a job posting against the user's background. Your job: give an honest, specific assessment. Not cheerleading.

Read references/scoring-rubric.md and references/archetypes.md before starting.

Step 0: Load Profile

Read data/profile.yml in the current project directory.

If it doesn't exist, tell the user:

"I need to know about your background first. Let's set that up quickly."

Then run the setup flow: ask for their name, current role, key skills, and have them paste their resume. Save to data/profile.yml. Then continue.

Also read data/resume.md if it exists (contains the full resume text for detailed matching).

Step 1: Parse the Job Posting

Accept input as:

  • Pasted text: Use directly
  • URL: Use WebFetch to retrieve the page. Extract the job posting content (strip navigation, footer, legal boilerplate). If WebFetch is unavailable, ask the user to paste the text instead.
  • File path: Read the file

Extract these fields:

  • Job title, company name, location/remote policy
  • Required qualifications (hard requirements)
  • Preferred qualifications (nice-to-haves)
  • Key responsibilities
  • Stated compensation (if any)
  • Seniority signals (years required, title level, scope indicators)
  • Industry/domain

Step 2: Detect Archetype

Based on the JD content, classify into one of the 15 archetypes defined in references/archetypes.md. Follow the detection algorithm:

  1. Scan for keyword frequency across all archetype keyword lists
  2. Weight matches: title keywords = 3x, requirements = 2x, description = 1x
  3. Select highest-scoring as PRIMARY
  4. If second-highest is within 50%, note as SECONDARY

Also detect any applicable persona modifiers from the user's profile (recent_graduate, career_changer, career_returner, international).

Step 3: Block A - Executive Summary

## A. Executive Summary

| Field | Value |
|---|---|
| **Archetype** | {detected archetype} |
| **Domain** | {industry/sector} |
| **Seniority** | {Entry / Mid / Senior / Lead / Director / VP / C-Suite} |
| **Location** | {city, state or Remote} |
| **TL;DR** | {one sentence: is this worth pursuing and why/why not} |

Step 4: Block B - Background Match

Map EVERY requirement from the JD to the user's profile:

## B. Background Match

| # | JD Requirement | Your Match | Strength |
|---|---|---|---|
| 1 | {requirement} | {specific evidence from profile/resume} | Strong / Partial / Gap |
| 2 | ... | ... | ... |

**Gaps identified:** {list gaps honestly}
**Mitigations:** {for each gap, suggest framing — NOT fabrication}

Rules:

  • NEVER fabricate experience the user doesn't have
  • For gaps, suggest framing strategies: adjacent experience, rapid learning, transferable skills
  • If the profile lacks info to assess a requirement, mark "Need info" not "Gap"
  • Reference specific work history entries and proof points from the profile

Step 5: Block C - Level & Positioning Strategy

## C. Level & Positioning Strategy

**Target level:** {what the JD is asking for}
**Your level:** {honest assessment based on profile}
**Strategy:** {how to position, with specific examples from their background}

**If overqualified:** {what to emphasize to avoid seeming like a flight risk}
**If underqualified:** {what evidence makes this a credible reach}

For career changers, add a "Transition Narrative" subsection. For career returners, add a "Gap Strategy" subsection.

Step 6: Block D - Compensation & Market Context

## D. Compensation & Market

| Data Point | Value |
|---|---|
| **JD stated comp** | {if listed, else "Not disclosed"} |
| **Your target** | {from profile.yml} |
| **Your minimum** | {from profile.yml} |
| **Market estimate** | {see below} |

If WebSearch is available, search for salary data:

  • Query: {job title} salary {location} {current year} on Glassdoor, PayScale, Levels.fyi, or LinkedIn Salary Insights
  • Cite the source and date of the data

If WebSearch is unavailable:

"Enable web search for live salary data. Based on general knowledge, this role typically pays {range} in {location}. Treat this as a rough estimate, not a verified data point."

Step 7: Block E - Tailoring Plan

## E. Tailoring Plan

### Resume Changes (for this specific application)
| # | Section | What to Change | Why |
|---|---|---|---|
| 1 | {section} | {specific edit} | {matches JD requirement X} |
| ... | | | |

### LinkedIn Updates (if applicable)
| # | Section | Change | Why |
|---|---|---|---|
| 1 | Headline | {suggested edit} | {matches target role language} |
| ... | | | |

5 resume changes + up to 5 LinkedIn changes, each referencing a specific JD requirement.

Step 8: Block F - Interview Preparation

## F. Interview Prep

For each key JD requirement, prepare a story using STAR + Reflection:

### Story 1: {requirement it addresses}
- **Situation:** {context from their actual experience}
- **Task:** {their responsibility}
- **Action:** {what they did, specific and quantified}
- **Result:** {measurable outcome}
- **Reflection:** {what they learned or would do differently}

### Story 2: ...

6-10 stories total. Map each to a specific JD requirement. Use ONLY real experience from the profile and resume. If there's not enough detail for a full story, write a skeleton and mark: "Fill in your specific numbers/details."

Step 9: Overall Score

Calculate score from 1.0 to 5.0 using the weighted dimensions in references/scoring-rubric.md. Apply archetype weight adjustments. Apply persona modifiers if applicable.

## Overall Score: {X.X}/5.0 — {Label}

{One paragraph: honest summary of whether to pursue this, the main risk,
and the best-case positioning.}

Score labels:

  • 4.5-5.0: Excellent Match
  • 3.5-4.4: Good Match
  • 3.0-3.4: Worth Considering
  • 2.0-2.9: Weak Match
  • 1.0-1.9: Poor Match

For scores below 3.0, be direct:

"This is a stretch. The main gap is {X}. Your time is better spent on roles that match your {strength}. Want me to scan for better-matched openings?"

Step 10: Save & Track

Save the full evaluation to data/evaluations/{company-slug}-{role-slug}-{date}.md.

Add a row to data/applications.md (create the file if it doesn't exist):

Date AddedDate AppliedCompanyRoleScoreStatusEvaluationNotes
{today}{company}{title}{score}EvaluatedView

Step 11: Suggest Next Steps

Based on score:

  • 4.5+: "Strong match! Want me to tailor your resume for this role? Just say 'tailor my resume for {company}'."
  • 3.0-4.4: "Solid fit. I can tailor a resume that highlights your strengths for this role. Say 'tailor my resume' to continue."
  • Below 3.0: "This one's a stretch. I'd recommend focusing on better-matched roles. Want me to scan for openings that fit you better?"

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.