agentleFS
Sign inStart free
dsdev-ddsdev-d/takemeup-mcp/skills/check-cv/SKILL.md

check-cv

Skill0 starsChanged 17 days agoMITView on GitHub

Review one of the user's TakeMeUp CVs with TakeMeUp's free checks — ATS compatibility, GDPR/personal-data risk for the target country, the six-second recruiter skim, and bullets that list duties instead of results — and turn the findings into a short, prioritised fix list. Use when the user asks if their CV is good, ATS-friendly, or ready to send.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is 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.

  • 1

    Very specific

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

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

    Use the TakeMeUp MCP tools.

    line 9
  2. Distinctive:

    Run the free checks — they don't use AI and cost nothing:

    line 12

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill 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
SKILL.md

Check a CV with TakeMeUp

Use the TakeMeUp MCP tools. If the user isn't signed in, tell them to run /mcp, choose takemeup and sign in.

  1. Pick the CV: list_my_takemeup_cvs, and ask which one if there are several (or use $ARGUMENTS).
  2. Run the free checks — they don't use AI and cost nothing:
    • analyze_takemeup_cv_ats — the 0–100 score and its findings.
    • check_takemeup_cv_gdpr — personal fields that are risky for the CV's country.
    • check_takemeup_six_second — the terms a recruiter should see in the top third of page 1; compare them with get_takemeup_cv_preview.
    • find_takemeup_weak_achievements — bullets that describe duties instead of results.
  3. Report in this order: the three changes that matter most, then the rest briefly. Quote the user's own bullet when you suggest a rewrite, and don't invent numbers — ask the user for the real ones.
  4. Offer to apply the fixes. If they agree, get_takemeup_cv, change only those parts, and save_takemeup_cv with the complete CV. Re-run the ATS check and show the new score.

The PRO checks (check_takemeup_resume_aging, detect_takemeup_buzzwords, run_takemeup_authenticity) are optional extras. If one returns a gate, say so in one line and carry on with the free results.

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