checkr
Checkr API for background checks, candidates, invitations, packages, reports, and screening workflows. Use when user mentions "Checkr", "background check", "candidate screening", "report status", "packages", or "FCRA".
What this skill does
## Troubleshooting
If requests fail, run `zero doctor check-connector --env-name CHECKR_TOKEN` or `zero doctor check-connector --url https://api.checkr.com/v1/packages --method GET`.
## Official Docs
- API docs: https://docs.checkr.com/
- Background check API overview: https://checkr.com/our-technology/background-check-api
## Authentication
Connect the Checkr connector at [app.vm0.ai/connectors](https://app.vm0.ai/connectors). The connector provides:
- `CHECKR_TOKEN`: Checkr API key
Checkr uses HTTP Basic auth with the API key as the username and an empty password:
```bash
curl -u "$CHECKR_TOKEN:" https://api.checkr.com/v1/packages
```
Base URL:
```bash
https://api.checkr.com/v1
```
## Candidates
### Create a Candidate
Write the payload to `/tmp/checkr_candidate.json`:
```json
{
"first_name": "Jane",
"last_name": "Doe",
"email": "[email protected]"
}
```
Then:
```bash
curl -s -X POST "https://api.checkr.com/v1/candidates" \
-u "$CHECKR_TOKEN:" \
--header "Content-Type: application/json" \
-d @/tmp/checkr_candidate.json | jq .
```
### Get a Candidate
```bash
curl -s "https://api.checkr.com/v1/candidates/<candidate-id>" \
-u "$CHECKR_TOKEN:" | jq .
```
## Packages
### List Packages
Use packages to determine which screening package slug to request.
```bash
curl -s "https://api.checkr.com/v1/packages" \
-u "$CHECKR_TOKEN:" | jq .
```
## Invitations
### Create an Invitation
Invitations let Checkr collect candidate information through a hosted flow.
Write the payload to `/tmp/checkr_invitation.json`:
```json
{
"candidate_id": "<candidate-id>",
"package": "<package-slug>",
"work_locations": [
{
"country": "US",
"state": "CA",
"city": "San Francisco"
}
]
}
```
Then:
```bash
curl -s -X POST "https://api.checkr.com/v1/invitations" \
-u "$CHECKR_TOKEN:" \
--header "Content-Type: application/json" \
-d @/tmp/checkr_invitation.json | jq .
```
### Cancel an Invitation
```bash
curl -s -X DELETE "https://api.checkr.com/v1/invitations/<invitation-id>" \
-u "$CHECKR_TOKEN:" | jq .
```
## Reports
### Create a Report
Use reports when you already have candidate data and authorization to run the screen.
Write the payload to `/tmp/checkr_report.json`:
```json
{
"candidate_id": "<candidate-id>",
"package": "<package-slug>"
}
```
Then:
```bash
curl -s -X POST "https://api.checkr.com/v1/reports" \
-u "$CHECKR_TOKEN:" \
--header "Content-Type: application/json" \
-d @/tmp/checkr_report.json | jq .
```
### Get a Report
```bash
curl -s "https://api.checkr.com/v1/reports/<report-id>" \
-u "$CHECKR_TOKEN:" | jq .
```
## Guidelines
- Background checks are regulated. Only create invitations or reports after the user confirms the candidate authorization and required compliance flow.
- Prefer invitation flows when the candidate should supply their own PII.
- Treat candidate PII, report status, adjudication details, and screening results as sensitive data.
- Use test API keys and packages for integration testing whenever possible.
Related in Backend & APIs
jfrog
IncludedInteract with the JFrog Platform via the JFrog CLI and REST/GraphQL APIs. Use this skill when the user wants to manage Artifactory repositories, upload or download artifacts, manage builds, configure permissions, manage users and groups, work with access tokens, configure JFrog CLI servers, search artifacts, manage properties, set up replication, manage JFrog Projects, run security audits or scans, look up CVE details, query exposures scan results from JFrog Advanced Security, manage release bundles and lifecycle operations, aggregate or export platform data, or perform any JFrog Platform administration task. Also use when the user mentions jf, jfrog, artifactory, xray, distribution, evidence, apptrust, onemodel, graphql, workers, mission control, curation, advanced security, exposures, or any JFrog product name.
cupynumeric-migration-readiness
IncludedPre-migration readiness assessor for porting NumPy to cuPyNumeric. Use BEFORE substantial porting work begins when the user asks whether code will scale on GPU, whether they should migrate to cuPyNumeric, which NumPy patterns transfer cleanly, what must be refactored before porting, or mentions pre-port assessment, scaling analysis, or refactor planning. Inspect the user's source code, look up NumPy usage, cross-reference the cuPyNumeric API support manifest, and distinguish distributed-scaling-friendly patterns from blockers such as unsupported APIs, scalar synchronization, host round-trips, Python/object-heavy control flow, shape/data-dependent branching, and in-place mutation hazards. Produce a verdict of READY, LIGHT REFACTOR, SIGNIFICANT REFACTOR, or NOT RECOMMENDED, with concrete refactor pointers.
alibabacloud-data-agent-skill
IncludedInvoke Alibaba Cloud Apsara Data Agent for Analytics via CLI to perform natural language-driven data analysis on enterprise databases. Data Agent for Analytics is an intelligent data analysis agent developed by Alibaba Cloud Database team for enterprise users. It automatically completes requirement analysis, data understanding, analysis insights, and report generation based on natural language descriptions. This tool supports: discovering data resources (instances/databases/tables) managed in DMS, initiating query or deep analysis sessions, real-time progress tracking, and retrieving analysis conclusions and generated reports. Use this Skill when users need to query databases, analyze data trends, generate data reports, ask questions in natural language, or mention "Data Agent", "data analysis", "database query", "SQL analysis", "data insights".
token-optimizer
IncludedReduce OpenClaw token usage and API costs through smart model routing, heartbeat optimization, budget tracking, and native 2026.2.15 features (session pruning, bootstrap size limits, cache TTL alignment). Use when token costs are high, API rate limits are being hit, or hosting multiple agents at scale. The 4 executable scripts (context_optimizer, model_router, heartbeat_optimizer, token_tracker) are local-only — no network requests, no subprocess calls, no system modifications. Reference files (PROVIDERS.md, config-patches.json) document optional multi-provider strategies that require external API keys and network access if you choose to use them. See SECURITY.md for full breakdown.
resend-cli
IncludedUse this skill when the task is specifically about operating Resend from an AI agent, terminal session, or CI job via the official resend CLI: installing/authenticating the CLI, sending/listing/updating/cancelling emails, batch sends, domains and DNS, webhooks and local listeners, inbound receiving, contacts, topics, segments, broadcasts, templates, API keys, profiles, or debugging Resend CLI/API failures. Trigger on mentions of Resend CLI, `resend`, `resend doctor`, `resend emails send`, `resend domains`, `resend webhooks listen`, `resend emails receiving`, or agent-friendly terminal automation.
alibabacloud-odps-maxframe-coding
IncludedUse this skill for MaxFrame SDK development and documentation navigation on Alibaba Cloud MaxCompute (ODPS). Helps answer MaxFrame API, concept, official example, and supported pandas API questions; create data processing programs; read/write MaxCompute tables; debug jobs (remote or local); and build custom DPE runtime images. Trigger when users mention MaxFrame, MaxCompute with MaxFrame, ODPS table processing, DPE runtime, MaxFrame docs/examples, DataFrame/Tensor operations, or GPU runtime setup. Works for both English and Chinese queries about Alibaba Cloud data processing with MaxFrame.