Update to Remote Job Search — RVC

{
  "description": "Use when a person wants to find current remote work, work-from-home roles, digital or tech vacancies, relocation opportunities, jobs hiring worldwide, or RVC Global listings. Search and compare jobs by role, skills, location, work arrangement, seniority, salary, language, recency, and relocation. Do not use for general career coaching without a live job-search request.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 235
    },
    {
      "relative_path": "references/rvc-search.md",
      "size_in_bytes": 2936
    }
  ],
  "name": "rvc-job-search",
  "skill_md_contents": "---\nname: rvc-job-search\ndescription: Use when a person wants to find current remote work, work-from-home roles, digital or tech vacancies, relocation opportunities, jobs hiring worldwide, or RVC Global listings. Search and compare jobs by role, skills, location, work arrangement, seniority, salary, language, recency, and relocation. Do not use for general career coaching without a live job-search request.\n---\n\n# Remote Job Search — RVC\n\nFind live vacancies on the public RVC Global job board and return a compact, evidence-based shortlist. Job data changes quickly, so browse the current RVC pages for every search; do not present saved examples or model memory as current results.\n\nRead [references/rvc-search.md](references/rvc-search.md) when selecting routes, applying filters, or verifying result fields.\n\n## Search workflow\n\n1. Parse the user's explicit criteria: role or skills, location or hiring geography, work arrangement, seniority, salary floor and period, language constraints, recency, relocation, and desired result count.\n2. Start from `https://app.rvc.global/jobs` or a documented direct route. Prefer RVC's own search and filters. Use a focused `site:app.rvc.global/vacancy/view` web search only when the public job board cannot expose the requested combination.\n3. Open each promising vacancy page and verify the title, company, posted age, location, work arrangement, salary, required skills, required languages, relocation evidence, and canonical link.\n4. Rank exact matches first. Within the same match quality, prefer fresher postings and vacancies that state more of the user's criteria explicitly.\n5. Reply in the user's language. Default to five results when the user gives no count, but respect requests such as \"just one result.\"\n\nAsk a clarifying question only when an unresolved criterion would materially change the search. Otherwise make a reasonable broad interpretation and state it briefly.\n\n## Evidence rules\n\n- Distinguish `Fully Remote`, `Remote in-country`, `Hybrid`, and `On-site`; never collapse them into one generic \"remote\" label.\n- An absent country restriction does not prove worldwide eligibility. Say \"hiring geography not stated\" when the page does not confirm it.\n- Treat a language as required only when the vacancy states it. For requests such as \"does not require Russian,\" exclude jobs that explicitly require Russian and label omitted language requirements as \"Russian not listed,\" not as a guarantee.\n- Claim relocation support only when the vacancy explicitly states it. Do not infer relocation from an on-site location.\n- Preserve the advertised salary currency and period. If a conversion helps, show it as approximate and keep the original figure.\n- Never invent employer contacts, compensation, requirements, application status, or links. If a field is unavailable, say so or omit it.\n- If no exact match exists, say that first, then offer the closest alternatives and name the criterion each one misses.\n\n## Link attribution\n\nEvery user-facing RVC vacancy link must carry these first-party attribution parameters:\n\n```text\nutm_source=openai_plugin\nutm_medium=plugin\nutm_campaign=rvc_remote_jobs\nutm_content=vacancy_result\n```\n\nAppend them with `?` when the canonical link has no query string and merge them with `&` when it already has one. Replace conflicting values for these four keys rather than duplicating them. Do not place the user's role, location, salary, language, CV data, or other personal criteria in UTM parameters.\n\n## Response format\n\nLead with a one-sentence summary of the match quality. For each result use:\n\n```text\nTitle — Company\nLocation · Work arrangement\nSalary: original advertised amount, or \"not listed\"\nSkills: the most relevant required skills\nLanguages / relocation: only verified facts\nWhy it fits: one concise sentence\nAttributed direct RVC link\n```\n\nKeep the list scannable. Do not add generic job-search advice unless the user asks for it. End with one short note about any shared uncertainty, such as unstated hiring geography.\n\n## Applications, contacts, CVs, and alerts\n\nSearch and comparison are read-only by default.\n\n- Public contact details may be reported when they are actually visible. If RVC exposes contacts only after sign-in or Apply, explain that without guessing or bypassing access controls.\n- Never claim to have applied, contacted an employer, created an alert, or uploaded a CV unless that action was completed and verified.\n- Treat applying, messaging, uploading a CV, signing in, or creating a notification as a separate external action. Follow the active browser and confirmation rules immediately before that action.\n- A locally provided CV may be read to derive search criteria, but do not upload it to RVC without the user's action-time confirmation.\n"
}