CtrlK
BlogDocsLog inGet started
Tessl Logo

trigger-dev

You are a Trigger.dev expert who builds reliable background jobs with exceptional developer experience. You understand that Trigger.dev bridges the gap between simple queues and complex orchestration - it's "Temporal made easy" for TypeScript developers.

32

Quality

27%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/trigger-dev/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

18%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill is essentially a skeleton or outline with no substantive content. It names patterns, anti-patterns, and sharp edges but provides zero executable code, no concrete steps, and no actual guidance. The sharp edges table hints at solutions but cuts off before showing them, and the patterns section is just a list of titles with one-line descriptions.

Suggestions

Add complete, executable TypeScript code examples for each pattern (Basic Task Setup, AI Task with OpenAI, Scheduled Task) — these are the core value of the skill and currently contain nothing.

Fill in the Sharp Edges table solutions with actual code snippets showing the fix (e.g., show the actual timeout configuration, the idempotency key usage, the concurrency limit setup).

Add concrete anti-pattern examples showing the bad code and the corrected version, rather than just listing anti-pattern names as empty headers.

Remove the self-referential introductory paragraphs ('You've built AI pipelines...') and the bare keyword 'Capabilities' list, replacing them with actionable content that Claude can use.

DimensionReasoningScore

Conciseness

The introductory paragraphs explain what Trigger.dev is and the author's experience, which is unnecessary padding for Claude. The 'Capabilities' list is just keywords with no actionable content. However, the sharp edges table is reasonably concise. Overall, there's a mix of efficient and wasteful content.

3 / 5

Actionability

The skill is almost entirely vague and abstract. The 'Patterns' section lists pattern names with one-line descriptions but provides zero code examples, commands, or concrete guidance. The 'Sharp Edges' table references solutions with comments like '# Configure explicit timeouts:' but never shows the actual code. The anti-patterns section lists names with no content at all.

1 / 5

Workflow Clarity

There are no multi-step processes defined anywhere. The 'Patterns' section names workflows like 'Basic Task Setup' and 'AI Task with OpenAI Integration' but provides no steps whatsoever. There are no validation checkpoints, no sequences, and no feedback loops despite the skill covering batch processing and long-running tasks which are inherently risky operations.

1 / 5

Progressive Disclosure

The document has section headers providing some structure, but there are no bundle files and no references to external files for the detailed content that is clearly missing (patterns, anti-patterns, examples). The content that should exist somewhere simply doesn't exist at all — it's not inlined and not referenced elsewhere.

2 / 5

Total

7

/

20

Passed

Description

36%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description uses first-person voice ('You are') which violates the third-person requirement, and reads more like a persona prompt than a skill description. It lacks concrete actions, specific trigger terms, and any 'when to use' guidance. The mention of Trigger.dev provides some distinctiveness, but the overall description is too vague and promotional to effectively differentiate this skill in a large skill library.

Suggestions

Replace the persona-style framing with third-person action verbs listing concrete capabilities, e.g., 'Creates and configures Trigger.dev background jobs, sets up task retries, defines cron schedules, and orchestrates multi-step workflows in TypeScript.'

Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about Trigger.dev, background jobs, scheduled tasks, async workflows, job queues, or task orchestration in TypeScript projects.'

Remove subjective/marketing language like 'exceptional developer experience' and 'Temporal made easy' and replace with specific technical capabilities that help Claude distinguish this skill from other job queue or orchestration skills.

DimensionReasoningScore

Specificity

Names the domain (Trigger.dev, background jobs) but provides no concrete actions. Phrases like 'builds reliable background jobs' and 'bridges the gap between simple queues and complex orchestration' are vague and don't describe specific capabilities like creating tasks, configuring retries, or setting up cron jobs.

2 / 5

Completeness

Has a vague 'what' (builds background jobs with Trigger.dev) but completely lacks any 'when' clause or trigger guidance. There is no 'Use when...' statement, which per the rubric should cap completeness at 3, and the 'what' itself is too vague to merit even that.

2 / 5

Trigger Term Quality

Includes some relevant keywords like 'Trigger.dev', 'background jobs', 'orchestration', 'TypeScript', and 'Temporal', but misses many natural user phrases like 'scheduled tasks', 'cron jobs', 'queues', 'async tasks', 'job retries', or 'workflow automation'.

3 / 5

Distinctiveness Conflict Risk

Mentioning 'Trigger.dev' specifically provides some distinctiveness, but the broader terms like 'background jobs', 'orchestration', and 'TypeScript' could overlap with skills for other job queue systems (BullMQ, Inngest, etc.) or general TypeScript development skills.

3 / 5

Total

10

/

20

Passed

Validation

90%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.