Skill instructions
foundrole-job-search5.2 KB
View saved version →
---
name: foundrole-job-search
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.
---
# FoundRole job search
Use 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.
## Load the relevant workflow
Read only the reference needed for the current action:
| 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) |
Resolve these files within this skill on its originating MCP server, or within the installed skill directory. They are supporting instructions, not additional skills.
## Choose the capability
Use the tools actually exposed in this session and their current schemas. Model-facing tools handle conversation requests; app-only data tools belong to widgets.
| User intent | Capability |
|---|---|
| Search by criteria | `jobs_search`, using the full role title and the user's stated filters |
| Find roles matching the account's profile | `jobs_recommendations` |
| Examine a FoundRole result | `jobs_details` with its exact returned job identifier |
| Evaluate a posting found elsewhere | `jobs_analyze_external` with the available source detail |
| Compare jobs | `jobs_compare`; preserve each returned `comparisonRef` |
| Save and manage applications | Tracker tools through the application-management reference |
| 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.
## Preserve result context
- 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.
- 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.
- Use FoundRole for follow-up and refresh requests. A refresh means calling the corresponding FoundRole tool again with the same intent.
- When the user explicitl
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 7 — file references are metadata, not package contents.
foundrole-resume-check5.5 KB
View saved version →
---
name: foundrole-resume-check
description: Check how hiring software (an ATS parser) reads a resume with the FoundRole MCP app, and report what the parser extracted and what it lost. Use when a user asks whether their resume is ATS-friendly, why applications get no reply, whether a parser can read their PDF, what a recruiting system sees on their resume, or asks for a resume scan, resume score, or resume review. Also use when the user pastes resume text and wants it checked. Do not use it to rewrite or grade the content of a resume — this check reports machine readability, not writing quality.
---
# FoundRole resume check
`resume_check` reports which parts of a resume hiring software can read. Report exactly what it returns.
## When `resume_check` is not available
This skill can load while the FoundRole app itself is disabled or not connected, so `resume_check` is missing from the session. Tell the user the FoundRole app is not enabled in this client, and that turning it on in the client's app or plugin settings (or connecting `https://www.foundrole.com/mcp`) and starting a new session makes the check available. Do not simulate the parse, and do not present your own reading of the resume as a FoundRole result or band.
## Choose what to check
- When the resume text is already in the conversation — pasted by the user, or read from a file they shared — pass it as `resume_text`. If the text is too short, ask for the full text.
- Pass `resume_id` when the user has identified an owned upload or editable version by its FoundRole ID. An editable version is checked as plain text.
- With neither input, the check runs on the account's primary upload.
- Do not paraphrase, reformat, or clean up the resume before passing it. The check measures what a parser reads from the actual text, so an improved version measures the wrong document.
- Check one resume per call. To compare two versions, call the tool once per version and contrast the returned bands and findings.
## Read the result
The response carries `mode`, `band`, `findings`, nullable `parsedAs`, and optional actions in `studioContinuation`, `profileSetupUrl`, and `parserReportUrl` or `studioReportUrl`.
- `mode` says which document was read: `uploaded` (an upload), `version` (an editable version), `text` (the pasted text), `no_resume` (nothing to check), `processing` (the upload is still being read).
- `band` is `strong`, `good`, or `partial`. Report the band in plain words. It is a readability band, not a percentage and not a match score — do not convert it into one, and do not invent a number to accompany it.
- `findings` lists what the parse lost, each with its own `detail` and suggested `fix`. Report every returned finding with its detail and fix; do not summarize several findings into one line, and do not add a finding the tool did not return. A single `clean` finding means nothing significant was lost. The returned findings are the scope of this check; do not invent hidden findings or advertise a more complete report.
- `parsedAs`, when present, is what the parser extracted: detected job title, years of experience, recognized skills count, sections, and which contact channels were found. Present these as the parser's reading, not as facts about the person — "the parser found no phone number" rather than "you have no phone number". When it is null, report the band and returned findings without inventing parsed facts.
## Explain what the check covers
- Pasted or extracted text cannot establish whether the original PDF or DOCX layout parses correctly. State this limitation when the user asks about a file; never present the text check as a test against a named ATS.
- This is the mechanical read only. It does not judge wording, achievements, seniority, or fit for any role. If the user asks whether the resume is good, say what the parser reads and what it loses, and keep any writing advice clearly separate from the tool's output.
- Never state or estimate a score, percen
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 1 — file references are metadata, not package contents.
foundrole-resume-workflows2.74 KB
View saved version →
---
name: foundrole-resume-workflows
description: Use FoundRole to review a saved profile or resume, preview tailoring for a job, check evidence of job fit, explain a resume parser result, or start a cover letter grounded in saved experience.
---
# FoundRole resume and application workflows
| Request | Tool |
|---|---|
| Read the career profile on the account | `profile_get` with no arguments |
| Read the actual saved resume text | `resume_get` with an optional `resume_id` |
| Preview a tailoring improvement for a specific job | `job_application_preview` with `workflow: "tailoring"` |
| See which saved evidence supports fit for a specific job | `job_application_preview` with `workflow: "fit"` |
| Get a cover-letter starting point for a specific job | `job_application_preview` with `workflow: "cover_letter"` |
| Explain what a resume parser read or missed | `resume_check` |
## Choose the resume and posting
Use the exact `id` returned by `jobs_search` as `job_id` in an application preview, and pass `resume_id` for a specific saved version. Without `resume_id` these tools use the account's primary or only resume, or return version choices. If `resume_get` returns `nextOffset`, continue with the same `resume.id` as `resume_id`, the returned `revision`, and `nextOffset` as `offset`. A `restart` status means the saved text or requested page changed. A processing state means the upload is still being read.
If a personal read or preview asks for consent, reconnect FoundRole in the host and approve sharing the saved profile and resume. If the resume or posting is unavailable, ask for the intended source. When no evidence or requirement is returned, say what is missing. A gap in the saved evidence is not proof the person lacks the skill.
## Explain the preview
An application preview can return `requirement`, `resumeEvidence`, `evidenceGap` and `guidance`. Use those returned fields. Tailoring offers a specific change or clarification, fit describes the evidence that supports the requirement, and a cover-letter starting point uses the evidence the tool returned. Fit does not establish eligibility or predict a hiring decision.
When the response has a `continueUrl`, present `continueLabel` with it. If `savesJobOnOpen` is true, the link saves the posting to the tracker when opened. The preview itself only reads. The user chooses whether to open the continuation.
For parsing, `resume_check` takes `resume_id` for an owned resume or `resume_text` for text supplied in the conversation. With neither argument it checks the primary upload. Explain its `band`, the returned `findings` and their fixes, and `parsedAs` when present. `parserReportUrl` or `studioReportUrl` can open the same saved upload. Keep the parsing result separate from job fit and writing quality.
Referenced files: 1 — file references are metadata, not package contents.