CtrlK
BlogDocsLog inGet started
Tessl Logo

automations

Event-triggered and schedule-triggered automations with natural-language conditions. Use when creating automations, wiring events, or understanding how triggers fire.

64

Quality

77%

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 ./.agents/skills/automations/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

80%

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

The body is a lean, highly actionable reference with concrete formats, code, and tool actions that assume Claude's intelligence. It is held back only by monolithic inline structure (no split reference files) and implicit rather than explicit validation feedback loops for risky dispatch operations.

Suggestions

Split the larger reference blocks (full Frontmatter Fields table, Event Bus API, Condition Evaluator internals) into separate referenced files so SKILL.md stays an overview with one-level-deep links.

Add an explicit validation/error-recovery feedback loop for dispatch (e.g., on lastStatus=error, inspect lastError, adjust condition/body, re-fire with action=fire-test) rather than only recording status.

DimensionReasoningScore

Conciseness

Dense, table-driven reference that assumes Claude's competence (no basics about cron, event buses, or HTTP) and avoids padding; every section earns its tokens.

3 / 3

Actionability

Provides a copy-paste markdown frontmatter format, concrete tool actions with parameters, executable TypeScript event-bus code, and a fully specified define example with exact field values.

3 / 3

Workflow Clarity

The "How It Works" 7-step sequence and the Example agent flow are clear, and delete carries an explicit confirmation checkpoint, but validation/error-recovery feedback loops for dispatch and risky batch operations are only implicit (status written back to frontmatter) rather than explicit validate->fix->retry steps.

2 / 3

Progressive Disclosure

No bundle files exist and the ~190-line body is well-sectioned, but it is monolithic: the full frontmatter field table, event-bus API, and condition-evaluator internals are inline content that could be split into one-level-deep reference files rather than carried entirely in SKILL.md.

2 / 3

Total

10

/

12

Passed

Description

75%

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 third-person, concise, and clearly pairs a what-statement with an explicit "Use when" trigger clause, satisfying completeness and distinctiveness. It is slightly held back on specificity and trigger-term breadth, which name capabilities but stop short of a rich list of concrete actions and natural phrasings.

Suggestions

Add a few more concrete verbs/actions (e.g., "create, update, delete, and test automations") to lift specificity toward a score-3 list of actions.

Broaden the trigger terms with natural phrasings users actually say (e.g., "set up an automation", "when an event fires", "cron-triggered task").

DimensionReasoningScore

Specificity

Names the domain and several specific mechanisms ("event-triggered and schedule-triggered automations", "natural-language conditions") but uses capability noun phrases rather than a list of distinct concrete actions like the score-3 anchor.

2 / 3

Completeness

Explicitly states both what it does (event/schedule automations with natural-language conditions) and when to use it via a clear "Use when..." clause.

3 / 3

Trigger Term Quality

Includes natural user-facing phrases ("creating automations, wiring events, or understanding how triggers fire") but offers limited coverage of common phrasings a user might actually say.

2 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (event/schedule-triggered automations) with explicit triggers unlikely to collide with sibling skills like recurring-jobs or secrets.

3 / 3

Total

10

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository
BuilderIO/agent-native
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.