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

build-cv

Skill0 starsChanged 17 days agoMITView on GitHub

Build or update a CV on TakeMeUp.cv — from an attached CV file, from what the user tells you, or from a role starter — in the right format for the country it's for, then preview it and give a download link. Use when the user wants to create, rewrite into, or move their CV to TakeMeUp.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. YanaNeycheva/lay-off-ai-assistant★ 11same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository3 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    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:

    Use the TakeMeUp MCP tools.

    line 9
  2. Very specific:

    Call list_my_takemeup_cvs.

    line 17
  3. Distinctive:

    No file: ask for the essentials (contact details, last roles with dates and 2–4 results each, education, skills, languages).

    line 19
  4. Distinctive:

    Write bullets as results, with numbers where the user gave them.

    line 22
  5. Very specific:

    Run analyze_takemeup_cv_ats and check_takemeup_cv_gdpr (both free).

    line 26

≈ “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

Build a CV with TakeMeUp

Use the TakeMeUp MCP tools. If a tool says the user isn't signed in, tell them to run /mcp, choose takemeup and sign in to TakeMeUp (they can create a free account there), then try again.

1. Where is the CV going?

Ask which country (and language) the CV is for, unless $ARGUMENTS or the conversation already says. Call get_takemeup_locale_cv_rules for that country and follow it: whether a photo, date of birth, nationality or marital status are expected, and the date format. Tell the user in one line what applies, for example that a German CV usually has a photo and a French one usually doesn't need a date of birth.

2. Start from what exists

  • Call list_my_takemeup_cvs. If the user has a CV there already, ask whether to update it or start a new one.
  • The user attached a CV file: read it yourself and keep their facts exactly — employers, titles, dates, degrees. Don't invent anything. Then create_takemeup_cv (pick a template with list_takemeup_cv_templates if the user cares about the look; the default is fine otherwise) and save_takemeup_cv with the complete CV.
  • No file: ask for the essentials (contact details, last roles with dates and 2–4 results each, education, skills, languages). For a common hands-on role (driver, warehouse, healthcare assistant, cleaner, retail, food service), create_takemeup_cv_from_role gives a filled starter to edit.
  • Updating: get_takemeup_cv first, change only what the user asked, and save the complete CV with save_takemeup_cv.

Write bullets as results, with numbers where the user gave them. Never add skills, employers or figures the user didn't give you.

3. Check and show it

Run analyze_takemeup_cv_ats and check_takemeup_cv_gdpr (both free). Fix what's clearly fixable with the user's agreement, and mention the rest. Then call get_takemeup_cv_preview to show page 1, and give the editor link from the result.

4. Download

When the user wants the file, call get_takemeup_download_link (format pdf, or docx for Word). If it returns a gate (a one-time purchase for this CV, or PRO), tell the user that plainly and give them the links from the result. Don't push them to buy. The link works for 10 minutes.

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