Rolester Docs

Rolester is a local, skill-driven job-search workspace. A coding agent (Claude Code, Codex, or any AGENTS.md-aware tool) runs inside the Rolester workspace and drives a set of skills that cover every step of the job-search loop — from sourcing and vetting to tailoring, tracking, and interview prep.

The agent is the runtime. The CLI is the front door and validated helper surface. You paste a job posting (or a recruiter email, or a link) into the agent chat and say what you want to do. The skills handle the work. The CLI scaffolds the workspace, renders the dashboard, checks health, and exposes safe config helpers — it is not a job board or separate cloud service.

Quick start

npm install -g rolester
rolester start claude   # or: rolester start codex

That scaffolds your workspace, boots the dashboard at http://localhost:7777, and launches your agent with a starter message. Paste a job posting and say "evaluate this" — within seconds you get a verdict on whether to keep or cut it, how well it fits, whether the pay clears your floor, and what to do next.

Two reading tracks

Not sure where to start?

Go to Getting Started. It walks you from a fresh clone through your first job evaluation in under ten minutes.

Already running, want to go deeper?

• Guides — step-by-step walkthroughs for each main workflow
• Advanced — architecture, the agent contract, data model, and configuration
• Reference — every skill in one table, CLI command index, disclaimer

Key ideas

Body-read gate. Rolester does not tailor or apply until a job passes a real read of the posting. Title and keyword matches are triage, not truth. Before any artifact is generated, the gate weighs the posting against your own constraints and returns a keep/cut call, a fit score, a comp check, and a recommended next step — printed as a GATE / FIT / COMP / ACTION block, with further lines added when the posting warrants them (a comp anchor, a legitimacy warning).

Evidence-only tailoring. Resumes and cover letters are built exclusively from an evidence bank you supply during onboarding. The agent cannot invent facts. A placeholder-lint step blocks any artifact that contains an unresolved token.

Config-driven, field-neutral. Every preference — comp floor, excluded companies, role buckets, keep/cut signals — lives in your private candidate/ config files. The skills are the same for any candidate; your config is what makes them yours.

Local by default. Your data never leaves your machine. The candidate/ directory is gitignored. Comp inputs marked private never appear in any outbound artifact.