trigger-job-pattern
Skill0 starsChanged 48 days agoMITView on GitHub
Define a Trigger.dev job contract the desk and app repo can share. Background work owned by a TypeScript codebase: scheduled syncs, durable retries, fan-out that should not live in n8n.
- Reads credentials
In this repository12 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- clay-table-designSkill
- competitor-teardownSkill
- deploy-surface-checkSkill
- fde-handoff-packSkill
- hermes-herdr-loopSkill
- icp-scorecardSkill
- jev-typesafe-briefSkill
- n8n-flow-scaffoldSkill
- signal-to-sequenceSkill
- weekly-pipeline-pulseSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 15
Document env dependencies by name only (CLAY_API_KEY, SUPABASE_URL, ...).
- Very specific: line 16
Write ops/<slug>/automation/trigger-<job>.md with the contract and a sample payload (redacted).
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Skill: trigger-job-pattern
Define a Trigger.dev job contract the desk and app repo can share.
When to use
Background work owned by a TypeScript codebase: scheduled syncs, durable retries, fan-out that should not live in n8n.
Steps
- Name the job (
enrichAccountBatch,mirrorSignalBoard) and the owning repo. - Specify payload schema (fields, types, max batch size) and result schema.
- Set retry: max attempts, backoff, and what is safe to retry vs poison-queue.
- Require an idempotency key derived from customer slug + batch id.
- Document env dependencies by name only (
CLAY_API_KEY,SUPABASE_URL, ...). - Write
ops/<slug>/automation/trigger-<job>.mdwith the contract and a sample payload (redacted). - Implement in the app repo; desk only tracks the contract and run notes.
Anti-patterns
- Fire-and-forget jobs with no idempotency
- Putting live secrets in the sample payload committed here
- Using Trigger.dev for one-off UI clicks better done in Clay
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

