automations

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

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/automations/SKILL.md

Quality

Content

75%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.

This is a well-structured, mostly lean reference that pairs executable examples with clear field and action tables and a concrete worked flow. It scores high across all dimensions, held just below 5 by implicit validation checkpoints, a minor field-name inconsistency in the example, and the absence of explicit deeper-reference files.

Suggestions

Add an explicit validation checkpoint to the create/update workflow (e.g., 'After define, list the automation and confirm lastStatus/triggerType before declaring success') to lift workflow_clarity toward 5.

Reconcile the example's 'trigger_type' with the frontmatter table's 'triggerType' so the actionable example is copy-paste accurate.

Consider moving the Event Bus API and Built-in Events tables into a short references file and signaling it from the body to strengthen progressive disclosure now that no bundle files exist.

Dimension	Reasoning	Score
Conciseness	The body is dense and mostly assumes Claude's competence, using tables and terse field specs rather than padded prose, with only minor over-explanation (e.g., the 'How It Works' lifecycle narration) that could be trimmed.	4 / 5
Actionability	It gives concrete tool actions, a complete frontmatter table, an executable event-bus code example, and a worked define flow, with only minor gaps such as the example using 'trigger_type' while the field table lists 'triggerType'.	4 / 5
Workflow Clarity	The 'How It Works' steps sequence acquisition through execution clearly and the example traces a concrete agent flow, but validation checkpoints are implicit rather than explicit (e.g., no confirm/verify step after define) and destructive ops like delete only note 'always confirm with user first'.	4 / 5
Progressive Disclosure	Content is well-sectioned with a Key Files table pointing one level into the codebase and Related Skills links for navigation; no bundle files exist so the overview stands alone, with only minor gaps in signaling deeper references.	4 / 5
	Total	16 / 20 Passed

Description

66%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 cleanly answers both what the skill does and when to use it in third person with concrete trigger phrases, landing above average on completeness and trigger quality. It is slightly under-specified on the concrete actions it enumerates, keeping specificity at the midpoint.

Suggestions

Add one or two concrete verbs (e.g., 'create, update, and inspect automations') to lift specificity toward 4-5.

Include a natural synonym such as 'cron schedules' or 'recurring jobs' in the description to broaden trigger-term coverage and reduce overlap ambiguity with the recurring-jobs skill.

Dimension	Reasoning	Score
Specificity	Names the domain ('Event-triggered and schedule-triggered automations') and one concrete capability ('natural-language conditions'), but does not enumerate the specific actions (create, wire events, inspect triggers) at the level the anchor for 4 expects.	3 / 5
Completeness	It states both what it does (event/schedule-triggered automations with NL conditions) and when to use it ('Use when creating automations, wiring events, or understanding how triggers fire'), with the 'when' slightly less explicit than the anchor for 5.	4 / 5
Trigger Term Quality	Natural phrases users would say ('creating automations', 'wiring events', 'how triggers fire') are present with good coverage, though common synonyms like 'schedules', 'cron jobs', or 'recurring jobs' are not surfaced in the description itself.	4 / 5
Distinctiveness Conflict Risk	The trigger phrasing around automations, events, and triggers is fairly distinct from sibling skills, with only minor overlap risk with the related 'recurring-jobs' skill which the body (not the description) disambiguates.	4 / 5
	Total	15 / 20 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
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
Path: .agents/skills/automations/SKILL.md
Commit: cc2a915

Reviewed: ~5 hours ago

Table of Contents

Discovery Implementation Validation

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.