pilot

Executes one autonomous job-search cycle by claiming, acting on, and journaling a single agenda item.

73|19|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/suxrobGM/jobpilot --skill pilot-suxrobgm
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pilot
Source: https://github.com/suxrobGM/jobpilot/tree/main/plugin/skills/pilot
Command: npx skills add https://github.com/suxrobGM/jobpilot --skill pilot-suxrobgm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Running an autonomous job-search agent requires a disciplined loop that senses pending work, acts on exactly one item, records results, and exits cleanly without leaking state between runs. This Skill encodes that cycle so the JobPilot host can re-invoke it perpetually while all state lives in the API. ## Core Features & Use Cases - Single-cycle autonomy: Fetches the ranked agenda, claims the top item with optimistic locking, executes one kind-specific procedure (job apply, search discovery, inbox review, networking follow-up, interview prep, and more), then journals and exits. - Kind-based procedures: Ships 19 per-kind instruction files covering board health probes, campaign scoring and strategy review, Upwork inbox sync, promotion drafting/posting, and question routing. - Resilient orchestration: Handles 409 claim conflicts, heartbeats long-running work, records structured journal entries with load-bearing detail markers, and always prints a machine-readable cycle sentinel. - Use Case: A user configures job-search goals once; the terminal host injects this Skill repeatedly, and each invocation discovers jobs, applies to one posting, or follows up with a recruiter, journaling every action for morning review. ## Quick Start Let the JobPilot terminal host inject the pilot skill so it fetches the current agenda and executes the top agenda item for this cycle.

Frequently Asked Questions about pilot

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How does the pilot skill run an autonomous job search?▼

Each invocation performs one cycle: refresh the agenda via POST /api/pilot/agenda/refresh, claim the top item, follow the matching kinds/<item.kind>.md procedure, journal action and cycle entries, release the claim, and print a [[JOBPILOT_CYCLE]] sentinel. The terminal host re-injects the skill for the next cycle.

What agenda item types can the pilot handle?▼

It ships 19 kind procedures including job.apply, search.discover, campaign.scorePending, campaign.strategyReview, inbox.review, interview.prep, interview.reply, networking follow-ups and warm intros, promo compose/post, queue.drain, board.health, upwork.syncInbox, and question.answered routing.

Does the pilot apply to jobs without user approval?▼

It applies autonomously within server-enforced caps, but parks jobs and posts a question when a worker returns needs_user, and never sends interview replies or networking messages without approval when autonomy is set to review. Draft promotions are never posted without user approval.

What happens when a claim returns a 409 conflict?▼

A 409 means the item was already claimed, the pilot was stopped, or the job was already applied. The skill re-fetches the agenda once, claims the next item, or treats the cycle as empty and journals accordingly rather than retrying blindly.

Why does the pilot send heartbeats during long tasks?▼

Long branches like search.discover and job.apply heartbeat the claim via POST /api/pilot/claims/<id>/heartbeat after each page or worker return and at least every 10 minutes, so the orchestrator does not misread legitimate work as stuck and send a check-in.

Can the pilot run without the JobPilot API being available?▼

No. The setup step health-checks GET /api/health first and aborts with a standard message if the API is down, since all state, agenda, claims, and journaling live in the API.