agentleFS
Miracle-AlignerMiracle-Aligner/job-search-hq/.claude/skills/build-profile/SKILL.md

build-profile

Skill1 starsChanged 5 months agoMITView on GitHub

Use when the user wants to create or refresh their candidate profile for Job Search HQ. Triggers: /build-profile, "build my profile", "set up my profile", "generate my candidate profile", "update my profile from my CV / LinkedIn". Produces profile/candidate.md (prose, read by the assessment skills) and profile/profile.json (structured) — either by parsing existing materials (CV, LinkedIn, an old profile) or by a short interview.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    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:

    Mode A — parse existing materials (preferred): If the user has a CV (run /ingest-cv first or point at profile/cv/), a LinkedIn export/URL, …

    line 23
  2. Very specific:

    Keep candidate.md skimmable: bullet lists, no fluff.

    line 39
  3. Very specific:

    Write both files (never overwrite without confirming if they already exist — offer to merge).

    line 44

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

build-profile

Two outputs, gitignored, mirroring the committed examples:

  • profile/candidate.md — prose, the shape of profile/candidate.example.md (Strengths · Gaps · Languages · CV variants). Assessment skills Read this at scoring time.
  • profile/profile.json — structured, the shape of profile/profile.example.json (name, title, experienceYears, education, targetRole, targetComp, location, strengths, gaps, languages, cvVariants).

Pick a mode

Mode A — parse existing materials (preferred). If the user has a CV (run /ingest-cv first or point at profile/cv/), a LinkedIn export/URL, or an old profile, read those and synthesize. Don't interrogate them for facts already on the page.

Mode B — interview. Otherwise ask a short set of questions (don't exhaust them):

  1. Target role(s) and seniority.
  2. Core strengths — the 4–6 things they're genuinely strong at.
  3. Honest gaps — what they'd be stretched or rejected on.
  4. Comp expectations (currency, monthly band) and location/timezone/relocation.
  5. Languages + levels.
  6. CV variants they keep (e.g. a backend/LLM CV vs a voice CV).

Synthesize

  • Be concise and honest — gaps are as useful as strengths (they drive accurate level/tech scoring and gap-defense in interview prep). Don't inflate.
  • Keep candidate.md skimmable: bullet lists, no fluff.
  • cvVariants[] entries reference files under profile/cv/ (see /ingest-cv).

Finish

Write both files (never overwrite without confirming if they already exist — offer to merge). Then tell the user they're ready to score roles (/add-vacancy) and that the files are local (gitignored). No bake needed — the profile isn't part of the board.

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.