Update to Standout

{
  "description": "Find open startup roles on the Standout job board, get the user introduced to the founders, and help a connected Standout candidate with their matches. Use when someone wants to find a job, compare roles, asks what a startup is hiring for, or asks about their Standout matches or profile.",
  "included_files": [],
  "name": "find-startup-jobs",
  "skill_md_contents": "---\nname: find-startup-jobs\ndescription: Find open startup roles on the Standout job board, get the user introduced to the founders, and help a connected Standout candidate with their matches. Use when someone wants to find a job, compare roles, asks what a startup is hiring for, or asks about their Standout matches or profile.\nmetadata:\n  short-description: Find startup jobs on Standout and meet the founders\n---\n\n# Find startup jobs\n\nHelp the user find open roles at startups on Standout, understand them, and\nget introduced to the founders instead of applying cold.\n\n## Workflow\n\n1. **Understand what they want.** You need a role keyword. Location or\n   remote, minimum salary, visa sponsorship and job type are useful but\n   optional. Ask one short question only if the role itself is unclear;\n   otherwise search straight away and refine afterwards.\n2. **Search with `search_jobs`.** Turn the request into filters:\n   - `query` is a short title keyword (`backend`, `product designer`,\n     `data`), never a sentence. For \"backend or platform roles\", make two\n     calls.\n   - `remote_only: true` for remote roles. `location` accepts only the listed\n     cities. For any other city, search without it and say the results are\n     not filtered by city.\n   - `min_salary` is annual base pay in the posting's currency.\n3. **Show the results.** For each role give the title, company, location and\n   salary when known, and link its `url`. Lead with the closest fits. If\n   `hasMore` is true, offer the next page.\n4. **Go deeper with `get_job`** when the user asks about a specific role:\n   requirements, responsibilities, the company, compensation.\n5. **Get them introduced.** When they are interested in a role and have\n   connected their Standout account, call `approve_job_match` with the\n   role's `id` as `job_id` once they ask for it, and relay what it returns. Otherwise share the\n   role's `interestUrl`: signing in there lets Standout introduce them to the\n   founders directly.\n\n## With a connected Standout account\n\nConnecting is optional. The account tools ask the user to sign in the first\ntime they are called. MCP account access requires `talent:read` (and\n`talent:write` for actions).\n\n- **Right after they connect,** call `get_my_profile` in the same reply and\n  follow its `assistantGuidance`. Greet them, explain in two or three\n  sentences how Standout works (roles at venture-backed startups that fit\n  them, a direct intro to the founders when they say yes), say what Standout\n  already knows about them, and ask about what `stillToAsk` lists. If they\n  already answered one in this conversation, propose that value and save it\n  once they confirm.\n- **When they ask for advice on their search,** call `get_my_profile` so\n  suggestions fit what they want. Each save returns `assistantGuidance` with\n  the next step: once nothing is left to ask, start `trigger_job_matching`\n  and tell them you started a search, and unless `hadCallWithStandout` is\n  true, offer a ten-minute call with Standout at\n  https://standout.work/me/call.\n- **Their matches:** `list_my_matches` lists the roles Standout matched them\n  with; `get_match_details` reads one. Show every match you mention with\n  its card, in the first message that names it: put `shareCard.markdown` on its own line, unchanged. If your client shows that linked image as a plain link (Grok does), show the image `shareCard.imageUrl` instead, then `shareCard.url` on its own line. Only when a\n  match has no `shareCard`, link Standout's page for the role, `jobUrl`, on\n  its own line. Never link the role's posting (Work at a Startup, a careers\n  page, an ATS). Describe progress\n  only as each match's `status` and `assistantGuidance` allow.\n- **Keeping up:** `check_for_updates` is the one call for news. Call it when\n  they ask what's new or a conversation about their search starts, and pass\n  back its `nextSince` as `since`. If they want you to keep watch and your\n  host can schedule work, set up a recurring check, and stay quiet when\n  `changes` is empty.\n- **Acting for them:** `approve_job_match` and `reject_job_match` (yes or\n  no to a match, or an intro to a role from `search_jobs`),\n  `update_my_preferences` and `update_my_background` (only the fields they\n  changed), `trigger_job_matching` (a fresh search by Standout, about five\n  minutes; `latestMatchingRun` in `list_my_matches` says when it is done),\n  and the tools for pausing, interview and offer news and hiring-team\n  questions.\n  `reply_to_standout` (a first-person message to Standout's team) is the\n  last resort for a message they ask to send that no other tool covers. Call\n  these only after the user has clearly asked or decided; start the first\n  `trigger_job_matching` once they have given what matching needs. Relay what Standout returns as Standout's\n  answer and never say an intro or a next step has happened unless it says\n  so.\n- **Self-apply roles:** when `approve_job_match` returns\n  `next_step: \"apply_directly\"`, Standout does not introduce that role. Don't\n  stop at `apply_url`: help them apply, pick one founder from\n  `self_apply.people_to_contact` and draft a short LinkedIn note they send\n  themselves. Steps: https://standout.work/talent/skills/self-apply.md\n- **Problems with Standout itself:** when a Standout tool keeps failing after\n  one retry or returns something wrong, or the user asks you to report a\n  problem, call `report_standout_issue` once per problem with the tool and the\n  error verbatim. Send technical facts only. Tell the user you reported it,\n  not that it is fixed.\n\n## Rules\n\n- Only present roles that a tool returned. Never invent roles, salaries or\n  companies, and never fill in a salary the tool left empty.\n- Do not ask for a CV, contact details or other personal data. The tools do\n  not need them.\n- Tool arguments carry only the fields a tool asks for, with what the user\n  stated or confirmed in this conversation. Never send chat history,\n  transcripts or summaries of the conversation. Standout never reads the\n  conversation.\n- Ask about work authorization only when a role or search needs it, and only\n  whether they can work somewhere without sponsorship, never their citizenship\n  or visa type.\n- The account tools only ever see the connected user's own account. There is\n  no way to look up another person; say so if asked.\n- If nothing matches, say so and suggest one change: a broader keyword, fewer\n  filters, or remote instead of a city.\n- A role with `isOpen: false` has closed. Say so and offer similar open\n  roles.\n\nA requested Standout search produces suggestions, including during human recruiter follow-up. It does not submit applications, contact companies, or reopen an earlier decision. Read the native run outcome before reporting results; a failed save is not an empty search.\n"
}