CtrlK
BlogDocsLog inGet started
Tessl Logo

workflow-automation

You are a workflow automation architect who has seen both the promise and the pain of these platforms. You've migrated teams from brittle cron jobs to durable execution and watched their on-call burden drop by 80%.

22

Quality

11%

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 ./plugins/antigravity-bundle-automation-builder/skills/workflow-automation/SKILL.md

The canonical home for this skill is workflow-automation in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

11%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 skill is essentially a skeleton with section headers but almost no substantive content. It names patterns, anti-patterns, and sharp edges without providing any actual implementation guidance, code examples, or concrete steps. For a workflow automation skill, the complete absence of executable code, platform-specific examples, or sequenced workflows makes it nearly unusable.

Suggestions

Add concrete, executable code examples for each pattern (Sequential, Parallel, Orchestrator-Worker) using at least one platform (e.g., Temporal, Inngest, or DBOS) with copy-paste ready implementations.

Fix the sharp edges table by replacing placeholder 'Issue' text with actual issue descriptions and providing real code snippets showing both the wrong approach and the correct approach for each edge case.

Add a decision framework or comparison table with concrete criteria (e.g., team size, throughput needs, infrastructure constraints) to help choose between platforms like n8n, Temporal, Inngest, and DBOS.

Flesh out anti-patterns with specific examples showing what the bad pattern looks like and how to refactor it, including validation/verification steps for destructive or batch workflow operations.

DimensionReasoningScore

Conciseness

The skill repeats the description as a preamble, includes a capabilities list that reads like tags rather than actionable content, and the sharp edges table has placeholder 'Issue' text with code comments as solutions that are never shown. The pattern and anti-pattern sections are just names with no substance, wasting tokens on structure without content.

2 / 5

Actionability

There is no executable code, no concrete commands, no specific examples, and no actual implementation guidance. The patterns section names patterns but provides no code or steps. The sharp edges table references code comments (e.g., '# ALWAYS use idempotency keys') but never shows the actual code. Everything is vague description with zero concrete guidance.

1 / 5

Workflow Clarity

Despite being a skill about workflow automation, there are no sequenced steps, no validation checkpoints, and no actual workflow instructions. The patterns section names Sequential, Parallel, and Orchestrator-Worker patterns but provides only one-line descriptions with no steps or implementation details.

1 / 5

Progressive Disclosure

There are no bundle files and no references to external documents. The content has some section headers providing minimal structure, but the sharp edges table is broken (placeholder 'Issue' text), and there's no navigation to deeper content. The 'Related Skills' section mentions other skills but provides no links or paths.

2 / 5

Total

6

/

20

Passed

Description

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

This description is written as a persona/backstory rather than a functional skill description. It fails to state what the skill does, when it should be used, or provide any concrete trigger terms. It also uses second-person framing ('You are') which is inappropriate for a skill description that should use third-person voice.

Suggestions

Replace the persona narrative with concrete actions the skill performs, e.g., 'Designs and implements workflow automations using durable execution frameworks. Migrates cron jobs to orchestration platforms.'

Add an explicit 'Use when...' clause with natural trigger phrases, e.g., 'Use when the user asks about workflow automation, replacing cron jobs, setting up durable execution, or orchestrating tasks.'

Include specific platform names, file types, or technologies to improve trigger term quality and distinctiveness, e.g., 'Temporal, Inngest, Step Functions, Airflow, DAGs.'

DimensionReasoningScore

Specificity

The description contains no concrete actions whatsoever. It uses vague, narrative language about 'migrating teams' and 'durable execution' but never states what the skill actually does (e.g., 'creates workflows', 'configures automation pipelines'). It reads as a persona backstory, not a capability description.

1 / 5

Completeness

Neither 'what does this do' nor 'when should Claude use it' is answered. There is no 'Use when...' clause or equivalent trigger guidance, and the 'what' is entirely absent—replaced by a persona description and an anecdote about on-call burden.

1 / 5

Trigger Term Quality

A few domain-relevant terms appear ('workflow automation', 'cron jobs', 'durable execution') but they are buried in narrative prose rather than presented as trigger keywords. Common user phrases like 'automate', 'pipeline', 'scheduling', 'orchestration', or specific platform names are absent.

2 / 5

Distinctiveness Conflict Risk

The term 'workflow automation architect' is broad and could overlap with many skills (CI/CD, DevOps, task scheduling, orchestration). Without specifying concrete capabilities or platforms, it would be difficult to distinguish this from other automation-related skills.

2 / 5

Total

6

/

20

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.