job-search-and-apply

Job Search & Application Drafting

A repeatable workflow for finding job openings across a prioritized list of sources and turning each one into either a direct link or a ready-to-send application draft — never neither.

Before first use: gather the user's profile

This skill needs a few things from the user (once — reuse across runs, e.g. from memory, a config file, or by asking):

• Role/stack focus: what kind of roles to search for (title, core tech stack).
• Location & remote preference: home location, and whether to search local, remote, or both.
• Sources, in priority order: which job boards to check and in what order. Ask if not given; don't assume a default list — job boards are highly region- and industry-specific.
• Contact sign-off: email, phone, portfolio/site — used to sign drafted applications.
• Real, quantified experience to draw on for cover letters (achievements, metrics, skills) — pull from a resume, memory, or ask the user to point to a source. Never invent stats.
• Whether to name past employers in application content, or keep experience generic ("in a previous role," "I've built...") — ask once, remember the preference.

Step 1: Search, in the user's priority order

For each source in priority order:

• Prefer a direct connector/API if one is available and connected for that source.
• Otherwise, web_search for the role + location/remote qualifier on that specific site, then web_fetch the listing page(s) for full details (title, company, pay, remote status, post date).
• Capture the actual URL for each listing when the source provides one directly (many job boards do). Do not fabricate or guess at a URL — only pass along links returned by a real search or fetch.
• Some sources (large aggregators in particular) only surface listings via search snippets with no individually fetchable page. Note this explicitly rather than presenting a broken or fabricated link.
• If the user asks for remote-only, filter on the actual listing content, not just the title — watch for "remote" labels that mean remote-from-a-specific-country or fixed-timezone-hours rather than genuinely open. Flag anything like this explicitly instead of silently including it.
• If a source turns up nothing new, say so rather than skipping it silently — the user should know it was checked.
• Only expand beyond the user's given source list if they ask, or if the given sources return nothing relevant — confirm before broadening scope.