agentleFS
leakyhoseleakyhose/resumekit/.claude/skills/import/SKILL.md

import

Skill1 starsChanged 3 months agoMITView on GitHub

Bring an existing resume (pdf, docx, tex, or pasted text) into the resumekit structure — extract its content, refit it onto a template in resume/, and verify it builds. Use when the user is setting up this workspace with a resume they already have.

17 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use export, status and 2 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.
  • soilmassSkill

    export

    Animation export configurations including format selection, resolution, framerate, quality, and optimization settings. Use when rendering animations for web, mobile, video, or social media. Provides tokens for all export parameters across Lottie, GIF, video, and sprite sheet formats.

    Also in 3 projects that use this

  • AnthropicSkill

    status

    Case status summary by audience — client-facing (plain language), internal (for the professor), or court-ready (formal caption format per local rules). Same facts, different framing and depth. Use when a student needs to update the client, brief the professor, or prepare a court status report.

    Also in 5 projects that use this

  • MicrosoftSkill

    report

    Turn an exploration (threads, findings, charts) into a single Markdown report — note, blog post, executive summary, KPI dashboard, slide brief, or multi-section analytical report, with embedded charts.

    Also in 3 projects that use this

  • OpenAISkill

    audit

    Audit or critique a product flow, journey, workflow, funnel, onboarding path, checkout path, settings path, screen, or multi-step product experience by capturing screenshots first, then reporting UX, design, and accessibility findings inline from that evidence. Use Figma only when the user explicitly asks for a board. Use when the user asks to audit, review, critique, inspect, assess, analyze, evaluate, or give feedback on a product experience.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 13 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    Read rules/core.md first if you haven't this session.

    line 8
  2. Distinctive:

    Hard rule: import preserves wording: Do not improve, rewrite, or trim bullets during import — content migrates verbatim so the user can …

    line 10
  3. Distinctive:

    Keep the original file untouched.

    line 20
  4. Very specific:

    Run make init to list templates.

    line 25

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

Importing an existing resume

Read rules/core.md first if you haven't this session.

Hard rule: import preserves wording. Do not improve, rewrite, or trim bullets during import — content migrates verbatim so the user can diff old vs new and trust nothing was lost. Improving bullets is a separate task for afterwards.

1. Read the source

  • .tex — read directly
  • .pdf — extract text with pdftotext <file> - (poppler is already installed)
  • .docx — try textutil -convert txt (macOS) or pandoc; otherwise ask the user to paste the text
  • Keep the original file untouched. If it contains real personal details, confirm this repo is the user's private copy before writing anything.

2. Pick the template

Run make init to list templates. Ask which the user wants if it isn't obvious — if their old resume already looks like Jake's Resume, jakes is the safe default. Then make init TEMPLATE=<choice> (use FORCE=1 only if resume/ is still placeholder content).

3. Migrate the content

Rewrite resume/resume.tex's content using the template's vocabulary (\resumeSubheading, \resumeItem, ...), section by section: header/contacts, education, experience, projects, skills. Escape LaTeX specials in the imported text (%, &, #, $, _).

4. Verify

  • make check — must compile and match the expected page count.
  • Overlong bullets (span violations) are reported, not rewritten: list them as follow-up work for the user, since fixing them changes wording.
  • make render + view the png; if the source was a pdf, compare against the original side by side and note layout differences.
  • Suggest committing the import as-is before any improvement work starts.

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.