workorai

name	workorai
description	WorkorAI talent-marketplace skill: candidates search jobs and manage applications; employers run the job lifecycle and get ranked candidate matches with white-box fit explanations.
category	productivity
risk	critical
source	community
source_repo	work0r-ai/agent-kit
source_type	community
date_added	2026-07-03
author	work0r-ai
tags	["job-search","hiring","recruiting","talent-marketplace","mcp"]
tools	["claude","cursor","gemini"]
license	MIT
license_source	https://github.com/work0r-ai/agent-kit/blob/main/skills/workorai/LICENSE.txt

WorkorAI

Overview

WorkorAI is a talent marketplace exposed to agents through an MCP server (streamable HTTP at https://workorai.com/mcp, listed on the official MCP Registry as io.github.work0r-ai/workorai). This skill routes requests by intent across the dual-role tool surface: 9 candidate.* tools (job search, job detail, applications, apply, invitations, saved jobs) and the employer.* tools (job lifecycle, candidate discovery, invitations, applicant review). Employer candidate discovery returns tiered rankings (best/good/weak) with a white-box match explanation per candidate — fit score, skills proven in interview, gaps, and a quotable rationale — instead of a black-box score.

When to Use This Skill

• Use when a user asks to find a job, search vacancies, apply to a position, or track their applications ("find me a job", "ищу работу").
• Use when an employer wants to post, publish, update, close, or archive a job on WorkorAI.
• Use when an employer asks to find, rank, compare, or evaluate candidates, or asks why a candidate matches a role.
• Use when a user needs to set up or troubleshoot the WorkorAI MCP connection and API key onboarding.

How It Works

Step 1: Connect the MCP server

Add the WorkorAI MCP server to your agent's MCP configuration. For Claude Code:

claude mcp add --transport http workorai https://workorai.com/mcp

If the user has no API key yet, call the request_access tool and follow the onboarding it returns.

Step 2: Route by role and intent

Detect whether the request is a candidate flow or an employer flow, then use the matching tool group:

• Candidate: candidate.search_jobs, candidate.get_job, candidate.apply_to_job, candidate.get_applications, candidate.accept_invitation / candidate.decline_invitation, candidate.withdraw_application, candidate.set_saved_job, candidate.get_saved_jobs.
• Employer: employer.create_job → employer.publish_job → employer.close_job / employer.archive_job for the lifecycle; employer.search_candidates_for_job or employer.search_candidates_by_query for discovery; employer.invite_candidate, , , for pipeline work.