← ClaudeAtlas

rewrite-linkedin-profilelisted

Rewrites the user's LinkedIn profile section by section (headline, about, experience, skills) to match a target job, using keywords mined from that job's posting. Use when the user says "rewrite my linkedin", "optimize my profile for this job", "tailor my linkedin to this role", or runs /rewrite-linkedin-profile. For the resume version use rewrite-resume; for keyword mining alone use jd-keyword-miner.
stalinzbb/job-search-toolkit · ★ 0 · Data & Documents · score 58
Install: claude install-skill stalinzbb/job-search-toolkit
# Rewrite LinkedIn Profile Rewrite the profile against a specific target role. Nothing gets written until the interview step is done — the whole value here is that every claim is true. ## Output location Everything for one target role lives in one folder: ``` $JOB_SEARCH_DIR/<company>-<role-slug>/ ├── inputs/ # raw job posts, the resume you provided ├── keyword-report-2026-08-24.md # every output is dated; newest wins ├── linkedin-rewrite-2026-08-24.md └── resume-rewrite-2026-08-24.md ``` `JOB_SEARCH_DIR` is the environment variable if the user has set one, otherwise `~/job-search`. Resolve it once with Bash — `echo "${JOB_SEARCH_DIR:-$HOME/job-search}"` — and never hardcode a path. Create the folder on first run and tell the user where it went. The newest report is whichever `keyword-report-*.md` sorts last: `ls "$DIR"/keyword-report-*.md | tail -1`. This skill writes `linkedin-rewrite-<YYYY-MM-DD>.md`. Dated by run, never overwritten — a second run the same day gets a `-2` suffix, so the folder keeps every version you've sent. ## Step 1 — Get the keyword report Check `$JOB_SEARCH_DIR` for an existing `<slug>/keyword-report-*.md` — reports are dated; use the most recent. If one matches the target role, read it and confirm with the user: "Using the report for `<slug>` — right target?" No report? Ask for the job link(s) and mine them first: - Fetch chain (never ask for LinkedIn credentials): logged-in Chrome → WebFetch → ask the user to paste