[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F60AAASH9C89AXW7F9P48W":3,"skill-same:01M7F60AAASH9C89AXW7F9P48W":90},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7F60AAASH9C89AXW7F9P48W","chat-agent",null,"Build, migrate or debug AI chat agents on Trigger.dev (chat.agent, the chat transport, sessions, transcript storage, tool approvals, server, Slack and Linear callers). Use when a Trigger.dev project needs a chat assistant or agent, or code imports @trigger.dev\u002Fsdk\u002Fai or @trigger.dev\u002Fsdk\u002Fchat.","yigitkonur\u002Fplugin-trigger-dev","yigitkonur","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F9989650?v=4","01M7548A59WS0A38NSK8FASK46","Yigit Konur","01M7F603G80FW917N44KZ2KHCQ",0,"MIT","https:\u002F\u002Fgithub.com\u002Fyigitkonur\u002Fplugin-trigger-dev\u002Fblob\u002Fmain\u002Fskills\u002Fchat-agent\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: chat-agent\ndescription: Build, migrate or debug AI chat agents on Trigger.dev (chat.agent, the chat transport, sessions, transcript storage, tool approvals, server, Slack and Linear callers). Use when a Trigger.dev project needs a chat assistant or agent, or code imports @trigger.dev\u002Fsdk\u002Fai or @trigger.dev\u002Fsdk\u002Fchat.\nargument-hint: \"[what the agent should do, or what is broken]\"\nallowed-tools: Bash(trigger-ctx *) Bash(node *trigger-ctx.mjs *) Bash(node *trigger-ctx.mjs\" *) Bash(npx trigger.dev@latest whoami*) Bash(npx tsc --noEmit*) Bash(pnpm exec tsc --noEmit*) Bash(yarn tsc --noEmit*) Bash(bunx tsc --noEmit*)\n---\n\n# Trigger.dev: chat agents\n\nA chat agent is a durable multi-turn assistant that survives refreshes, deploys, idle gaps and crashes. Three parts: the agent task (`chat.agent`, which owns the turn loop), a durable **session** (`.in` and `.out` streams keyed on `chatId`, outliving runs), and the frontend **transport** (`useTriggerChatTransport` feeding `useChat`). A run suspends after `idleTimeoutInSeconds` (30 s by default) and resumes the same process; continuation runs boot cold and fire `onBoot`.\n\n## Invariants (check every snippet; the plugin's edit checks enforce several)\n\n1. **SDK ≥ 4.5.0.** Older projects update first (`npx trigger.dev@latest update`). `needsApproval` needs AI SDK 6 or newer.\n2. **`streamText` comes from `run`'s argument** (`run: async ({ messages, signal, streamText }) => …`), not from `\"ai\"`. The stock import silently loses compaction, steering and injection. Spreading `...chat.toStreamTextOptions()` into it is the supported alternative (and the only one in a custom agent).\n3. **Both server actions check ownership.** The token action and the start-session action must verify that the signed-in user owns the `chatId` before minting anything. Never authorise from `clientData`. Without this, one user can reach another user's chat.\n4. **`chat.local` is initialised in `onBoot`** (every fresh worker, continuations included), never in `onChatStart` or `onPreload`.\n5. **Declare tools on `chat.agent({ tools })`**, not only at the `streamText` call, so each tool's `toModelOutput` is re-applied across turns.\n6. **Persistence:** the platform snapshot by default (a self-hosted instance needs `OBJECT_STORE_*`), or `storage: TranscriptStorage` when your database is the source of truth. `hydrateMessages` is deprecated. The transcript format is roll-forward only, and `createLoadTranscriptAction` has no tenant check of its own: wrap it.\n7. **Retries:** keep `maxAttempts: 1`; `oomMachine` is the only retry path; tools must be idempotent because OOM retries and regenerate replay them.\n8. **Approvals and questions:** a question tool has no `execute`; an approval uses `needsApproval` plus `execute`. `onAction` returns nothing or `chat.turn()`, never a response.\n\n## Anchor and discovery\n\nUse the project facts in context (or `trigger-ctx detect --brief`): SDK version, `ai` major, frontend, Cloud or self-host. Infer first, ask second (at most two questions in the whole reply, next steps included, defaults for the rest; the repo usually answers):\n\n| # | Ask only if not inferable | Changes | Infer from |\n|---|---|---|---|\n| C1 | Migrating an existing chat route, or new? | `migrate-route-handler` vs `greenfield` | `app\u002Fapi\u002Fchat\u002Froute.ts`, `streamText` + `toUIMessageStreamResponse`, `resumable-stream`, `useChat` |\n| C2 | Who talks to the agent: a browser, Slack or Linear, other servers or agents? | transport vs `AgentChat` vs channels (`slack()`\u002F`linear()`, SDK ≥ 4.8.0) | `@slack\u002F*`, webhook routes, a frontend present |\n| C3 | Must chat history live in your database (list, search, edit, branch, audit)? | platform snapshot vs `storage` | prisma or drizzle schema with chat tables |\n| C4 | Do any tools have side effects that need approval? | `needsApproval`, idempotent tools | an existing tools map; `ai` major |\n| C5 | How do users authenticate, and who owns a chat? | the ownership check (mandatory) | next-auth, clerk, lucia, supabase |\n| C6 | Is first-reply latency important? | Preload vs Head Start vs neither | a warm server route, a serverless host |\n| C7 | Long conversations or very large tool outputs? | compaction, prompt caching, id references (about 1 MiB cap) | the domain (RAG, code, files) |\n| C8 | Cloud or self-hosted? | `baseURL`; `OBJECT_STORE_*` | the project facts |\n\nInferred without asking: the frontend (the React transport hook is React-only; other frameworks use the client protocol), the AI SDK major, the provider packages, the deploy host.\n\n## Choose the layer, the callers and the persistence\n\n- **Layer:** `chat.agent` (default) · `chat.createSession` (your own per-turn code; no lifecycle hooks, actions or approvals; Head Start works with it since 4.5.0 even though the `ai-chat\u002Fbackend` capability table still says no) · `chat.customAgent` with primitives (a custom protocol) · raw `sessions` (not chat-shaped).\n- **Callers:** a browser (React transport) · a server, script, Slack bot or another agent (`AgentChat`; deterministic `id` to resume) · a non-React or non-TS client (the client protocol over REST\u002FSSE) · Slack or Linear (`slack()` \u002F `linear()` channels, SDK ≥ 4.8.0, generally available; below that, offer the update or call `AgentChat` from your own handler).\n- **Persistence:** snapshot (default) · `storage: TranscriptStorage` (`runTranscriptStorageTests` to verify) · never new `hydrateMessages`.\n\n## Playbooks (read one, at `${CLAUDE_SKILL_DIR}\u002Fplaybooks\u002F\u003Cfile>`)\n\n| Situation | File |\n|---|---|\n| a new chat agent from scratch | `greenfield.md` |\n| an existing `useChat` + route handler to move | `migrate-route-handler.md` |\n| history in your database, list\u002Fsearch\u002Fedit | `persistence.md` |\n| tool approvals, questions to the user, undo\u002Fedit actions | `approvals-and-questions.md` |\n| Slack, Linear, server callers, other agents | `server-and-channel-callers.md` |\n| the first reply is slow | `fast-first-reply.md` |\n| long conversations, big tool outputs, caching | `long-conversations.md` |\n| crashes, OOM, recovery, deploys mid-conversation | `resilience.md` |\n| sub-agents, skills, code sandboxes | `sub-agents-tools-sandbox.md` |\n| tests, a live smoke test, readiness to ship | `test-verify-ship.md` |\n\n## Verify before you write, answer in the bridge format\n\nResolve every API name with `trigger-ctx docs \u003Ctopic or name>` (a name returns whether the installed types declare it, any `@deprecated` note, and the pinned-doc `file:line`) and read the local pinned page (`node_modules\u002F@trigger.dev\u002Fsdk\u002Fdocs\u002Fai-chat\u002F…`) or the web `.md`; the chat API changes fast (changelog: https:\u002F\u002Ftrigger.dev\u002Fdocs\u002Fai-chat\u002Fchangelog). If no docs tier is reachable, still answer from the playbook and list every API name you could not check as unverified; never refuse for lack of docs. Answer as: *You're building X. Y fits because Z (not W, because …). Minimal shape (≤ 15 lines). Watch out for (≤ 3). Docs: local path · URL.* Name the environment when you test (`dev` unless the user says otherwise); a live smoke test is MCP `list_agents` → `start_agent_chat` → `send_agent_message` → `close_agent_chat`, and `start_agent_chat` in prod spends real LLM budget: ask first.\n","# Trigger.dev: chat agents\n\nA chat agent is a durable multi-turn assistant that survives refreshes, deploys, idle gaps and crashes. Three parts: the agent task (`chat.agent`, which owns the turn loop), a durable **session** (`.in` and `.out` streams keyed on `chatId`, outliving runs), and the frontend **transport** (`useTriggerChatTransport` feeding `useChat`). A run suspends after `idleTimeoutInSeconds` (30 s by default) and resumes the same process; continuation runs boot cold and fire `onBoot`.\n\n## Invariants (check every snippet; the plugin's edit checks enforce several)\n\n1. **SDK ≥ 4.5.0.** Older projects update first (`npx trigger.dev@latest update`). `needsApproval` needs AI SDK 6 or newer.\n2. **`streamText` comes from `run`'s argument** (`run: async ({ messages, signal, streamText }) => …`), not from `\"ai\"`. The stock import silently loses compaction, steering and injection. Spreading `...chat.toStreamTextOptions()` into it is the supported alternative (and the only one in a custom agent).\n3. **Both server actions check ownership.** The token action and the start-session action must verify that the signed-in user owns the `chatId` before minting anything. Never authorise from `clientData`. Without this, one user can reach another user's chat.\n4. **`chat.local` is initialised in `onBoot`** (every fresh worker, continuations included), never in `onChatStart` or `onPreload`.\n5. **Declare tools on `chat.agent({ tools })`**, not only at the `streamText` call, so each tool's `toModelOutput` is re-applied across turns.\n6. **Persistence:** the platform snapshot by default (a self-hosted instance needs `OBJECT_STORE_*`), or `storage: TranscriptStorage` when your database is the source of truth. `hydrateMessages` is deprecated. The transcript format is roll-forward only, and `createLoadTranscriptAction` has no tenant check of its own: wrap it.\n7. **Retries:** keep `maxAttempts: 1`; `oomMachine` is the only retry path; tools must be idempotent because OOM retries and regenerate replay them.\n8. **Approvals and questions:** a question tool has no `execute`; an approval uses `needsApproval` plus `execute`. `onAction` returns nothing or `chat.turn()`, never a response.\n\n## Anchor and discovery\n\nUse the project facts in context (or `trigger-ctx detect --brief`): SDK version, `ai` major, frontend, Cloud or self-host. Infer first, ask second (at most two questions in the whole reply, next steps included, defaults for the rest; the repo usually answers):\n\n| # | Ask only if not inferable | Changes | Infer from |\n|---|---|---|---|\n| C1 | Migrating an existing chat route, or new? | `migrate-route-handler` vs `greenfield` | `app\u002Fapi\u002Fchat\u002Froute.ts`, `streamText` + `toUIMessageStreamResponse`, `resumable-stream`, `useChat` |\n| C2 | Who talks to the agent: a browser, Slack or Linear, other servers or agents? | transport vs `AgentChat` vs channels (`slack()`\u002F`linear()`, SDK ≥ 4.8.0) | `@slack\u002F*`, webhook routes, a frontend present |\n| C3 | Must chat history live in your database (list, search, edit, branch, audit)? | platform snapshot vs `storage` | prisma or drizzle schema with chat tables |\n| C4 | Do any tools have side effects that need approval? | `needsApproval`, idempotent tools | an existing tools map; `ai` major |\n| C5 | How do users authenticate, and who owns a chat? | the ownership check (mandatory) | next-auth, clerk, lucia, supabase |\n| C6 | Is first-reply latency important? | Preload vs Head Start vs neither | a warm server route, a serverless host |\n| C7 | Long conversations or very large tool outputs? | compaction, prompt caching, id references (about 1 MiB cap) | the domain (RAG, code, files) |\n| C8 | Cloud or self-hosted? | `baseURL`; `OBJECT_STORE_*` | the project facts |\n\nInferred without asking: the frontend (the React transport hook is React-only; other frameworks use the client protocol), the AI SDK major, the provider packages, the deploy host.\n\n## Choose the layer, the callers and the persistence\n\n- **Layer:** `chat.agent` (default) · `chat.createSession` (your own per-turn code; no lifecycle hooks, actions or approvals; Head Start works with it since 4.5.0 even though the `ai-chat\u002Fbackend` capability table still says no) · `chat.customAgent` with primitives (a custom protocol) · raw `sessions` (not chat-shaped).\n- **Callers:** a browser (React transport) · a server, script, Slack bot or another agent (`AgentChat`; deterministic `id` to resume) · a non-React or non-TS client (the client protocol over REST\u002FSSE) · Slack or Linear (`slack()` \u002F `linear()` channels, SDK ≥ 4.8.0, generally available; below that, offer the update or call `AgentChat` from your own handler).\n- **Persistence:** snapshot (default) · `storage: TranscriptStorage` (`runTranscriptStorageTests` to verify) · never new `hydrateMessages`.\n\n## Playbooks (read one, at `${CLAUDE_SKILL_DIR}\u002Fplaybooks\u002F\u003Cfile>`)\n\n| Situation | File |\n|---|---|\n| a new chat agent from scratch | `greenfield.md` |\n| an existing `useChat` + route handler to move | `migrate-route-handler.md` |\n| history in your database, list\u002Fsearch\u002Fedit | `persistence.md` |\n| tool approvals, questions to the user, undo\u002Fedit actions | `approvals-and-questions.md` |\n| Slack, Linear, server callers, other agents | `server-and-channel-callers.md` |\n| the first reply is slow | `fast-first-reply.md` |\n| long conversations, big tool outputs, caching | `long-conversations.md` |\n| crashes, OOM, recovery, deploys mid-conversation | `resilience.md` |\n| sub-agents, skills, code sandboxes | `sub-agents-tools-sandbox.md` |\n| tests, a live smoke test, readiness to ship | `test-verify-ship.md` |\n\n## Verify before you write, answer in the bridge format\n\nResolve every API name with `trigger-ctx docs \u003Ctopic or name>` (a name returns whether the installed types declare it, any `@deprecated` note, and the pinned-doc `file:line`) and read the local pinned page (`node_modules\u002F@trigger.dev\u002Fsdk\u002Fdocs\u002Fai-chat\u002F…`) or the web `.md`; the chat API changes fast (changelog: https:\u002F\u002Ftrigger.dev\u002Fdocs\u002Fai-chat\u002Fchangelog). If no docs tier is reachable, still answer from the playbook and list every API name you could not check as unverified; never refuse for lack of docs. Answer as: *You're building X. Y fits because Z (not W, because …). Minimal shape (≤ 15 lines). Watch out for (≤ 3). Docs: local path · URL.* Name the environment when you test (`dev` unless the user says otherwise); a live smoke test is MCP `list_agents` → `start_agent_chat` → `send_agent_message` → `close_agent_chat`, and `start_agent_chat` in prod spends real LLM budget: ask first.\n",{"name":5,"description":7,"allowed-tools":24,"argument-hint":25},"Bash(trigger-ctx *) Bash(node *trigger-ctx.mjs *) Bash(node *trigger-ctx.mjs\" *) Bash(npx trigger.dev@latest whoami*) Bash(npx tsc --noEmit*) Bash(pnpm exec tsc --noEmit*) Bash(yarn tsc --noEmit*) Bash(bunx tsc --noEmit*)","[what the agent should do, or what is broken]","main","de61c7e5bf67b2195147465b59e1f0e41813330b","skills\u002Fchat-agent","https:\u002F\u002Fgithub.com\u002Fyigitkonur\u002Fplugin-trigger-dev","https:\u002F\u002Fgithub.com\u002Fyigitkonur","https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fyigitkonur\u002F","HKEY_LOCAL_MACHINE","2026-11-02 14:22:03",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add yigitkonur\u002Fplugin-trigger-dev --skill chat-agent",{"tool":40,"command":41},"bunx","bunx skills add yigitkonur\u002Fplugin-trigger-dev --skill chat-agent",{"tool":43,"command":44},"pnpm","pnpm dlx skills add yigitkonur\u002Fplugin-trigger-dev --skill chat-agent","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fyigitkonur\u002Fplugin-trigger-dev\u002Fblob\u002Fmain\u002Fskills\u002Fchat-agent\u002FSKILL.md",true,[48,54,58,62,66,70,74,78,82,86],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"playbooks\u002Fapprovals-and-questions.md","REFERENCE","参考文档",4164,"https:\u002F\u002Fgithub.com\u002Fyigitkonur\u002Fplugin-trigger-dev\u002Fblob\u002Fmain\u002Fskills\u002Fchat-agent\u002Fplaybooks\u002Fapprovals-and-questions.md",{"path":55,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":56,"sourceHtmlUrl":57},"playbooks\u002Ffast-first-reply.md",4031,"https:\u002F\u002Fgithub.com\u002Fyigitkonur\u002Fplugin-trigger-dev\u002Fblob\u002Fmain\u002Fskills\u002Fchat-agent\u002Fplaybooks\u002Ffast-first-reply.md",{"path":59,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":60,"sourceHtmlUrl":61},"playbooks\u002Fgreenfield.md",4722,"https:\u002F\u002Fgithub.com\u002Fyigitkonur\u002Fplugin-trigger-dev\u002Fblob\u002Fmain\u002Fskills\u002Fchat-agent\u002Fplaybooks\u002Fgreenfield.md",{"path":63,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":64,"sourceHtmlUrl":65},"playbooks\u002Flong-conversations.md",3917,"https:\u002F\u002Fgithub.com\u002Fyigitkonur\u002Fplugin-trigger-dev\u002Fblob\u002Fmain\u002Fskills\u002Fchat-agent\u002Fplaybooks\u002Flong-conversations.md",{"path":67,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":68,"sourceHtmlUrl":69},"playbooks\u002Fmigrate-route-handler.md",4136,"https:\u002F\u002Fgithub.com\u002Fyigitkonur\u002Fplugin-trigger-dev\u002Fblob\u002Fmain\u002Fskills\u002Fchat-agent\u002Fplaybooks\u002Fmigrate-route-handler.md",{"path":71,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":72,"sourceHtmlUrl":73},"playbooks\u002Fpersistence.md",4222,"https:\u002F\u002Fgithub.com\u002Fyigitkonur\u002Fplugin-trigger-dev\u002Fblob\u002Fmain\u002Fskills\u002Fchat-agent\u002Fplaybooks\u002Fpersistence.md",{"path":75,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":76,"sourceHtmlUrl":77},"playbooks\u002Fresilience.md",4078,"https:\u002F\u002Fgithub.com\u002Fyigitkonur\u002Fplugin-trigger-dev\u002Fblob\u002Fmain\u002Fskills\u002Fchat-agent\u002Fplaybooks\u002Fresilience.md",{"path":79,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":80,"sourceHtmlUrl":81},"playbooks\u002Fserver-and-channel-callers.md",4952,"https:\u002F\u002Fgithub.com\u002Fyigitkonur\u002Fplugin-trigger-dev\u002Fblob\u002Fmain\u002Fskills\u002Fchat-agent\u002Fplaybooks\u002Fserver-and-channel-callers.md",{"path":83,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":84,"sourceHtmlUrl":85},"playbooks\u002Fsub-agents-tools-sandbox.md",4300,"https:\u002F\u002Fgithub.com\u002Fyigitkonur\u002Fplugin-trigger-dev\u002Fblob\u002Fmain\u002Fskills\u002Fchat-agent\u002Fplaybooks\u002Fsub-agents-tools-sandbox.md",{"path":87,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":88,"sourceHtmlUrl":89},"playbooks\u002Ftest-verify-ship.md",4420,"https:\u002F\u002Fgithub.com\u002Fyigitkonur\u002Fplugin-trigger-dev\u002Fblob\u002Fmain\u002Fskills\u002Fchat-agent\u002Fplaybooks\u002Ftest-verify-ship.md",[91,98,105,112,119,126],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M7F61CVT2DCWNXPEKKFTQPH7","ship","Deploy Trigger.dev tasks (trigger deploy) to staging, prod or a preview branch with a preflight, the right CI or integration pipeline, an explicit --env, and a verification step. Use when asked to deploy, ship or release the Trigger.dev tasks or jobs. Not for deploying the app itself to Vercel, Fly or another host.","https:\u002F\u002Fgithub.com\u002Fyigitkonur\u002Fplugin-trigger-dev\u002Fblob\u002Fmain\u002Fskills\u002Fship\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":19},"01M7F618DS2RCBCFX75RRAH2CH","new","Add one capability to an existing Trigger.dev project (a task, a schedule, a progress UI, an approval step, a webhook handler) and prove it runs.","https:\u002F\u002Fgithub.com\u002Fyigitkonur\u002Fplugin-trigger-dev\u002Fblob\u002Fmain\u002Fskills\u002Fnew\u002FSKILL.md",[],[],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":19},"01M7F60XZX1JEC6V2DT8S8VANA","init","Set up Trigger.dev in this repository with a short discovery, an explicit architecture decision, and a first task proven to run.","https:\u002F\u002Fgithub.com\u002Fyigitkonur\u002Fplugin-trigger-dev\u002Fblob\u002Fmain\u002Fskills\u002Finit\u002FSKILL.md",[],[],{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":19},"01M7F60S7KR91VW9C5E4KY4332","doctor","Check the Trigger.dev toolchain around this project (Node, CLI login and profile, MCP server, versions, duplicate official skills, self-host target, plugin install scope) and report what to fix.","https:\u002F\u002Fgithub.com\u002Fyigitkonur\u002Fplugin-trigger-dev\u002Fblob\u002Fmain\u002Fskills\u002Fdoctor\u002FSKILL.md",[],[],{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":19},"01M7F60HTN9QXE5T5WX1EWMC8D","diagnose","Find out why Trigger.dev runs or deploys misbehave (stuck QUEUED or PENDING_VERSION, failed, timed out, crashed or OOM, schedules not firing, 429s, CI deploy failures, chat history lost). Use when a Trigger.dev project shows an error, a run id such as run_abc123, or the user says a task did not run.","https:\u002F\u002Fgithub.com\u002Fyigitkonur\u002Fplugin-trigger-dev\u002Fblob\u002Fmain\u002Fskills\u002Fdiagnose\u002FSKILL.md",[],[],{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":130,"categories":131,"keywords":132,"publishedAt":19},"01M7F605TT9K0FBQPQMQ3XN54W","audit","Review a Trigger.dev codebase against the plugin's rule catalog (stale APIs, silent-failure patterns, config, deploy, cost) and write a findings report; optionally apply safe fixes.","https:\u002F\u002Fgithub.com\u002Fyigitkonur\u002Fplugin-trigger-dev\u002Fblob\u002Fmain\u002Fskills\u002Faudit\u002FSKILL.md",[],[]]