build-profile

build-profile

Produce profile/master-profile.md from whatever the user already has, then fill gaps with a short, track-aware interview. Ingest first, ask last.

1. Gather what exists (don't ask the user to retype anything)

Collect any of these the user provides; actively offer the options:

• Resume / CV — see step 1a for PDFs (mandatory link-extractor first), then read the body with your runtime's file-read tool.
• LinkedIn PDF — read it. (Point them to LinkedIn → profile → Resources → Save to PDF if they don't have it.)
• AI-memory (proactively offer it). Ask once: "Have you used ChatGPT, Claude, or Gemini for your job search or career? Paste this prompt into the one you use most and bring back the result — I'll fold in recent interviews, feedback, and career details you'd otherwise have to retype." Then surface the prompt from ../../profile/IMPORT_MEMORIES_PROMPT.md (it pulls only job-search-relevant memories, not everything). On ingest, merge only new facts — never duplicate what the resume/profile already has; mark uncertain items [VERIFY].
• Links — record every link, then enrich the user's own ones (see §1b). LinkedIn stays record-only (ToS).

Read everything before asking anything.

1a. For every PDF input — run the link extractor FIRST

A typical agent file-read tool surfaces visible anchor text only (it shows the word "LinkedIn" but not the URL it's hyperlinked to). LaTeX/Word/Docs resumes routinely embed \href{url}{anchor} annotations whose URLs are invisible to a plain read. You will silently lose the user's LinkedIn / GitHub / portfolio URLs if you skip this step — which is why extract_links.py exists.

python3 skills/build-profile/scripts/extract_links.py <path-to-resume.pdf>

The script decompresses every FlateDecode stream and pulls every /URI annotation it can find. Stdout is JSON:

{
  "urls": ["https://...", ...],           // every URL found, in order
  "classified": {
    "linkedin": "https://linkedin.com/in/...",
    "github": "https://github.com/...",
    "other": { "<host-or-label>": "<url>", ... }
  }
}