recruit

name: recruit version: 0.2.31 description: > Recruitment management (ATS) component for zylos. Provides a web Kanban board for managing candidates through interview stages, with SQLite-backed role library, job profiles, resume storage, and interview evaluations. Use when the user mentions recruiting, hiring, candidates, resumes, interview scheduling, ATS, 招聘, 候选人, 简历, 面试, or asks to add / move / evaluate a candidate. type: capability

lifecycle: npm: true service: type: pm2 name: zylos-recruit entry: src/index.js data_dir: ~/zylos/components/recruit hooks: post-install: hooks/post-install.js pre-upgrade: hooks/pre-upgrade.js post-upgrade: hooks/post-upgrade.js preserve: - config.json - recruit.db - resumes/

upgrade: repo: zz-howard/zylos-recruit branch: main

config: optional: - name: RECRUIT_PORT description: HTTP port for the recruit service default: "3465"

http_routes:

• path: /recruit/* type: reverse_proxy target: localhost:3465 strip_prefix: /recruit

dependencies: []

Zylos Recruit

Web-based ATS (Applicant Tracking System) for managing candidates through interview stages. Kanban board UI + REST API + SQLite storage.

Features

• Role library — create roles, attach versioned job profiles
• Candidate Kanban — 6 columns: pending / scheduled / contacted / interviewed / passed / talent pool
• Resume storage — upload PDF, preview in-browser via pdf.js
• AI resume evaluation — multi-runtime (Claude/Codex/Gemini), configurable model & effort
• Interview evaluations — notes with author and verdict (yes/no for AI, pass/hold/reject for interview)
• Authentication — cookie-based session auth (scrypt) + API token for programmatic access

Usage

# Install
zylos add recruit

# Access
# Open https://<your-domain>/recruit/
# Password is printed during post-install; also in ~/zylos/components/recruit/config.json

API Quick Start

Programmatic access uses the API token stored in the component config. The token is generated on first service start if auth.api_token is missing.

TOKEN=$(jq -r '.auth.api_token' ~/zylos/components/recruit/config.json)
HOST="https://<your-domain>/recruit"

curl -s \
  -H "Authorization: Bearer $TOKEN" \
  "$HOST/api/companies"

Use Authorization: Bearer <api_token> on /api/* routes. The Bearer token does not grant access to the browser UI; UI pages use the cookie login flow.

API Reference

Detailed documentation in references/: