Read and write trigger.dev: list runs, check run status, trigger tasks, cancel runs, list schedules. Trigger phrases: trigger.dev, background jobs.
npx skills add https://github.com/Anil-matcha/awesome-muse-connectors --skill triggerdev
Manage the user's trigger.dev background jobs: list runs, check a run's status and output, trigger task runs, cancel runs, and list schedules. Use when the user mentions trigger.dev or background jobs.
All commands go through bin/triggerdev.py:
bin/triggerdev.py auth # verify the API key
bin/triggerdev.py runs --limit 25 # list recent runs
bin/triggerdev.py run --id run_abc123 # show one run's status and output
bin/triggerdev.py trigger --task my-task --payload-json '{"x":1}' # trigger a task run
bin/triggerdev.py trigger --task my-task --payload-json '{}' --project-ref proj_abc123 # with a personal access token
bin/triggerdev.py cancel --run-id run_abc123 # cancel a run
bin/triggerdev.py schedules # list schedules
triggerdev (credential is collected as custom.triggerdev)credentials.request_api_access); created in the trigger.dev dashboard under API keys, sent in the standard Authorization header.api.trigger.devbin/triggerdev.py auth (must return "ok": true)trigger and cancel are writes: confirm the task, payload, or run ID with the user before running, unless standing permission exists. Triggering a task starts real compute that can cost money.trigger, poll run --id to watch the status move to COMPLETED or FAILED.--project-ref with trigger when the stored credential is a personal access token rather than a project API key.🧪 Draft: written from trigger.dev's public API docs; not yet live-tested end-to-end.
Take anil-matcha/triggerdev from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.