CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

workflow

Creates durable, resumable workflows using Vercel's Workflow SDK. Use when building workflows that need to survive restarts, pause for external events, retry on failure, or coordinate multi-step operations over time. Triggers on mentions of "workflow", "durable functions", "resumable", "workflow sdk", "queue", "event", "push", "subscribe", or step-based orchestration.

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./skills/workflow/upstream/SKILL.md

The canonical home for this skill is workflow in vercel/vercel-plugin

SKILL.md
Quality
Evals
Security

Quality

Content

71%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 highly actionable, well-organized reference packed with executable, SDK-specific guidance and validation tooling. Its weaknesses are verbosity from duplicated sections and an inlined API reference that should live in bundled reference files, plus the absence of a single unified build/validate/test sequence.

Suggestions

Move the World SDK method signatures, event-types table, and dashboard URL-format reference into a references/ file (e.g., references/world-sdk.md, references/cli.md) and keep only the key signatures and pointers in SKILL.md, cutting the file to well under half its current size.

Merge the "Error handling" and "Error handling patterns" sections into one, since both demonstrate FatalError/RetryableError with near-identical code.

Collapse the four near-identical namespaced-stream writer functions (logDebug/logInfo/emitAgentThought/emitAgentResult) into one parameterized helper example, stating the namespace naming convention in a sentence instead.

DimensionReasoningScore

Conciseness

The body is dense with SDK-specific, non-obvious knowledge and avoids explaining basics Claude already knows, but it includes clear padding: the FatalError/RetryableError guidance appears in two separate sections ("Error handling" and "Error handling patterns") with near-duplicate code, and the namespaced-streams example repeats the identical try/finally writer pattern across four functions (logDebug, logInfo, emitAgentThought, emitAgentResult). It could be tightened to a 4-5 by deduplicating these, but as written it matches "mostly efficient with some unnecessary content".

3 / 5

Actionability

Nearly every section gives copy-paste-ready, complete TypeScript or shell commands: directives, imports, step/workflow patterns, hook creation and resumption, serde class protocol, chunking/batching patterns, vitest integration config with waitForHook/waitForSleep, CLI commands with flags (--json, --url, --backend), and World SDK method signatures. The examples cover the common cases end to end.

5 / 5

Workflow Clarity

There is a clear docs-first procedure (numbered glob/grep steps against node_modules/workflow/docs/), explicit validation tooling for serde compliance (workflow transform --check-serde, workflow validate --json, build-time warnings), and testing guidance with a worked integration-test flow. It falls short of a 5 because there is no unified end-to-end sequence (write -> validate -> test) tying the sections together; validation checkpoints exist per-topic rather than as an explicit feedback loop.

4 / 5

Progressive Disclosure

The SKILL.md is an 845-line monolith with no bundled references/ directory, and roughly 150+ lines of it are API-reference material inlined inline (World SDK method signatures, the event-types table, streams methods, dashboard URL formats) that clearly belongs in a separate reference file — closely matching the anchor-3 example. Pointers to node_modules/**/docs/ are clearly signaled and only one level deep, which keeps it above a 2, but the skill bundle itself makes no use of progressive disclosure.

3 / 5

Total

15

/

20

Passed

Description

80%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 strong description that clearly states what the skill does and when to use it, with an explicit trigger list including good synonyms. Its main weakness is the inclusion of very generic trigger words ("queue", "event", "push", "subscribe") that create conflict risk with unrelated eventing/messaging tasks.

Suggestions

Drop or qualify the generic trigger terms "queue", "event", "push", and "subscribe" (e.g., "message queue backed by a workflow", "push events into a workflow") so the skill does not fire on ordinary pub/sub, notification, or event-handler requests.

Add a couple of natural phrasing variations users actually say, such as "long-running jobs", "background jobs", or "orchestrating steps", to improve trigger coverage without adding generic words.

DimensionReasoningScore

Specificity

"Creates durable, resumable workflows using Vercel's Workflow SDK" plus "survive restarts, pause for external events, retry on failure, or coordinate multi-step operations" names the domain and several specific capabilities. It falls short of a 5 because the capabilities are framed as use conditions rather than a comprehensive list of concrete actions.

4 / 5

Completeness

It explicitly answers both "what" ("Creates durable, resumable workflows using Vercel's Workflow SDK") and "when" ("Use when building workflows that need to survive restarts..." plus an explicit "Triggers on mentions of..." list with concrete trigger phrases), matching the top anchor.

5 / 5

Trigger Term Quality

The trigger list ("workflow", "durable functions", "resumable", "workflow sdk", "queue", "event", "push", "subscribe", "step-based orchestration") has good coverage including synonyms like "durable functions" and "resumable". A few natural phrases users would say are missing (e.g., "long-running", "background job", "orchestration" as a standalone word), so it is not a 5.

4 / 5

Distinctiveness Conflict Risk

The core niche (Vercel's Workflow SDK) is distinct, but the generic trigger terms "queue", "event", "push", and "subscribe" would fire on many unrelated requests (message queues, push notifications, pub/sub), creating real overlap risk with messaging- and event-handling skills. This is more than the "minor overlap" of a 4, but the SDK-specific framing keeps it above a 2.

3 / 5

Total

16

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (853 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository

vercel/vercel-plugin

Path

skills/workflow/upstream/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.