CtrlK
BlogDocsLog inGet started
Tessl Logo

workflows

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

64

Quality

75%

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

100%

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, well-organized reference with concrete executable commands, complete action and template-variable tables, and clear user-task mappings. It is token-efficient and highly actionable with no notable weaknesses.

DimensionReasoningScore

Conciseness

The body is lean and table-driven with no padding or explanation of concepts Claude already knows; every line (triggers, steps, template variables, firing lifecycle, common tasks) earns its place, matching the 'lean and efficient; every token earns its place' anchor.

3 / 3

Actionability

It provides a fully executable, copy-paste-ready command ('create-workflow --trigger before-event --steps ...'), complete action/step tables, and a concrete template-variable list, matching the 'fully executable code/commands; specific examples; copy-paste ready' anchor.

3 / 3

Workflow Clarity

Although it is a reference-style skill rather than a multi-step procedure, the single action (create/toggle a workflow) is unambiguous and illustrated by concrete user-request→command mappings; per the simple-skills note workflow clarity scores 3, and creating workflows is not a destructive/batch op requiring validation checkpoints.

3 / 3

Progressive Disclosure

The skill is under 50 lines, needs no external references (no bundle files present), and is organized into clearly labeled sections (Triggers, Steps, Template variables, Firing, Common tasks), so per the under-50-lines guideline progressive disclosure scores 3 with well-organized sections alone.

3 / 3

Total

12

/

12

Passed

Description

50%

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 clearly states the skill's domain and lists a few concrete capabilities, but it lacks explicit 'Use when...' trigger guidance and omits several actions documented in the body. It is a competent but incomplete description that would benefit from explicit trigger phrasing.

Suggestions

Add a 'Use when...' clause naming natural trigger phrases, e.g. 'Use when setting up booking reminders, follow-ups, or webhook notifications.'

Expand the action list to cover all capabilities in the body (e.g. include emails/SMS, not just reminders/follow-ups/webhooks).

Add user-natural variations like 'notifications', 'alerts', or 'automation' to broaden trigger term coverage.

DimensionReasoningScore

Specificity

The description names a domain ('Trigger-based automations') and three concrete action types ('reminders, follow-ups, webhooks'), but the actions are terse and not comprehensive (emails/SMS from the body are omitted), matching the 'names domain and some actions, but not comprehensive' anchor rather than the full multi-action anchor.

2 / 3

Completeness

It answers 'what' (trigger-based automations across the booking lifecycle) but provides no 'Use when...' clause or explicit trigger guidance, so per the judging guidelines completeness is capped at 2.

2 / 3

Trigger Term Quality

'reminders, follow-ups, webhooks' are natural terms a user would say, but coverage is limited and misses common variations like 'notifications', 'alerts', or 'automation', fitting the 'some relevant keywords but missing common variations' anchor.

2 / 3

Distinctiveness Conflict Risk

'across the booking lifecycle' scopes it to a niche, but without explicit triggers and with the somewhat generic 'trigger-based automations' framing it could still overlap with a general notifications/automation skill, matching the 'somewhat specific but could still overlap' anchor.

2 / 3

Total

8

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

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.