← Search

trigger.dev Connector for Muse
Developer tools 🧪 Install ran in our test sandbox · Nov 11, 2026 📌 Pinned version: commit 6e31fd4
Install test only, on the date shown. This does not guarantee the code is safe.
🔎 Install prompt analysis · 2026-10-13 : uses API keys or tokens
⚙ Needs: A trigger.dev API key (dashboard > API keys…

trigger.dev Connector for Muse

Trigger background jobs, list runs, manage schedules.

At a glance
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.

Version:

@
Created by: @bluman1
Creator of the bluman1/muse-connectors catalog — 150 free open-source (MIT) connector skills for the Muse agent. Curated listings — credit to the creator.

Quick answer

trigger.dev Connector is a free, open-source Muse 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, and triggering a task starts real compute that can cost money, since runs are async.

⌁

Install

Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 6e31fd4

Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. 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/6e31fd44a71f9f28377a1460e64cd7483c3cce22/connectors/triggerdev Pinned version: install the code at commit 6e31fd44a71f9f28377a1460e64cd7483c3cce22 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder 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.

🔒 Security, provenance and what this touches
🧭 What this touches
  • It works with an API key or a token that you provide.
Install prompt analysis · 2026-10-13
🔒 Security and provenance
📌 Pinned version: commit 6e31fd4 · 2026-10-13
🧪 Install ran in our test sandbox · Nov 11, 2026
👁 Observed during the install test · Nov 11, 2026 : no network contact
🔎 Install prompt analysis · 2026-10-13 : uses API keys or tokens
What the scan found — excerpts from the install prompt
  • uses API keys or tokens — Prerequisites: A trigger.dev API key (dashboard > API keys; per-environment), kept in your Muse's secure vault · Prérequis : Une clé API trigger.dev (tableau de bord > clés API ; par environnement), conservée dans le coffre
🔎 Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Wanna be extra careful?

The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?

How to check a skill before installing →

Free and open-source (MIT): https://github.com/bluman1/muse-connectors/tree/main/connectors/triggerdev — Trigger background jobs, list runs, manage schedules.
✓

Verification certificate

Dated facts about what was checked for this listing, and how. This is not a safety certification.

Pinned version
6e31fd4 · 2026-10-13
Sandbox install test
Install ran in our test sandbox · Nov 11, 2026
Creator identity
Not verified
Fingerprint watch
Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
Install prompt analysis
2026-10-13 : uses API keys or tokens

Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify

?

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.