CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

workflows

Trigger-based automations — reminders, follow-ups, webhooks — across the booking lifecycle.

Quality

80%

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 ./packages/scheduling/docs/skills/workflows/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A well-structured, token-efficient reference that documents the domain model thoroughly and gives concrete CLI examples for common requests. Its weaknesses are incompleteness in the examples (truncated step JSON, missing toggle-workflow syntax) and the absence of verification steps for creating and especially disabling workflows.

Suggestions

Complete the truncated example, e.g. 'create-workflow --trigger new-booking --steps '[{action: sms-host, offsetMinutes: 0}]'', so all common-task rows are copy-paste ready.

Add the 'toggle-workflow' command syntax and show how to find the workflow ID (e.g. a 'list-workflows' command or where IDs appear in API responses).

Add a verification checkpoint after creating or disabling a workflow (e.g. re-fetch the workflow and confirm its enabled state), especially since 'stop all reminders' is a batch operation.

DimensionReasoningScore

Conciseness

Lean and efficient throughout: every line delivers API facts (trigger names, step actions, template variables) via compact tables with no padding or explanations of concepts Claude already knows. The 'Firing' section is borderline internals but stays to two sentences.

5 / 5

Actionability

Mostly executable guidance — the common-tasks table gives concrete 'create-workflow' commands with real flags and JSON. However, the 'Text me when someone books' example is truncated with '...', and the 'toggle-workflow' row gives no command syntax or ID argument, so it is not fully copy-paste ready.

4 / 5

Workflow Clarity

The mapping from user requests to commands is clear, but there are validation gaps: no step to verify a workflow was created/enabled, no guidance on how to find the workflow ID that 'toggle-workflow' needs, and disabling ('Stop all reminders') is a batch operation with no verification checkpoint.

3 / 5

Progressive Disclosure

A single, well-organized ~50-line file with clean sections (Triggers, Steps, Template variables, Firing, Common tasks) and no external references — appropriate for a skill of this scope, matching the simple-skill exception.

5 / 5

Total

17

/

20

Passed

Description

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

A concise, specific description that clearly communicates the skill's niche, but it lacks any 'when to use' trigger guidance, which is its most significant gap. Adding an explicit 'Use when...' clause with natural user phrasings would raise both completeness and trigger-term quality.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to set up reminders, notifications, follow-ups, or automated emails/SMS/webhooks around bookings.'

Include common user synonyms such as 'notifications', 'automations', or 'email/SMS reminders' to broaden natural trigger-term coverage.

State the operative verbs (e.g. 'Create and manage trigger-based automations...') so the capability list reads as actions rather than nouns.

DimensionReasoningScore

Specificity

Names the domain ('booking lifecycle') and three concrete capability types ('reminders, follow-ups, webhooks'), but omits the verbs (create, manage, configure) that would make the actions fully comprehensive.

4 / 5

Completeness

The 'what' is clear (trigger-based automations for reminders, follow-ups, webhooks across bookings), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3.

3 / 5

Trigger Term Quality

Contains good natural keywords a user would say ('reminders', 'follow-ups', 'webhooks', 'booking'), but misses common variations like 'notifications', 'automations', or 'email/SMS reminders'.

4 / 5

Distinctiveness Conflict Risk

'across the booking lifecycle' pins a clear niche, and the trigger/action vocabulary (reminders, webhooks, bookings) is distinct enough to avoid firing for unrelated skills.

5 / 5

Total

16

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

BuilderIO/agent-native

Path

packages/scheduling/docs/skills/workflows/SKILL.md

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.