Agent Skill Candidate Matching Guide

What this agent skill does

The vitae.build skill operationalizes candidate matching in your agent stack. Instead of manually triaging every role, your workflow sends requirements toPOST /api/v1/candidates/match and receives ranked candidates ready for recruiter review.

This is built for multi-agent workflows where one agent handles intake, another enriches context, and vitae.build executes high-signal matching.

Core API endpoint

Use the matching endpoint directly from your orchestration layer:

POST /api/v1/candidates/match

The endpoint is defined with a stable OpenAPI contract and the following schema set:

• MatchRequest
• MatchResponse
• MatchCandidate
• MatchFilters

How to wire it into an agent workflow

1. Capture a role brief from the source of truth (client email, ATS intake, or CRM ticket).
2. Convert that brief into a MatchRequest payload.
3. Call /api/v1/candidates/match and request a recruiter-friendly shortlist.
4. Route the results to your consultant channel (CRM note, Slack thread, or reply draft).

Real automation scenario: inbox to shortlist

A high-impact pattern is inbox triage automation. An inbox agent scans incoming client emails, detects new job descriptions, and triggers matching immediately.

Outcome: by the time a consultant opens the thread, a shortlist is already attached, reducing response latency and increasing submission velocity.

Usage limits by plan

• Professional (Pro): 30 calls/day
• Enterprise: 500 calls/day

Daily limits apply per organization and reset each day.

Direct candidate links in every response

Every match result includes a candidate_url field — a direct link to the candidate's full profile in vitae.build. Share these links with recruiters so they can review candidates immediately, without searching or navigating.

For candidates with multiple CV variants (profiles), the response also includes a profile_links array. Each entry contains a profile_url that deep-links to the candidate page with a specific profile pre-selected. This lets recruiters jump straight to the most relevant CV variant for the role — for example, a "Cloud Engineering" profile for infrastructure roles or a "DevOps" profile for platform engineering positions.

Example: candidate URLs and profile links

"candidate_url": "https://vitae.build/app/candidates/ab24...678",
"profile_links": [
  {
    "profile_id": "11111111-aaaa-...",
    "profile_name": "Cloud Engineering",
    "profile_url": "https://vitae.build/app/candidates/ab24...678?profile=11111111-aaaa-..."
  }
]

Screenshot checklist for your internal runbook

For maximum adoption, capture: (1) inbox/JD intake event, (2) request payload preview, (3) ranked match response, and (4) recruiter handoff surface.

Implementation tips

• Normalize location and seniority fields before request dispatch to improve relevance consistency.
• Log request IDs and filters so support can trace unexpected rankings quickly.
• Persist shortlist snapshots for QA, recruiter coaching, and auditability.