ashby-workflows

Automate candidate progression through the Ashby recruitment pipeline via API endpoints.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/jjeremycai/claudekit --skill ashby-workflows
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ashby-workflows
Source: https://github.com/jjeremycai/claudekit/tree/main/skills/ashby-workflows
Command: npx skills add https://github.com/jjeremycai/claudekit --skill ashby-workflows

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill guides recruiters and hiring teams to efficiently manage candidate progression within the Ashby ATS, reducing manual coordination and delays.

Core Features & Use Cases

  • Candidate Pipeline Guidance: Help move candidates through standard stages (Sourced → Applied → Phone Screen → Interview → Offer → Hired) with clear steps.
  • Interview Scheduling & Archiving: Provide workflows for scheduling interviews, updating stages, and applying consistent archive reasons when needed.
  • Team Collaboration & Reporting: Coordinate hiring team actions and track progress across applications.

Quick Start

Use this skill to advance a candidate to the next stage, schedule an interview, or archive an application by providing the relevant IDs and stage information.

Frequently Asked Questions about ashby-workflows

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

FAQPage Schema
How do I automate candidate progression through the Ashby recruiting pipeline?

You can automate candidate progression in the Ashby recruiting pipeline by using API-driven operations to move candidates between stages, schedule interviews, and apply archive reasons. This workflow reduces manual coordination and delays for hiring teams.

How do I schedule interviews and update candidate stages in Ashby?

To schedule interviews and update candidate stages in Ashby, you provide the relevant application IDs and stage information. The workflow uses Ashby endpoints like interview_schedule_create and application_change_stage to execute these actions.

Can I use Ashby API endpoints to manage my candidate pipeline and applications?

Yes, you can manage your candidate pipeline and applications using Ashby API endpoints. The workflow supports candidate_create, application_list, interview_stage_list, and application_change_stage to coordinate hiring team actions.

What is the best way to archive applications and apply consistent archive reasons in Ashby?

The best way to archive applications in Ashby is through guided workflows that apply consistent archive reasons. This ensures hiring teams track decisions accurately across the candidate pipeline without manual errors.

Does this Ashby workflow tool support moving candidates from sourcing to hired stages?

Yes, this Ashby workflow tool supports moving candidates through standard stages from Sourced to Applied, Phone Screen, Interview, Offer, and Hired. It provides clear steps for advancing candidates at each phase.

Why does coordinating hiring team actions in Ashby require specific application IDs?

Coordinating hiring team actions in Ashby requires specific application IDs to accurately target candidate records. Supplying the correct IDs ensures that stage transitions and interview scheduling execute against the right applications.