Emploive

View saved version →

---
name: find-jobs
description: Find current job openings on Emploive by role, level, place, company, or keyword, and show the newest matches with their job pages. Use when the user asks for jobs, internships, or openings.
---

Use this skill when the user wants to find open jobs or internships.

1. Read the request into search_jobs filters.
   - Put employment type in `role_types`: Full-Time, Internship, Co-Op, Part-Time, or Contract.
   - Put seniority in `experience_levels`: New Grad, Junior, Mid Level, Senior, Staff, or Principal. Internships have no level.
   - Put the job function in `position_types`, such as Software Engineer or Data Science.
   - Put places in `locations` and Remote, Hybrid, or On-Site in `work_models`.
   - Put company names in `companies`, or name the company in `query`.
   - Call list_filter_options only when a value is rejected or unclear.
2. Call search_jobs. Start with 10 results.
3. If search_jobs rejects a value, it lists the valid values. Pick the closest one and call it again. Do not ask the user to choose from a raw list.
4. Show the jobs as a short list: title, company, location, pay when present, and how long ago Emploive found the job. Link each title to its `url`, the Emploive job page, where the user applies.
5. If `has_more` is true, say that more jobs match and offer the next page.
6. Offer a tracker when the search is worth repeating, for example "I can email you new matches for this search." Use the job-alerts skill if the user agrees.

Do not invent jobs, pay, or dates. Report only what search_jobs and get_job return.

Referenced files: 1 — file references are metadata, not package contents.

View saved version →

---
name: job-alerts
description: Create, change, pause, or delete Emploive trackers, which email the user new jobs that match saved filters. Use when the user wants alerts, notifications, or to follow a search over time.
---

Use this skill when the user wants to be told about new jobs, or wants to manage the trackers they have.

1. For a new tracker, collect the filters as in the find-jobs skill. Use the current conversation's search when the user says "this search".
2. Name the tracker in a few words, such as "SF SWE internships".
3. Use one email a day unless the user asks for another cadence. Valid cadences in minutes: 5, 15, 30, 60, 180, 360, 720, 1440.
4. Call create_tracker. If the result has a `note`, tell the user in one sentence. It says when the user's plan slows the alerts down.
5. Confirm the tracker name, its filters in plain words, and the alert cadence. Show a few of `newest_matches` so the user sees the tracker works.
6. To change a tracker, call list_trackers to find its id, then update_tracker with only the fields that change. Pass `paused: true` to pause it.
7. Before delete_tracker, confirm with the user by name. Deleting stops its emails.

If a tool says a filter needs a different plan, tell the user that their plan does not include it, and continue without that filter if they agree. Do not describe prices or push an upgrade. Do not add links to pricing, trials, or checkout.

Referenced files: 1 — file references are metadata, not package contents.

View saved version →

---
name: review-tracker-matches
description: Show the newest jobs that match the user's Emploive trackers and help decide which to open. Use when the user asks what is new, what matches their alerts, or to catch up on their trackers.
---

Use this skill when the user wants to catch up on jobs that match their trackers.

1. Call list_trackers. If the user has none, offer to create one with the job-alerts skill.
2. Pick the tracker the user names. If they name none, go through the active trackers, newest first, and skip paused ones.
3. Call get_tracker_jobs for each tracker you review, 10 jobs at a time.
4. Group the jobs by tracker. For each job show title, company, location, pay when present, and how long ago Emploive found it, linked to its `url`.
5. Point out jobs found in the last day first; they are the most likely to still be open.
6. When the user asks about one job, call get_job and summarize the description: what the team does, requirements, and pay.

To browse visually, call open_emploive. It opens the Emploive view with the trackers and their jobs.

Referenced files: 1 — file references are metadata, not package contents.