[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EW888FCSTSM4M4ERNF7G5C":3,"skill-same:01M7EW888FCSTSM4M4ERNF7G5C":45},{"skillNo":4,"name":5,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7EW888FCSTSM4M4ERNF7G5C","ams-trigger-dev",null,"TanNhatCMS\u002Fjarvis","TanNhatCMS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F113796420?v=4","01M753MV17KG5CD3152G3WQEQY","KietNT","01M7EKEDYVYQ6PWVJJMZ911VMX",0,"MIT","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-trigger-dev\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: trigger-dev\ndescription: Build reliable background jobs with Trigger.dev: task definition, scheduling, retries, and observability. Use when adding durable background work to a TypeScript application.\ncategory: workflow-automation\n---\n\n# Trigger.dev\n\n## Overview\n\nTrigger.dev is an open-source background job platform for TypeScript: define tasks in code, trigger via events\u002Fschedules, get retries and observability built in.\n\nIt solves the classic pain: background work (emails, webhooks, data syncs, AI pipelines) that's reliable, visible, and retryable — without building job infrastructure.\n\nModel: tasks as code, runs as durable executions, dashboard for monitoring, schedules and event triggers built in.\n\n## When to use\n\n- Adding background jobs to a TypeScript\u002FNext.js app\n- Replacing fragile cron scripts or queue DIY\n- Scheduled tasks (reports, syncs, cleanups) with monitoring\n- Event-driven workflows (on signup -> onboard sequence)\n- Long-running tasks (AI pipelines, video processing, bulk ops)\n\n## Core concepts\n\n- **Tasks as code.**\n  Define tasks with schemas (e.g., zod) for type-safe payloads. Tasks live with your app code — versioned, reviewed, tested like the rest.\n- **Triggers.**\n  Event triggers (from your app), schedules (cron), and manual. One task, multiple trigger sources — reuse the logic.\n- **Retries and idempotency.**\n  Automatic retries with backoff; design task bodies idempotent (safe on retry). Use idempotency keys for external side effects.\n- **Concurrency and queues.**\n  Control parallelism per task; queues for ordering and rate-limiting. Protect downstream APIs from thundering herds.\n- **Runs dashboard.**\n  Every execution visible: inputs, logs, timing, retries. Debugging production jobs without SSH-ing into servers.\n- **Schedules.**\n  Cron-like scheduling with timezone support. Replace scattered cron jobs with visible, monitored scheduled tasks.\n- **Environments.**\n  Dev\u002Fstaging\u002Fprod separation for tasks. Test tasks safely before they touch production data.\n- **Self-hosting option.**\n  Open source — self-host for data control. Managed cloud for zero ops. Choose by your constraints.\n\n## Practical workflow\n\n1. **Identify background work.**\n   List: what runs async today (crons, scripts, queue hacks)? What should? Prioritize by pain (failures, invisibility).\n2. **Define tasks.**\n   One task per job with typed payload schema. Name clearly (`send-welcome-email`, `sync-crm-contacts`). Keep tasks focused.\n3. **Wire triggers.**\n   Events from app code, schedules for periodic work. Start with one trigger per task; add more as patterns emerge.\n4. **Build idempotent bodies.**\n   Each task: validate input, check-before-act where possible, external calls with idempotency keys, structured logging.\n5. **Configure retries\u002Fqueues.**\n   Retry policy per task criticality; concurrency limits protecting downstream APIs; queues where ordering matters.\n6. **Test in dev.**\n   Run tasks locally\u002Fwith dev environment using real-shaped payloads. Verify retries by simulating failures.\n7. **Deploy and monitor.**\n   Ship with dashboard bookmarks; set up failure alerts to a watched channel. First week: watch runs closely.\n8. **Migrate crons gradually.**\n   Move one cron\u002Fscript at a time. Keep old and new running in parallel briefly; verify parity, then cut over.\n\n## Common pitfalls\n\n- **Non-idempotent tasks.**\n  Retries creating duplicate emails\u002Fcharges\u002Frecords. Idempotency isn't optional with automatic retries.\n- **No payload validation.**\n  Untrusted event data crashing tasks. Schema-validate at the boundary, every time.\n- **Unbounded concurrency.**\n  1,000 parallel tasks hammering a rate-limited API. Concurrency limits and queues exist — use them.\n- **Ignoring the dashboard.**\n  Failures visible in the dashboard, nobody watching. Alerts to a real channel, reviewed daily.\n- **Cron sprawl migration.**\n  Moving 30 crons at once. One at a time, verified, or you'll debug 30 new failure modes simultaneously.\n- **Secrets in task code.**\n  API keys hardcoded in task definitions. Environment secrets, never in code or logs.\n- **No dev\u002Fprod separation.**\n  Testing tasks against production data\u002FAPIs. Environments exist for a reason — use them.\n- **Fire-and-forget events.**\n  Triggering without confirming the task ran. For critical flows, verify completion or alert on absence.\n","# Trigger.dev\n\n## Overview\n\nTrigger.dev is an open-source background job platform for TypeScript: define tasks in code, trigger via events\u002Fschedules, get retries and observability built in.\n\nIt solves the classic pain: background work (emails, webhooks, data syncs, AI pipelines) that's reliable, visible, and retryable — without building job infrastructure.\n\nModel: tasks as code, runs as durable executions, dashboard for monitoring, schedules and event triggers built in.\n\n## When to use\n\n- Adding background jobs to a TypeScript\u002FNext.js app\n- Replacing fragile cron scripts or queue DIY\n- Scheduled tasks (reports, syncs, cleanups) with monitoring\n- Event-driven workflows (on signup -> onboard sequence)\n- Long-running tasks (AI pipelines, video processing, bulk ops)\n\n## Core concepts\n\n- **Tasks as code.**\n  Define tasks with schemas (e.g., zod) for type-safe payloads. Tasks live with your app code — versioned, reviewed, tested like the rest.\n- **Triggers.**\n  Event triggers (from your app), schedules (cron), and manual. One task, multiple trigger sources — reuse the logic.\n- **Retries and idempotency.**\n  Automatic retries with backoff; design task bodies idempotent (safe on retry). Use idempotency keys for external side effects.\n- **Concurrency and queues.**\n  Control parallelism per task; queues for ordering and rate-limiting. Protect downstream APIs from thundering herds.\n- **Runs dashboard.**\n  Every execution visible: inputs, logs, timing, retries. Debugging production jobs without SSH-ing into servers.\n- **Schedules.**\n  Cron-like scheduling with timezone support. Replace scattered cron jobs with visible, monitored scheduled tasks.\n- **Environments.**\n  Dev\u002Fstaging\u002Fprod separation for tasks. Test tasks safely before they touch production data.\n- **Self-hosting option.**\n  Open source — self-host for data control. Managed cloud for zero ops. Choose by your constraints.\n\n## Practical workflow\n\n1. **Identify background work.**\n   List: what runs async today (crons, scripts, queue hacks)? What should? Prioritize by pain (failures, invisibility).\n2. **Define tasks.**\n   One task per job with typed payload schema. Name clearly (`send-welcome-email`, `sync-crm-contacts`). Keep tasks focused.\n3. **Wire triggers.**\n   Events from app code, schedules for periodic work. Start with one trigger per task; add more as patterns emerge.\n4. **Build idempotent bodies.**\n   Each task: validate input, check-before-act where possible, external calls with idempotency keys, structured logging.\n5. **Configure retries\u002Fqueues.**\n   Retry policy per task criticality; concurrency limits protecting downstream APIs; queues where ordering matters.\n6. **Test in dev.**\n   Run tasks locally\u002Fwith dev environment using real-shaped payloads. Verify retries by simulating failures.\n7. **Deploy and monitor.**\n   Ship with dashboard bookmarks; set up failure alerts to a watched channel. First week: watch runs closely.\n8. **Migrate crons gradually.**\n   Move one cron\u002Fscript at a time. Keep old and new running in parallel briefly; verify parity, then cut over.\n\n## Common pitfalls\n\n- **Non-idempotent tasks.**\n  Retries creating duplicate emails\u002Fcharges\u002Frecords. Idempotency isn't optional with automatic retries.\n- **No payload validation.**\n  Untrusted event data crashing tasks. Schema-validate at the boundary, every time.\n- **Unbounded concurrency.**\n  1,000 parallel tasks hammering a rate-limited API. Concurrency limits and queues exist — use them.\n- **Ignoring the dashboard.**\n  Failures visible in the dashboard, nobody watching. Alerts to a real channel, reviewed daily.\n- **Cron sprawl migration.**\n  Moving 30 crons at once. One at a time, verified, or you'll debug 30 new failure modes simultaneously.\n- **Secrets in task code.**\n  API keys hardcoded in task definitions. Environment secrets, never in code or logs.\n- **No dev\u002Fprod separation.**\n  Testing tasks against production data\u002FAPIs. Environments exist for a reason — use them.\n- **Fire-and-forget events.**\n  Triggering without confirming the task ran. For critical flows, verify completion or alert on absence.\n",{},"main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-trigger-dev",1,"https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis","https:\u002F\u002Fgithub.com\u002FTanNhatCMS","https:\u002F\u002Fmrkiet.name.vn","2026-11-07 14:23:08",{"source":7,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add TanNhatCMS\u002Fjarvis --skill ams-trigger-dev",{"tool":37,"command":38},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill ams-trigger-dev",{"tool":40,"command":41},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill ams-trigger-dev","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-trigger-dev\u002FSKILL.md",true,[],[46,53,61,68,75,82],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":18},"01M7EWYJR0J8DARY7E59Z6Y9MV","web-scrape","Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open\u002Ffetch fails on JS-heavy pages, or when you need clean markdown\u002Fstructured extraction from a site. Requires FIRECRAWL_API_KEY.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fweb-scrape\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":57,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":18},"01M7EWYBN5P6F2AJG3FR24T9BP","design-taste-frontend","tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML\u002FCSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, \"AI-made\", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":18},"01M7EWY8FQFNQ2GB7NZZWGSSDX","test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-tdd\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":18},"01M7EWY5SHBFRH1HDHVWM9K7TV","systematic-debugging","Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-debugging\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":18},"01M7EWY3NM0Z0JAKS7HDZ24K66","requesting-code-review","Use when completing tasks, implementing major features, or before merging to verify work meets requirements","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-code-review\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":18},"01M7EWY0WRMWX4M9ZFY0WKC593","brainstorming","You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-brainstorming\u002FSKILL.md",[],[]]