AGENT SKILL

workorai

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.

License 许可
MIT
最近更新
2026-10-22
Stars
★ 1
Forks
0

01 前言 Front Matter

name
workorai
risk
critical
tags
[ "job-search", "hiring", "recruiting", "talent-marketplace", "mcp" ]
tools
[ "claude", "cursor", "gemini" ]
author
work0r-ai
source
community
license
MIT
category
productivity
date_added
2026-07-03
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.
source_repo
work0r-ai/agent-kit
source_type
community
license_source
https://github.com/work0r-ai/agent-kit/blob/main/skills/workorai/LICENSE.txt

03 SKILL.md 正文

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, employer.list_applicants, employer.get_applicant_detail, employer.set_review_status for pipeline work.

Step 3: Explain matches with white-box data

When presenting employer search results, keep the tier structure (best/good/weak) and surface each candidate's matchExplanation: fit score, interview-proven skills, gaps, and rationale. For deeper comparison, fetch per-candidate interview evidence with employer.get_candidate_evidence and employer.get_applicant_transcript.

Examples

Example 1: Candidate job search

User: "Find me remote TypeScript jobs and apply to the best one."
Agent: candidate.search_jobs(query="TypeScript", remote=true)
       → present ranked results → candidate.get_job(id)
       → confirm with the user → candidate.apply_to_job(id)

Example 2: Employer candidate discovery

User: "Who are the best candidates for my Senior Backend role?"
Agent: employer.search_candidates_for_job(jobId)
       → report Best tier with each candidate's fit score, proven
         skills, and gaps → employer.invite_candidate on approval

Best Practices

  • ✅ Confirm with the user before applying, inviting, or changing job status — these are visible, stateful marketplace actions.
  • ✅ Quote the white-box match explanation when recommending a candidate, so the employer sees why, not just a score.
  • ✅ Use request_access for key onboarding instead of asking users to paste credentials into chat.
  • ❌ Don't fabricate fit scores or ranks — only report what the tools return.
  • ❌ Don't apply to jobs or send invitations in bulk without explicit user approval.

Limitations

  • Requires a WorkorAI account and API key; tools fail without a valid key.
  • This skill does not replace environment-specific validation, testing, or expert review.
  • Stop and ask for clarification if required inputs, permissions, or safety boundaries are missing.

Security & Safety Notes

  • All operations go through the remote WorkorAI MCP server over HTTPS; the skill itself runs no shell commands.
  • Mutating tools (apply, withdraw, invite, publish, close, delete) should be preceded by an explicit user confirmation.
  • Treat API keys as secrets: store them in MCP client configuration, never in chat transcripts or committed files.

Additional Resources

04 同仓库更多 Skills

Hazek-dc
Hazek-dc/PresensiGuru_FaceNet_EMAR

testing-best-practices

Laravel test design and review. Use when selecting coverage, naming or structuring tests, choosing assertions or test data, isolating dependencies, testing HTTP or security boundaries, improving suite performance, or reviewing test value. Use framework guidance or search-docs for Pest and PHPUnit syntax.

★ 1
Hazek-dc
Hazek-dc/PresensiGuru_FaceNet_EMAR

tailwindcss-development

Always invoke when the user's message includes 'tailwind' in any form. Also invoke for: building responsive grid layouts (multi-column card grids, product grids), flex/grid page structures (dashboards with sidebars, fixed topbars, mobile-toggle navs), styling UI components (cards, tables, navbars, pricing sections, forms, inputs, badges), adding dark mode variants, fixing spacing or typography, and Tailwind v3/v4 work. The core use case: writing or fixing Tailwind utility classes in HTML templates (Blade, JSX, Vue). Skip for backend PHP logic, database queries, API routes, JavaScript with no HTML/CSS component, CSS file audits, build tool configuration, and vanilla CSS.

★ 1
Hazek-dc
Hazek-dc/PresensiGuru_FaceNet_EMAR

laravel-best-practices

Apply this skill whenever writing, reviewing, or refactoring Laravel PHP code. This includes creating or modifying controllers, models, migrations, form requests, policies, jobs, scheduled commands, service classes, and Eloquent queries. Triggers for N+1 and query performance issues, caching strategies, authorization and security patterns, validation, error handling, queue and job configuration, route definitions, and architectural decisions. Also use for Laravel code reviews and refactoring existing Laravel code to follow best practices. Covers any task involving Laravel backend PHP code patterns.

★ 1
Hazek-dc
Hazek-dc/PresensiGuru_FaceNet_EMAR

infer-conventions

Use this skill to analyze how a Laravel application is actually written and record its conventions as shared rules. Trigger when the user wants to detect, infer, document, or standardize project conventions or coding style, set up or grow `.ai/rules`, resolve mixed or conflicting patterns (e.g. "are we using Form Requests or inline validation?"), or onboard agents and teammates to "how we do things here". Covers: a systematic sweep of ~49 Laravel convention dimensions (validation, models, architecture, testing, frontend, database, console), open-ended house-pattern discovery, conflict reporting, and recording rules scoped to the right paths via the Boost `record-rule` MCP tool. Only run this skill when the user explicitly asks for it; never start a sweep as part of another task. Do not use for one-off code review, enforcing formatting a linter already handles, or editing `.ai/rules` files by hand.

★ 1
Hazek-dc
Hazek-dc/PresensiGuru_FaceNet_EMAR

inertia-react-development

Develops Inertia.js v2 React client-side applications. Activates when creating React pages, forms, or navigation; using <Link>, <Form>, useForm, or router; working with deferred props, prefetching, or polling; or when user mentions React with Inertia, React pages, React forms, or React navigation.

★ 1
Hazek-dc
Hazek-dc/PresensiGuru_FaceNet_EMAR

deploying-to-cloud

Deploys and manages Laravel applications on Laravel Cloud using the `cloud` CLI. Use when the user wants to deploy an app, ship to Cloud, create or manage applications, environments, databases, caches, object storage, queues, domains, instances, background processes, secrets, compute, scheduled tasks, or Laravel Cloud infrastructure; or check billing, usage, or spend. Triggers on deployment, shipping, Cloud management, environment setup, database provisioning, billing or usage queries, the `cloud` CLI, and Laravel Cloud deployment troubleshooting.

★ 1