davila7/claude-code-templates / cli-tool/components/skills/career/workorai
workorai
VerifiedWorkorAI 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.
| File | Kind | Size |
|---|---|---|
| LICENSE.txt | markdown | 1.0 KB |
| SKILL.md | skill md | 9.5 KB |
| references/auth-flow.md | markdown | 10.2 KB |
| references/candidate-catalog.md | markdown | 12.4 KB |
| references/candidate-recipes.md | markdown | 6.6 KB |
| references/candidate-troubleshooting.md | markdown | 6.4 KB |
| references/employer-catalog.md | markdown | 19.6 KB |
| references/employer-recipes.md | markdown | 6.1 KB |
| references/employer-troubleshooting.md | markdown | 6.0 KB |
| references/troubleshooting.md | markdown | 5.1 KB |
| scripts/credential-store.mjsexecutable | script | 22.5 KB |
references/employer-recipes.md
View on GitHub# Employer Recipes
Calling-order recipes for the four common employer flows plus the job
lifecycle. Tool names match `references/employer-catalog.md`.
## Recipe 1 — Hire from a specific job (shortlist → explain → invite)
Use when the employer has a vacancy in mind and wants the agent to
find, evaluate, explain, and invite suitable candidates.
```
employer.search_candidates_for_job({ jobId, tier: 'best' })
# read tierCounts {best,good,weak}; cascade to tier:'good' then 'weak' only if
# you need more candidates. paginate WITHIN a band via page.hasMore (not total).
# if tierCounts.best === 0 (no exceptional match) the result carries `advisory` —
# relay it: suggest the employer review/relax the must-have skills. do NOT
# present a Good/Weak candidate as a Best.
→ for each shortlisted entry, explain from entry.matchExplanation:
# verifiedSkills[] = proven in the interview (lead with these)
# matchedMust[] / missingMust[] = coverage + gaps to probe
# rationale = a ready-to-quote sentence
employer.get_candidate_evidence({ jobId, userId }) # the few you shortlist
# facts[] + qas[] + interview.summary → write a deeper comparative review
employer.get_candidate({ userId })
# inspect existingApplications:
# - INVITED → already pending, skip
# - APPLIED → already in funnel, route to list_applicants
# - DECLINED → terminal, do not re-invite
# - WITHDRAWN → re-invite is allowed (service UPDATEs row)
# - (no entry) → fresh invite is fine
employer.invite_candidate({ jobId, candidateUserId })
→ employer.list_invitations({ jobId }) # confirm pending state
later, once the candidate has accepted:
→ employer.list_applicants({ jobId }) # source='INVITED'
```
Guidance:
- START with `tier:'best'` — these are the strongest (cover the required skills,
proven in interview). Cascading to `good`/`weak` is opt-in; do not dump the
whole pool. (Omit `tier` only for an explicit "show everyone" request.)
- Explain every recommendation from `matchExplanation` (our white-box evidence),
and deepen with `get_candidate_evidence` facts/Q&A for the shortlist — this is
the platform's value: an evidence-backed ranking, not a black-box score.
- `get_candidate_evidence` is the heavy artefact — call it ONLY for the handful
you shortlist, never the whole list.
- Empty Best (`tierCounts.best === 0`) is an honest signal, not an error: the
vacancy's requirements are strict. Relay the returned `advisory` (suggest moving
less-critical must-haves to nice-to-have) and work from the Good band — never
re-label a Good/Weak candidate as Best.
- Never invite more candidates than the user asked for in one batch.
## Recipe 2 — Hire from a free-form description
Use when the user describes the role in plain text but has not picked
a specific vacancy yet.
```
employer.search_candidates_by_query({ query })
→ present top entries to the user
→ on user pick:
employer.get_candidate({ userId }) # check existingApplications
(vacancy selection branch:)
either employer.list_jobs({ status: 'PUBLISHED' })
or employer.create_job({ rawText }) + employer.publish_job
employer.invite_candidate({ jobId, candidateUserId })
```
Guidance:
- `search_candidates_by_query` does NOT return match metadata. Use
Recipe 1 once a vacancy id is selected to get ranking.
## Recipe 3 — Funnel review
Use when the employer wants to triage applicants on a published job.
```
employer.list_applicants({ jobId })
→ for each row, surface status, reviewStatus, source, match
summary from candidate + interview slice.
→ on triage action:
employer.set_review_status({ applicationId, reviewStatus })
# 'SHORTLISTED' or 'HIRED' unlocks contact in next reads.
→ for shortlisted candidates:
employer.get_applicant_detail({ applicationId })
# full evidence bundle, contact now visible.
employer.get_applicant_transcript({ applicationId })
# optional, on user request.
```
Error guidance:
- `CONFLICT: NOT_APPLIED` from `set_review_status` means the row is
still INVITED (candidate has not accepted). Tell the user to wait
for acceptance; review controls activate only after.
- `CONFLICT: WITHDRAWN` means the candidate withdrew. Nothing to
review. Suggest `invite_candidate` to re-engage (allowed for
WITHDRAWN).
- Contact gating: `email`/`phone`/`linkedinUrl`/`githubUrl`/
`websiteUrl` are null until `reviewStatus ∈ {SHORTLISTED, HIRED}`.
Don't promise contact details before moving the row.
## Recipe 4 — Pending invites cleanup
Use when the employer is auditing outstanding invites or wants to
rescind an unanswered invitation.
```
employer.list_invitations({ jobId })
→ for each pending row (status INVITED):
employer.cancel_invitation({ jobId, candidateUserId })
# errors NOT_INVITED if candidate accepted/declined meanwhile
```
Guidance:
- After cancellation, the candidate disappears from `list_invitations`.
- Re-inviting a previously cancelled candidate creates a brand-new
application row (no DB row exists after cancel — unlike WITHDRAWN
which preserves history).
## Lifecycle recipe — Create through retire
```
employer.create_job({ rawText })
→ returns DRAFT job (Gemini parse, 5-30 s sync)
→ optional: employer.update_job({ jobId, fields: { ... } })
employer.publish_job({ jobId })
→ status DRAFT → PUBLISHED, publishedAt set
running:
Recipe 1/2/3 against the job
when filled or paused:
employer.close_job({ jobId })
→ status PUBLISHED → CLOSED, closedAt set
later, when no longer needed in the active list:
employer.archive_job({ jobId })
→ status CLOSED → ARCHIVED
to drop a DRAFT that was never published:
employer.delete_job({ jobId })
→ DRAFT-only; on non-DRAFT use close + archive instead.
```
Guidance:
- `update_job` whitelist excludes `rawInput` (audit-only) and
`dataSource` (auto-flipped to `USER_EDITED` on every agent update).
- `create_job` client timeout recovery: do NOT resubmit. Run
`employer.list_jobs({ status: 'DRAFT' })` and pick the newest row.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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: 472k | Updated | Claude CodeCodex | Verified | Install |
| 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: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| 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 available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |