trigger-getting-started

trigger-getting-started is a Background jobs & messaging skill for AI agents, published by code-with-antonio in the browser-automation-app repository on GitHub. Skillspace rates trigger-getting-started F (45/100) and the safety scan rated it risky; the rating is based on static analysis only.

Bootstrap Trigger.dev into an existing project from scratch: authenticate the CLI, install @trigger.dev/sdk and @trigger.dev/build, write trigger.config.ts with the project ref and task dirs, scaffold a /trigger directory with a first task, wire tsconfig and .gitignore, set TRIGGER_SECRET_KEY, and run the dev server. Load this when a project has no trigger.config.ts yet and the user asks to "add Trigger.dev", "set up Trigger.dev", "initialize Trigger.dev", or get a first task running, including in a monorepo. Once the project is set up and you are writing task code, switch to the trigger-authoring-tasks skill.

Grade
F
Quality
45 / 100
Safety
Risky
GitHub stars
55

Unproven: rated by static analysis only, not yet compared head-to-head.

Our two independent classifiers differ on this skill's category, so treat the placement as provisional.

This rating describes the version of the repository we crawled; it may have changed since.

Our review

Architecture
84 / 100
Maturity
Basic: a single SKILL.md
Security scan
High-risk patterns
License
Not declared. Check the repository before reusing it.
Adoption
Adopted by 2 other repositories, in 0 collections

What the scanner flagged

  • references sensitive credential env

Not checked yet

  • Not judged on the rubric yet (not a contender in its category)
  • No blind task eval yet
  • Scope (portable / vendor / repo-internal) not assessed; only the top of each category is read for scope
  • Sibling files (scripts, references) not fetched; security scan covers SKILL.md only

Skillspace indexes and rates this skill; it does not host or endorse it. Run third-party skills at your own risk.