Community skillDraft — source instructions not independently live-testedWork & collaboration

Ashby for Meta Muse

Community draft proposes: Search Ashby public job boards without a key, or propose authenticated ATS reads and application creation. The pinned stage-move action is currently incompatible with Ashby’s documented API.

Guide description: Public Ashby job-board search is documented and credential-free. The pinned community skill also proposes authenticated candidate, job and application reads plus application creation. Its stage-move helper calls a stale endpoint and payload, so moving applications is not a supported working action.

Community draft. OpenTools has not verified a Muse installation or provider API result. Public job search does not require a key. Authenticated candidates, applications and changes require an admin-created API key with endpoint-specific permissions. The pinned stage-move action uses a stale endpoint and payload and should not be used until repaired.

View original source ↗

How to set it up

Paste a prompt

Draft — these instructions come from the linked source and have not been independently live-tested by OpenTools.

Source maturity: 🧪 Draft: written from Ashby's public API docs; not yet live-tested end-to-end.

Before you start

  • No key for public job-board search; an admin-created Ashby API key with endpoint-specific permissions is required for ATS data and changes

Steps

  1. Review the pinned connectors/ashby/SKILL.md and its Files list (SKILL.md, bin/ashby.py).
  2. For authenticated ATS actions, prepare an admin-created Ashby API key with the required candidates, applications, jobs and private-data permissions; provide it only through Muse’s secure flow if available.
  3. Ask Muse to fetch the pinned skill and its exact listed files. Treat this as an upstream proposed installation, not a verified one-click setup.
  4. Run the source status check `bin/ashby.py auth` (must return `"ok": true`); inspect the actual response before using any action. Do not use the pinned stage-move command until it is repaired to match `application.changeStage` and `interviewStageId`.

Prompt to paste into Muse

Inspect this community skill: https://raw.githubusercontent.com/bluman1/muse-connectors/6e31fd44a71f9f28377a1460e64cd7483c3cce22/connectors/ashby/SKILL.md
Read its Files manifest. If this Muse account supports custom skill installation and secure credentials, install exactly those files; otherwise report that the setup is unavailable. Collect credentials through Muse's secure credential flow; never ask me for raw keys in chat. Run the skill's status check and report the actual result.

Account access: API key via the secure credential flow (`credentials.request_api_access`); created in Ashby under Admin > API Keys. The exact scheme is HTTP Basic with the key as the username and a blank password (`Authorization: Basic base64("<key>:")`). New keys have NO permissions by default: grant the module scopes for the endpoints you use, or calls fail.

Allowed hosts: api.ashbyhq.com

Source status check: `bin/ashby.py auth` (must return `"ok": true`)

A successful source status check may verify only configuration or credentials; it is not proof of a working end-to-end integration.

Services it connects with

These are the services the connector uses.

← Browse all Muse connectors