Skip to content

davila7/claude-code-templates / cli-tool/components/skills/career/workorai

workorai

Verified

WorkorAI talent marketplace skill: candidate job search and employer hiring with white-box match explanations via the WorkorAI MCP server (https://workorai.com/mcp). Use when the user asks to find a job, apply to jobs, respond to employer invitations, or when an employer wants to post jobs, search and evaluate candidates, invite them, and review applicants.

references/candidate-recipes.md

View on GitHub
# Candidate Recipes

Calling-order recipes for the common candidate flows. Tool names match
`references/candidate-catalog.md`. Every tool takes an optional `apiKey`
(used when the MCP client started anonymously) — omitted below for brevity.

## Recipe 1 — Find and apply

The core journey: search, inspect, apply.

```
candidate.search_jobs({ q?, workModel?, seniority?, jobType?, limit, offset })
  → present top entries by matchScore, with TWO links each:
       job page (jobUrl/url) and apply (applicationUrl/applyUrl)
  → on user pick:
       candidate.get_job({ jobId })        # full detail BEFORE applying
       candidate.apply_to_job({ jobId })    # idempotent; reused=true if re-apply
```

Guidance:
- Always show the job page link too — never apply-only. The user must be
  able to inspect the vacancy first.
- `apply_to_job` is gated on a completed + evaluated interview. On
  `GATE_LOCKED`/`GATE_EVALUATING`/`GATE_FAILED`, route to the onboarding
  step in `auth-flow.md` — do NOT retry blindly.
- `reused: true` means the candidate had already applied — tell them, don't
  imply a fresh application.

## Recipe 2 — Paginated / filtered search

Use when the first page isn't enough or the user has hard constraints.

```
candidate.search_jobs({ workModel: 'REMOTE', seniority: 'SENIOR', limit: 20, offset: 0 })
  → read page.hasMore
  → next page: same filters, offset += limit
```

Guidance:
- Filters are enums: `workModel ∈ {REMOTE, HYBRID, ON_SITE}`,
  `seniority ∈ {INTERN, JUNIOR, MIDDLE, SENIOR, LEAD, PRINCIPAL}`,
  `jobType ∈ {FULL_TIME, PART_TIME, CONTRACT, FREELANCE}`.
- Passing a free-text `q` (or having no completed interview) switches from
  semantic ranking to a recency BROWSE with NO fit score (`matchScore` is
  `null`). `seniorityFit` is always `UNKNOWN` and `matchReasons` always `[]`
  on BOTH paths (the combiner has no seniority signal).
- Page with `offset` + `page.hasMore`; don't refetch page 0.

## Recipe 3 — Gap analysis

Use when the user asks "am I a fit?" or "what am I missing?".

```
candidate.search_jobs({ q?/filters })       # or get_job for one known jobId
  → for a target job, read:
       matchedMustHaveSkills[]   # strengths to highlight
       missingMustHaveSkills[]   # gaps to discuss
       matchScore                # overall fit
  → frame missing skills as gaps to close, NOT as rejections.
```

Guidance:
- A missing must-have skill is a conversation, not a hard stop — the
  candidate can still apply. Be encouraging and concrete.
- Use `get_job` to pull the full `mustHaveSkills`/`niceToHaveSkills`/
  `qualifications` when the user wants the complete requirement list.

## Recipe 4 — Manage applications & invitations

Use when the user asks "where did I apply?", "any invites?", or wants to
respond to an employer.

```
candidate.get_applications()
  → branch on each row's status:
       INVITED   → candidate.accept_invitation({ jobId })   # → APPLIED
                   or candidate.decline_invitation({ jobId }) # TERMINAL
       APPLIED   → candidate.withdraw_application({ jobId })  # soft exit
       DECLINED  → terminal (no re-invite possible)
       WITHDRAWN → terminal for this row (employer may re-invite)
```

Guidance:
- ⚠️ `decline_invitation` is TERMINAL — it blocks any future re-invite from
  that employer. Confirm with the user; if they're merely unsure, leave the
  invite open (do nothing) instead of declining.
- `withdraw_application` is the soft exit: WITHDRAWN is the one state an
  employer can re-invite from later.
- `accept_invitation` puts the user in the employer's applicant funnel —
  confirm before accepting.
- All four are idempotent — a repeated call on an already-final row succeeds
  without changing anything.

## Recipe 5 — Saved jobs (shortlist)

Use to build and review a personal shortlist.

```
candidate.set_saved_job({ jobId, saved: true })    # bookmark
candidate.set_saved_job({ jobId, saved: false })   # remove
candidate.get_saved_jobs()                          # PUBLISHED-only list
```

Guidance:
- `set_saved_job` is a desired-state setter, NOT a toggle — always pass an
  explicit `saved` boolean.
- `get_saved_jobs` omits jobs that were closed/archived after saving (the
  bookmark persists, the listing filters). A vanished entry = unpublished,
  not unsaved.

## Recipe 6 — Present results (Agent Pick)

Use after `candidate.search_jobs` returns SCORED rows. Don't dump a flat list —
lead with one strongest `Agent Pick`, then brief secondary matches.

Template (scored rows only):

```md
Agent verdict: I'd look at <Role> at <Company> first.

⭐ Agent Pick
<Role> · <Company> · <Salary> · <Remote>      (job facts, not fit %)
match 88%   (Best)                            (matchScore; band ONLY from the tier you queried, else omit)

Fit Breakdown
Overall fit        ████████░░  88%            matchExplanation.score
Must-have skills   █████████░  6/7            count: matchedMust/(matchedMust+missingMust); fill: mustCoverage
Nice-to-have       ███████░░░  4/6            count: matchedNice/(matchedNice+missingNice); fill: niceCoverage
Verified in interview: Go, PostgreSQL, gRPC   matchExplanation.verifiedSkills

Why you stand out: …   matchExplanation.matchedMust + verifiedSkills
Gap to apply: …        matchExplanation.missingMust
Positioning / Agent view: …   matchExplanation.rationale

[View Role](jobUrl) · [Apply](applicationUrl)
```

Field rules:
- Every bar/line binds to a real `matchExplanation` field (present on SCORED
  rows only). Counts come from the skill arrays (`matched*`/`missing*`), bar
  fill from the coverage fractions, overall from `score`. No fabricated axis.
- DROP dims with no backing field: seniority (`seniorityFit` is always
  `UNKNOWN`), salary-fit, remote-fit, company-fit, "role direction", and any
  "chance to get hired %". Salary/remote/seniority show as job FACTS only.
- The per-row band word (`Best`/`Good`/`Weak`) is NOT a serialized field — use
  it only when you passed a `tier`, else omit. Never recompute it from a
  hardcoded score threshold.

Honesty-guard (no-score browse):
- A free-text `q`, or a not-yet-interviewed candidate, returns
  `matchScore: null` (recency browse, no `matchExplanation`). Show a plain list
  — NO bars — and say why, split by cause:
    - no / unevaluated interview → "finish your interview for ranked matches";
    - free-text `q` on an interviewed candidate → "free-text search browses by
      recency — drop the query or use the structured filters to get ranked
      Agent Picks back".

Secondary matches: keep brief — band + match% + one-line why/risk + a compact
`[View Role](…) · [Apply](…)` line.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall