Update to Seekrly

{
  "description": "Build or tailor a resume in Seekrly - tailor an existing resume to a job, create a new resume from the career profile or from a resume file the user shares, change its template, change its look (font size, margins, spacing, colors) or fit it on fewer pages, download or share it. Use for \"tailor my resume for this job\", \"make a resume for…\", \"turn this PDF into a Seekrly resume\", \"download/share my resume\".",
  "included_files": [],
  "name": "seekrly-tailor-resume",
  "skill_md_contents": "---\nname: seekrly-tailor-resume\ndescription: Build or tailor a resume in Seekrly - tailor an existing resume to a job, create a new resume from the career profile or from a resume file the user shares, change its template, change its look (font size, margins, spacing, colors) or fit it on fewer pages, download or share it. Use for \"tailor my resume for this job\", \"make a resume for…\", \"turn this PDF into a Seekrly resume\", \"download/share my resume\".\n---\n\n# Build and tailor resumes\n\nFollow the ground rules in the `seekrly` skill. Never invent experience, employers,\ndates, degrees, numbers or skills - only use facts from Seekrly or from the user.\n\n## Know the two kinds\n\n`list_resumes` returns each resume's `kind`:\n\n- **built** - made in Seekrly; content is JSON Resume, readable with `get_resume`\n  and editable with `update_resume`.\n- **uploaded** - the user's own PDF/DOC file; content can't be read or edited here.\n  To work from it, ask the user to share the file or paste its text in the chat, then\n  build a new resume with `create_resume`.\n\n## Tailor to a job\n\n1. **Get the job**: from the chat, or the tracked application (`get_application`\n   → `description`, `skills`).\n2. **Get the source**: the user's chosen built resume (`get_resume` →\n   `resumeData`), or the career profile (`get_career_profile`) if there's none.\n3. **Plan the changes** and show them briefly before saving:\n   - Reorder and rewrite highlights to lead with what the job asks for, keeping the\n     user's facts and numbers.\n   - Sharpen `basics.label` (headline) and `basics.summary` for the role.\n   - Surface matching skills that the user really has; don't add ones they don't.\n   - List any gaps honestly (\"the job wants Kubernetes; nothing in your profile\n     mentions it - want to add something true?\").\n4. **Show it, then save.** Show the tailored resume before saving: the headline,\n   summary, each job with its highlights, skills, and what changed from the\n   source. Ask \"Save it, or change something?\" Then save. Prefer a **new**\n   resume so the original stays intact:\n   `create_resume` with `name` like \"Backend Engineer - Stripe\", the full\n   `resumeData`, and a `template` (modern, classic, minimal, twocolumn, timeline;\n   keep the source's template and `design` unless asked). Replacing an existing resume's content\n   uses `update_resume`, which saves right away: send the **complete** JSON Resume\n   document (not a diff), and confirm the change with the user first.\n5. Offer to link it to the application (`update_application` with `resumeId`) or to\n   attach it to an outreach email (`seekrly-outreach`).\n\n## Build from a file the user shares\n\nRead the whole file and map it into JSON Resume: `basics` (name, label, email,\nphone, url, summary, location, profiles), `work` (one entry per job; bullets into\n`highlights`), `education`, `skills` (groups with `keywords`), `projects`,\n`certificates`, `awards`, `languages`, `volunteer`, `publications`. Keep the user's\nwording, dates as `YYYY-MM`, and leave out what isn't there. Before calling\n`create_resume`, show what you extracted (sections and entry counts, anything\nunclear) and ask them to confirm.\n\n## Look and page fit\n\nBoth `create_resume` and `update_resume` take an optional `design`; with\n`update_resume` only the fields you send change (ask first, like content).\n\n- `fontSize`: `xxsmall`, `xsmall`, `small` (default), `medium`, `large`.\n- `margin` (page margins): `minimal`, `narrow`, `normal` (default).\n- `sectionSpacing` (space between sections and entries): `tight`, `compact`,\n  `normal` (default).\n- `primaryColor`, `textColor`, `backgroundColor`: hex colors like `#2563eb`.\n\nWhen the user wants fewer pages or a denser resume (\"fit on one page\", \"less\nwhite space\", \"smaller margins\"), try `margin: \"narrow\"` and\n`sectionSpacing: \"compact\"` first, then `minimal` / `tight`, and only then a\nsmaller `fontSize`, so the text stays readable. Don't cut their content to make\nit fit unless they ask.\n\n## Labels, download and sharing\n\n- Rename, version label or make default: `update_resume` with `name`, `version` or\n  `makeDefault` - applies directly.\n- File: `download_resume` returns a link valid for 5 minutes; give it only to the\n  user and fetch a new one if it expired.\n- Public link: `share_resume` with `visibility` `public` (ask first; explain who can\n  see it) or `private` (immediate). `get_resume` shows the current link, whether it's\n  password-protected, and view/download stats.\n- Password-protected link: never ask for, suggest or handle a password. The user\n  sets one in Seekrly on the Resumes page (the link is in the `share_resume`\n  description). Making a password-protected resume public removes its password, so\n  say so before the call.\n"
}