agentleFS
VincenzoImpVincenzoImp/openings/skills/maintain-career/SKILL.md

maintain-career

Skill7 starsChanged 3 days agoMITView on GitHub

Maintain the owner's Openings Profile, career entries, highlights and CV/letter templates - "update my profile from this CV", "add my new job", "improve my highlights", "fix my CV template". Reconciles new material into the existing record without inventing anything.

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:

    Read openings first, and the writing reference before writing highlights.

    line 11
  2. Distinctive:

    Read the entries in full, propose sharper wording in chat, grounded in the narrative, and save the ones the owner approves as approved.

    line 58

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

Keep your Profile and career entries current

Read openings first, and the writing reference before writing highlights. Only the owner is a source of facts: their CV, LinkedIn export, publication list, messages in chat. Job postings never are.

1. Read the record

workspace_context with the full career. Read the material the owner gives in full; when it is a file, read it from disk (pdftotext for a PDF).

2. Reconcile

Compare the material with the record, item by item:

  • Profile: name, headline, contact, location, summary, links.
  • Entries: match by employer or institution, title and dates. The same role is the same entry, even when worded differently.
  • New: a role, project, degree, award or publication not in the record.
  • Changed: a later end date, a promotion, a new responsibility, a correction.
  • Conflicts: dates, titles or scope that disagree. Ask; never pick one.

A CV is a selection: something missing from it stays in the record. Remove an entry only when the owner says it is wrong.

3. Confirm, then write

List the material changes in chat (new entries, changed titles or dates, Profile changes, conflicts) and wait for the owner's yes. Small corrections inside an approved plan need no second round.

Then:

  • profile_update for the Profile;
  • career_save for entries, in one batch. Integrate new facts into the entry's narrative so it reads as one current account: rewrite the passage, do not append dated updates. Keep personal and team work apart, keep exact dates and titles, and put where a fact came from in the entry's metadata;
  • highlights_save for wording worth reusing: new highlights are saved not approved unless the owner approved that exact wording in chat. Mark ★ always include only on request. Remove duplicates, keeping the better one.

Facts about eligibility, availability or salary belong in Facts about me: offer to record them there.

Improve highlights

Read the entries in full, propose sharper wording in chat, grounded in the narrative, and save the ones the owner approves as approved. Flag a highlight that claims more than its entry supports.

Templates

For "fix my CV template": read it with templates_get, change the TeX, compile it locally with sample content from the record, check the PDF (pages, layout, links), then templates_save with its version. Keep writing rules in Preferences and limits in the template.

After a change

Shortlisted applications whose documents would now be clearly better can be redone with prepare-applications: name them and offer it; do not redo them unasked.

Report back

In chat: Profile fields changed; entries added and updated, by title; new highlights and how many await approval; conflicts and questions still open; applications that could benefit.

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.