Update to Seekrly

{
  "description": "Save a job to the user's Seekrly tracker or move it through the pipeline. Use when the user pastes a job posting, link or screenshot and wants to save, bookmark or track it, says they applied, got rejected, got an offer, or otherwise changes an application's status. Also for companies: everything at one company, adding an application or a company, editing, merging, deleting or suggesting a company for the shared directory.",
  "included_files": [],
  "name": "seekrly-track-job",
  "skill_md_contents": "---\nname: seekrly-track-job\ndescription: Save a job to the user's Seekrly tracker or move it through the pipeline. Use when the user pastes a job posting, link or screenshot and wants to save, bookmark or track it, says they applied, got rejected, got an offer, or otherwise changes an application's status. Also for companies: everything at one company, adding an application or a company, editing, merging, deleting or suggesting a company for the shared directory.\n---\n\n# Track a job in Seekrly\n\nFollow the ground rules in the `seekrly` skill (ids, confirmations, dates).\n\n## Saving a new job\n\n1. **Extract** from what the user shared - only what's actually there:\n   `company`, `role` (job title), `jobUrl`, `companyUrl` (the same job on the\n   company's own careers site, when `jobUrl` is a job board that sends applicants\n   there), `location`, `salary`, `experience`\n   (e.g. \"3-5 years\"), `employmentType` (Full-time, Contract…), `skills` (short\n   keywords, max 50), `description` (the job description text), `contactPerson`.\n   Don't invent missing fields; leave them out.\n2. **Check for duplicates**: `search` with the company name (and role). If the same\n   company + role already exists, show it and ask whether to update that one instead.\n3. **Pick the status**:\n   - Just saving / \"bookmark this\" → `Bookmarked` (the default).\n   - \"I applied\" → `Applied`, with `appliedDate` (`YYYY-MM-DD`, not in the future).\n     Ask for the date if it wasn't today and they didn't say.\n   - Mid-application → `Applying`.\n4. **Resume used** (only when applied): if the user names one, resolve it with\n   `list_resumes` and pass `resumeId`; otherwise the default resume is recorded.\n5. **Show what you'll save** and ask \"Save it, or change something?\": role,\n   company, status, applied date (in words), location, salary, experience,\n   employment type, skills and the job link, plus the first lines of the\n   description. Leave out fields you don't have.\n6. After a yes, call `create_application` and confirm in one line: role,\n   company, status.\n7. **Offer next steps** (one short line, don't do them unasked): add the recruiter\n   as a contact (`create_contact` with `applicationIds`, or `update_contact` with\n   `linkApplicationIds` if they're already saved), plan a follow-up, or\n   tailor a resume for it (`seekrly-tailor-resume`).\n\nIf the posting names a recruiter or hiring manager with an email or LinkedIn URL,\noffer to save them as a contact linked to the application (check `find_contacts`\nfirst).\n\n## Updating status\n\n1. Resolve the application (`search` or `list_applications` with `query`). If more\n   than one matches, ask which.\n2. Say what will change and ask (one line is enough, e.g. \"Mark Backend Engineer\n   at Acme as Rejected?\"), then call `update_application` with only the changed\n   fields, e.g.\n   `{ applicationId, status: \"Rejected\" }`. Moving to Applied or later without an\n   `appliedDate` on record: pass one (ask if unknown).\n3. For interviews use `create_interview` (see `seekrly-interview-prep`) - it moves the\n   application to Interviewing by itself.\n4. Useful extras when relevant: a note with the reason or feedback (`add_note` on the\n   application), or marking related follow-ups done.\n\n## Bulk updates\n\nFor \"mark everything with no reply for 30 days as No Response\": list first\n(`list_applications`, filter by status/date), show the user the matching list and\nask before updating each one.\n\n## Companies\n\nApplications and contacts with the same company name (ignoring case and endings\nlike Inc or Ltd) share one company, so saving a job creates its company. Find a\ncompany's id with `list_companies` (`query`) or `search_companies`.\n\n- **Everything at one company** (\"what do I have at Acme?\"): `get_company` -\n  profile, applications, people, interviews, follow-ups, notes and look-alike\n  companies. Filter `list_applications` or `find_contacts` by `companyId` for more.\n- **Add an application at a company** (\"add another role at Acme\"): collect the\n  job as in \"Saving a new job\", then `create_application` with that `companyId`\n  (and the company's name in `company`). To move an application to another of the\n  user's companies, `update_application` with the new `companyId`.\n- **Add a company before any job there** (\"track Acme, I want to work there\"):\n  `search_companies` first. Already saved (`mine`)? Use it. In the directory? Offer\n  `create_company` with that `directoryId` (its profile comes from there); otherwise\n  `create_company` with `name` and any website, careers page or industry the user gave.\n  Show what you'll save first.\n- **Edit a company**: `update_company` with only the fields that change (name,\n  website, careersUrl, socials, industry, locations, description; `socials` and\n  `locations` replace the whole list). Show before → after first. A company with\n  `inDirectory: true` only takes a new name; for wrong details, offer\n  `request_company_change` (say what's wrong, give the right values in `fields`;\n  show it to the user and send only after a clear yes).\n- **Directory**: `get_company` may return `directoryMatch` for an own company - offer\n  `link_company_to_directory` with that id (its profile then comes from the directory;\n  `directoryId: null` unlinks). To share an own company with other Seekrly users,\n  `suggest_company_for_directory` (ask first; only the public profile is shared, never\n  the user's applications, people or notes, and Seekrly reviews it first).\n- **Saved twice under different names**: `find_duplicate_companies`, show the groups\n  and ask which name to keep. Then `merge_companies` with `keepId` and `mergeIds`\n  (show what will merge and call only after a clear yes).\n  Applications, contacts and notes move to the kept company. If the user says a group\n  is really different companies, `dismiss_duplicate_companies` so it isn't suggested\n  again.\n- **Delete a company**: only one with no applications or contacts; otherwise offer to\n  merge it. `delete_company` also deletes its notes: ask first.\n- **Notes about a company** (culture, people, why the user is interested): `add_note`\n  with `target: \"company\"`.\n"
}