trigger.dev Connector for Muse
Trigger background jobs, list runs, manage schedules.
- What
- Trigger background jobs, list runs, manage schedules.
- Cost
- Free
- Needs
- A trigger.dev API key (dashboard > API keys; per-environment), kept in your Muse's secure vault (never paste secrets here). Note: trigger and cancel are writes — confirm the task, payload, or run ID first; triggering starts real compute that can cost money. Reading (runs, run, schedules) needs no confirmation. trigger.dev has a free tier.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
A Muse agent skill that manages your trigger.dev background jobs: list runs, check a run's status and output, trigger task runs, cancel runs, and list schedules. `trigger` and `cancel` are writes — confirmed with you first. Honest note: triggering a task starts real compute that can cost money. Runs are async — poll the run until it moves to COMPLETED or FAILED. trigger.dev has a free tier. Draft: written from trigger.dev's public API docs, not yet live-tested end-to-end — this listing's unverified status reflects that. No secrets in the repo.
Curated by Skill Harbor — free, open-source build (MIT) by @bluman1.
Version:
Install
Prerequisites: A trigger.dev API key (dashboard > API keys; per-environment), kept in your Muse's secure vault (never paste secrets here). Note: trigger and cancel are writes — confirm the task, payload, or run ID first; triggering starts real compute that can cost money. Reading (runs, run, schedules) needs no confirmation. trigger.dev has a free tier. No GitHub account needed unless listed here. Install "trigger.dev Connector for Muse" for me. A Muse agent skill for background jobs: trigger tasks, list runs, manage schedules. Repository: https://github.com/bluman1/muse-connectors/tree/main/connectors/triggerdev 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "triggerdev". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. save my trigger.dev API key in the vault). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.