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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/trigger-dev/SKILL.md

The canonical home for this skill is trigger-dev in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

11%Weight 40%Scale 1-5

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

The body is well-sectioned but hollow: it lists capabilities and edge-case titles yet provides virtually no executable code, commands, or sequenced workflow with validation. It reads as a scaffold awaiting real examples rather than a usable skill.

Suggestions

Fill each Pattern with a complete, copy-pasteable code example (task definition, OpenAI integration with retries, cron-scheduled task).

Expand Sharp Edges solutions into actual commands/snippets (e.g. `export async function task(...)`, `task.tool({ idempotencyKey: ... })`) instead of bare comments.

Add a sequenced workflow with a validation checkpoint for at least one batch/long-running scenario, and remove the duplicated persona paragraph.

DimensionReasoningScore

Conciseness

The body is short and sectioned, but the opening persona paragraphs ('You are a Trigger.dev expert...', 'You've built AI pipelines...') duplicate the frontmatter and add no actionable knowledge, matching 'mostly efficient but includes some unnecessary explanation'.

3 / 5

Actionability

The Patterns are bare titles with no code ('Basic Task Setup / Setting up Trigger.dev in a Next.js project'), and the Sharp Edges 'solutions' are inert comments ('# Configure explicit timeouts:') with no executable code or commands, matching 'entirely vague or abstract; only describes rather than instructs'.

1 / 5

Workflow Clarity

No multi-step sequence exists anywhere in the body and there are no validation/checkpoint steps despite the skill covering batch and long-running tasks; this fits 'steps missing or incoherent; no sequence; no validation for risky operations'.

1 / 5

Progressive Disclosure

Content is organized into clearly labeled sections (Capabilities, Patterns, Anti-Patterns, Sharp Edges, Related Skills) with no bundle files to navigate; structure is good with minor gaps (thin stub sections), placing it at the 4 anchor rather than the fully-realized 5.

4 / 5

Total

9

/

20

Passed

Description

43%Weight 40%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 is persona-driven and buzzword-heavy, stating a clear niche (Trigger.dev background jobs for TypeScript) but offering only one concrete action and no explicit 'when to use' guidance. Second-person voice and over-claims further weaken specificity.

Suggestions

Rewrite in third person as concrete actions, e.g. 'Builds, schedules, and retries Trigger.dev background tasks and AI pipelines in TypeScript'.

Add an explicit trigger clause: 'Use when the user mentions Trigger.dev, background jobs, task queues, scheduled/cron jobs, or long-running TypeScript workflows'.

Drop marketing fluff like 'exceptional developer experience' and 'Temporal made easy' in favor of listed capabilities.

DimensionReasoningScore

Specificity

The description frames an identity ('You are a Trigger.dev expert') with one concrete action ('builds reliable background jobs') buried under marketing fluff ('exceptional developer experience', 'Temporal made easy'); reduced by 1 for second-person voice ('You are', 'You understand'), landing at the vague/near-no-concrete-actions anchor.

1 / 5

Completeness

A 'what' is weakly present (builds background jobs) but there is no 'Use when...' or equivalent trigger guidance; per the rubric a missing explicit 'when' clause caps completeness at 3, and it does not rise above that cap.

3 / 5

Trigger Term Quality

It surfaces relevant natural terms a user might say ('Trigger.dev', 'background jobs', 'TypeScript', 'orchestration') but misses common variations and synonyms, matching the 'some relevant keywords but missing variations' anchor rather than the 4 or 5 anchor.

3 / 5

Distinctiveness Conflict Risk

Naming the specific product (Trigger.dev) and its niche (background jobs/orchestration for TypeScript) gives it a mostly-distinct trigger profile with only minor overlap risk against general queue/cron skills, fitting the 4 anchor rather than the fully-distinct 5.

4 / 5

Total

11

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

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.