← Jobs by FoundRoleCONTENT HISTORY

Update to Jobs by FoundRole

Snapshot Nov 20, 2026 · 00:10 UTC · version 2.1.8

Collection source: downloaded plugin package.

WHAT CHANGED

Instructions updated for foundrole-job-search

Skill instructions — Now says: | Choosing a role, place or employer, or repairing an empty search | [search-criteria.md](references/search-criteria.md) | | Choosing a personalized feed or...

Observed in instructions or declared skills. Runtime behavior has not been tested.

Save Jobs by FoundRole and check future changes in Following.

Up to 3 plugins free · no card required.

All fields and original values.

Skill instructions

Before

Oct 24, 2026 · 12:50 UTC

Use FoundRole's canonical match score when present. Keep an assistant estimate separate and label it; an estimate cannot satisfy a condition requiring a FoundRole

After

Nov 20, 2026 · 00:10 UTC

| Choosing a role, place or employer, or repairing an empty search | [search-criteria.md](references/search-criteria.md) | | Choosing a personalized feed or helping with a returned profile setup step | [profile-recommendations.md](refere...

Supporting files

Before

Oct 24, 2026 · 12:50 UTC

[{"relative_path":"agents/openai.yaml","size_in_bytes":513},{"relative_path":"references/app-capabilities.md","size_in_bytes":4331},{"relative_path":"references/application-management.md","size_in_bytes":5997},{"relative_path":"reference...

After

Nov 20, 2026 · 00:10 UTC

[{"relative_path":"agents/openai.yaml","size_in_bytes":513},{"relative_path":"references/app-capabilities.md","size_in_bytes":4331},{"relative_path":"references/application-management.md","size_in_bytes":5997},{"relative_path":"reference...

Compare saved observations

Download comparison JSON

SKILL.md text changes

− removed · + added

--- before
+++ after
@@ -14,6 +14,9 @@
 | Situation | Reference |
 |---|---|
 | Connecting, missing tools, OAuth errors, unsupported features, text versus widgets, or an uncertain tool result | [app-capabilities.md](references/app-capabilities.md) |
+| Choosing a role, place or employer, or repairing an empty search | [search-criteria.md](references/search-criteria.md) |
+| Choosing a personalized feed or helping with a returned profile setup step | [profile-recommendations.md](references/profile-recommendations.md) |
+| Empty results, location errors, or widened results | [search-recovery.md](references/search-recovery.md) |
 | Saving internal or external jobs, changing application details, reminders, or email alerts | [application-management.md](references/application-management.md) |
 | Watching a saved search, handling new-job events, renewing or stopping a host task | [monitoring.md](references/monitoring.md) |
 
@@ -34,6 +37,7 @@
 | Schedule follow-up or email notifications | Reminder or job-alert tools through that reference |
 | Act on new matches in the host | Host event-task workflow through the monitoring reference |
 | Check resume machine readability | `resume_check`; follow its returned mode, findings and links |
+| Identify an employer by name or domain | `company_lookup`; use the confirmed candidate’s `lookupValue` in a job search |
 | Career guidance, company research or interview preparation | `knowledge_search` and its relevant returned articles; `knowledge_topics` for topic discovery |
 
 If a capability is unavailable, explain what is missing and use an available alternative only within the user's request. Skill loading alone does not connect the app or create a background task.
@@ -48,7 +52,7 @@
 
 ## Present the result
 
-Use FoundRole's canonical match score when present. Keep an assistant estimate separate and label it; an estimate cannot satisfy a condition requiring a FoundRole score. Use FoundRole's returned sponsorship history for canonical H-1B claims, separating it from a posting's explicit visa statement.
+Use FoundRole's canonical match score when present. If a match score is absent, describe the evidence the tool returned without supplying a substitute score. Use FoundRole's returned sponsorship history for canonical H-1B claims, separating it from a posting's explicit visa statement.
 
 Distinguish posted pay from market estimates. Treat fit, sponsorship, E-Verify and ghost-job signals as evidence with uncertainty, not guarantees. Keep those sources stable across turns unless returned data changes.
 
Full technical diff · 2 changed fields

changed /included_files

BEFORE
[
  {
    "relative_path": "agents/openai.yaml",
    "size_in_bytes": 513
  },
  {
    "relative_path": "references/app-capabilities.md",
    "size_in_bytes": 4331
  },
  {
    "relative_path": "references/application-management.md",
    "size_in_bytes": 5997
  },
  {
    "relative_path": "references/monitoring.md",
    "size_in_bytes": 7284
  }
]
AFTER
[
  {
    "relative_path": "agents/openai.yaml",
    "size_in_bytes": 513
  },
  {
    "relative_path": "references/app-capabilities.md",
    "size_in_bytes": 4331
  },
  {
    "relative_path": "references/application-management.md",
    "size_in_bytes": 5997
  },
  {
    "relative_path": "references/monitoring.md",
    "size_in_bytes": 7284
  },
  {
    "relative_path": "references/profile-recommendations.md",
    "size_in_bytes": 2751
  },
  {
    "relative_path": "references/search-criteria.md",
    "size_in_bytes": 2010
  },
  {
    "relative_path": "references/search-recovery.md",
    "size_in_bytes": 2652
  }
]

changed /skill_md_contents

BEFORE
"---\nname: foundrole-job-search\ndescription: Use when a user wants FoundRole job search, personalized recommendations, job or resume-fit analysis, salary or H-1B signals, ghost-job assessment, job comparisons, application tracking, reminders, email job alerts, or supported monitoring of new jobs through event-triggered tasks. Also use to analyze or save a posting found elsewhere, including partner listings, and for career questions about visas, resumes, salary, interviews or relocation. Search FoundRole when using this skill; another job board's own search is outside its scope.\n---\n\n# FoundRole job search\n\nUse FoundRole's returned data for job results, scores, tracker state, alerts and URLs. Carry the user's intent across search, evaluation, saving and follow-up.\n\n## Load the relevant workflow\n\nRead only the reference needed for the current action:\n\n| Situation | Reference |\n|---|---|\n| Connecting, missing tools, OAuth errors, unsupported features, text versus widgets, or an uncertain tool result | [app-capabilities.md](references/app-capabilities.md) |\n| Saving internal or external jobs, changing application details, reminders, or email alerts | [application-management.md](references/application-management.md) |\n| Watching a saved search, handling new-job events, renewing or stopping a host task | [monitoring.md](references/monitoring.md) |\n\nResolve these files within this skill on its originating MCP server, or within the installed skill directory. They are supporting instructions, not additional skills.\n\n## Choose the capability\n\nUse the tools actually exposed in this session and their current schemas. Model-facing tools handle conversation requests; app-only data tools belong to widgets.\n\n| User intent | Capability |\n|---|---|\n| Search by criteria | `jobs_search`, using the full role title and the user's stated filters |\n| Find roles matching the account's profile | `jobs_recommendations` |\n| Examine a FoundRole result | `jobs_details` with its exact returned job identifier |\n| Evaluate a posting found elsewhere | `jobs_analyze_external` with the available source detail |\n| Compare jobs | `jobs_compare`; preserve each returned `comparisonRef` |\n| Save and manage applications | Tracker tools through the application-management reference |\n| Schedule follow-up or email notifications | Reminder or job-alert tools through that reference |\n| Act on new matches in the host | Host event-task workflow through the monitoring reference |\n| Check resume machine readability | `resume_check`; follow its returned mode, findings and links |\n| Career guidance, company research or interview preparation | `knowledge_search` and its relevant returned articles; `knowledge_topics` for topic discovery |\n\nIf a capability is unavailable, explain what is missing and use an available alternative only within the user's request. Skill loading alone does not connect the app or create a background task.\n\n## Preserve result context\n\n- Keep exact job identifiers, result occurrence identifiers, tracked-job identifiers, search references and comparison references. Use the field each tool requests; these identifiers are not interchangeable.\n- Resolve “the second job” or a named role from shown results rather than asking the user for an identifier already available. Clarify only when several results match.\n- Use FoundRole for follow-up and refresh requests. A refresh means calling the corresponding FoundRole tool again with the same intent.\n- When the user explicitly requests external sources, label them separately. Never present web results or remembered listings as FoundRole results.\n- Read current state before a write when it is needed to identify the target or preserve existing information. Execute the authorized changes; clarify genuinely ambiguous targets or times.\n\n## Present the result\n\nUse FoundRole's canonical match score when present. Keep an assistant estimate separate and label it; an estimate cannot satisfy a condition requiring a FoundRole score. Use FoundRole's returned sponsorship history for canonical H-1B claims, separating it from a posting's explicit visa statement.\n\nDistinguish posted pay from market estimates. Treat fit, sponsorship, E-Verify and ghost-job signals as evidence with uncertainty, not guarantees. Keep those sources stable across turns unless returned data changes.\n\nPrefer a rendered widget without duplicating its full contents. In a text-only host, summarize the relevant returned jobs, fit evidence and uncertainties with returned links. Honor preview and account-access limits actually reported by the tool.\n\nFor guidance, cite relevant `knowledge_search` articles; say when none answer the question. A completed write, reminder, email alert or monitoring task requires a successful tool or host result. Report partial completion accurately.\n"
AFTER
"---\nname: foundrole-job-search\ndescription: Use when a user wants FoundRole job search, personalized recommendations, job or resume-fit analysis, salary or H-1B signals, ghost-job assessment, job comparisons, application tracking, reminders, email job alerts, or supported monitoring of new jobs through event-triggered tasks. Also use to analyze or save a posting found elsewhere, including partner listings, and for career questions about visas, resumes, salary, interviews or relocation. Search FoundRole when using this skill; another job board's own search is outside its scope.\n---\n\n# FoundRole job search\n\nUse FoundRole's returned data for job results, scores, tracker state, alerts and URLs. Carry the user's intent across search, evaluation, saving and follow-up.\n\n## Load the relevant workflow\n\nRead only the reference needed for the current action:\n\n| Situation | Reference |\n|---|---|\n| Connecting, missing tools, OAuth errors, unsupported features, text versus widgets, or an uncertain tool result | [app-capabilities.md](references/app-capabilities.md) |\n| Choosing a role, place or employer, or repairing an empty search | [search-criteria.md](references/search-criteria.md) |\n| Choosing a personalized feed or helping with a returned profile setup step | [profile-recommendations.md](references/profile-recommendations.md) |\n| Empty results, location errors, or widened results | [search-recovery.md](references/search-recovery.md) |\n| Saving internal or external jobs, changing application details, reminders, or email alerts | [application-management.md](references/application-management.md) |\n| Watching a saved search, handling new-job events, renewing or stopping a host task | [monitoring.md](references/monitoring.md) |\n\nResolve these files within this skill on its originating MCP server, or within the installed skill directory. They are supporting instructions, not additional skills.\n\n## Choose the capability\n\nUse the tools actually exposed in this session and their current schemas. Model-facing tools handle conversation requests; app-only data tools belong to widgets.\n\n| User intent | Capability |\n|---|---|\n| Search by criteria | `jobs_search`, using the full role title and the user's stated filters |\n| Find roles matching the account's profile | `jobs_recommendations` |\n| Examine a FoundRole result | `jobs_details` with its exact returned job identifier |\n| Evaluate a posting found elsewhere | `jobs_analyze_external` with the available source detail |\n| Compare jobs | `jobs_compare`; preserve each returned `comparisonRef` |\n| Save and manage applications | Tracker tools through the application-management reference |\n| Schedule follow-up or email notifications | Reminder or job-alert tools through that reference |\n| Act on new matches in the host | Host event-task workflow through the monitoring reference |\n| Check resume machine readability | `resume_check`; follow its returned mode, findings and links |\n| Identify an employer by name or domain | `company_lookup`; use the confirmed candidate’s `lookupValue` in a job search |\n| Career guidance, company research or interview preparation | `knowledge_search` and its relevant returned articles; `knowledge_topics` for topic discovery |\n\nIf a capability is unavailable, explain what is missing and use an available alternative only within the user's request. Skill loading alone does not connect the app or create a background task.\n\n## Preserve result context\n\n- Keep exact job identifiers, result occurrence identifiers, tracked-job identifiers, search references and comparison references. Use the field each tool requests; these identifiers are not interchangeable.\n- Resolve “the second job” or a named role from shown results rather than asking the user for an identifier already available. Clarify only when several results match.\n- Use FoundRole for follow-up and refresh requests. A refresh means calling the corresponding FoundRole tool again with the same intent.\n- When the user explicitly requests external sources, label them separately. Never present web results or remembered listings as FoundRole results.\n- Read current state before a write when it is needed to identify the target or preserve existing information. Execute the authorized changes; clarify genuinely ambiguous targets or times.\n\n## Present the result\n\nUse FoundRole's canonical match score when present. If a match score is absent, describe the evidence the tool returned without supplying a substitute score. Use FoundRole's returned sponsorship history for canonical H-1B claims, separating it from a posting's explicit visa statement.\n\nDistinguish posted pay from market estimates. Treat fit, sponsorship, E-Verify and ghost-job signals as evidence with uncertainty, not guarantees. Keep those sources stable across turns unless returned data changes.\n\nPrefer a rendered widget without duplicating its full contents. In a text-only host, summarize the relevant returned jobs, fit evidence and uncertainties with returned links. Honor preview and account-access limits actually reported by the tool.\n\nFor guidance, cite relevant `knowledge_search` articles; say when none answer the question. A completed write, reminder, email alert or monitoring task requires a successful tool or host result. Report partial completion accurately.\n"
Full snapshot data
{
  "description": "Use when a user wants FoundRole job search, personalized recommendations, job or resume-fit analysis, salary or H-1B signals, ghost-job assessment, job comparisons, application tracking, reminders, email job alerts, or supported monitoring of new jobs through event-triggered tasks. Also use to analyze or save a posting found elsewhere, including partner listings, and for career questions about visas, resumes, salary, interviews or relocation. Search FoundRole when using this skill; another job board's own search is outside its scope.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 513
    },
    {
      "relative_path": "references/app-capabilities.md",
      "size_in_bytes": 4331
    },
    {
      "relative_path": "references/application-management.md",
      "size_in_bytes": 5997
    },
    {
      "relative_path": "references/monitoring.md",
      "size_in_bytes": 7284
    },
    {
      "relative_path": "references/profile-recommendations.md",
      "size_in_bytes": 2751
    },
    {
      "relative_path": "references/search-criteria.md",
      "size_in_bytes": 2010
    },
    {
      "relative_path": "references/search-recovery.md",
      "size_in_bytes": 2652
    }
  ],
  "name": "foundrole-job-search",
  "skill_md_contents": "---\nname: foundrole-job-search\ndescription: Use when a user wants FoundRole job search, personalized recommendations, job or resume-fit analysis, salary or H-1B signals, ghost-job assessment, job comparisons, application tracking, reminders, email job alerts, or supported monitoring of new jobs through event-triggered tasks. Also use to analyze or save a posting found elsewhere, including partner listings, and for career questions about visas, resumes, salary, interviews or relocation. Search FoundRole when using this skill; another job board's own search is outside its scope.\n---\n\n# FoundRole job search\n\nUse FoundRole's returned data for job results, scores, tracker state, alerts and URLs. Carry the user's intent across search, evaluation, saving and follow-up.\n\n## Load the relevant workflow\n\nRead only the reference needed for the current action:\n\n| Situation | Reference |\n|---|---|\n| Connecting, missing tools, OAuth errors, unsupported features, text versus widgets, or an uncertain tool result | [app-capabilities.md](references/app-capabilities.md) |\n| Choosing a role, place or employer, or repairing an empty search | [search-criteria.md](references/search-criteria.md) |\n| Choosing a personalized feed or helping with a returned profile setup step | [profile-recommendations.md](references/profile-recommendations.md) |\n| Empty results, location errors, or widened results | [search-recovery.md](references/search-recovery.md) |\n| Saving internal or external jobs, changing application details, reminders, or email alerts | [application-management.md](references/application-management.md) |\n| Watching a saved search, handling new-job events, renewing or stopping a host task | [monitoring.md](references/monitoring.md) |\n\nResolve these files within this skill on its originating MCP server, or within the installed skill directory. They are supporting instructions, not additional skills.\n\n## Choose the capability\n\nUse the tools actually exposed in this session and their current schemas. Model-facing tools handle conversation requests; app-only data tools belong to widgets.\n\n| User intent | Capability |\n|---|---|\n| Search by criteria | `jobs_search`, using the full role title and the user's stated filters |\n| Find roles matching the account's profile | `jobs_recommendations` |\n| Examine a FoundRole result | `jobs_details` with its exact returned job identifier |\n| Evaluate a posting found elsewhere | `jobs_analyze_external` with the available source detail |\n| Compare jobs | `jobs_compare`; preserve each returned `comparisonRef` |\n| Save and manage applications | Tracker tools through the application-management reference |\n| Schedule follow-up or email notifications | Reminder or job-alert tools through that reference |\n| Act on new matches in the host | Host event-task workflow through the monitoring reference |\n| Check resume machine readability | `resume_check`; follow its returned mode, findings and links |\n| Identify an employer by name or domain | `company_lookup`; use the confirmed candidate’s `lookupValue` in a job search |\n| Career guidance, company research or interview preparation | `knowledge_search` and its relevant returned articles; `knowledge_topics` for topic discovery |\n\nIf a capability is unavailable, explain what is missing and use an available alternative only within the user's request. Skill loading alone does not connect the app or create a background task.\n\n## Preserve result context\n\n- Keep exact job identifiers, result occurrence identifiers, tracked-job identifiers, search references and comparison references. Use the field each tool requests; these identifiers are not interchangeable.\n- Resolve “the second job” or a named role from shown results rather than asking the user for an identifier already available. Clarify only when several results match.\n- Use FoundRole for follow-up and refresh requests. A refresh means calling the corresponding FoundRole tool again with the same intent.\n- When the user explicitly requests external sources, label them separately. Never present web results or remembered listings as FoundRole results.\n- Read current state before a write when it is needed to identify the target or preserve existing information. Execute the authorized changes; clarify genuinely ambiguous targets or times.\n\n## Present the result\n\nUse FoundRole's canonical match score when present. If a match score is absent, describe the evidence the tool returned without supplying a substitute score. Use FoundRole's returned sponsorship history for canonical H-1B claims, separating it from a posting's explicit visa statement.\n\nDistinguish posted pay from market estimates. Treat fit, sponsorship, E-Verify and ghost-job signals as evidence with uncertainty, not guarantees. Keep those sources stable across turns unless returned data changes.\n\nPrefer a rendered widget without duplicating its full contents. In a text-only host, summarize the relevant returned jobs, fit evidence and uncertainties with returned links. Honor preview and account-access limits actually reported by the tool.\n\nFor guidance, cite relevant `knowledge_search` articles; say when none answer the question. A completed write, reminder, email alert or monitoring task requires a successful tool or host result. Report partial completion accurately.\n"
}

SHA-256 of public snapshot: bdbe55b6a5d4f22e479d337bad92cb1662fc52b8f93c53a9a2d41bea7f9cd89b