CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

workflow

Vercel Workflow DevKit (WDK) expert guidance. Use when building durable workflows, long-running tasks, API routes or agents that need pause/resume, retries, step-based execution, or crash-safe orchestration with Vercel Workflow.

60

Quality

76%

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/vercel/skills/workflow/SKILL.md
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.

The body is highly actionable with executable code, exact commands, and valuable version-specific gotchas that Claude could not know. Its weaknesses are repetition in the Namespaced Streams section and an orphaned bundle reference file that the body never signals, leaving progressive disclosure underused.

Suggestions

Link the bundled reference from the DurableAgent section, e.g. 'See [durable-agent-patterns.md](references/durable-agent-patterns.md) for complete agent examples', so the existing bundle file is discoverable.

Collapse the Namespaced Streams section to one producer and one consumer example — the four near-identical logDebug/logInfo/emitAgentThought/emitAgentResult blocks repeat the same try/finally boilerplate.

Move the Testing Workflows details (Vitest configs, waitForHook/waitForSleep APIs) into a references file, keeping only a short summary and the pointer in SKILL.md.

Add a validation checkpoint to the doc-search workflow, e.g. verify node_modules/workflow/docs/ exists before advising an update to the latest Workflow DevKit.

DimensionReasoningScore

Conciseness

Most content is non-obvious, version-specific SDK knowledge (sandbox limitations, deterministic hook tokens, testing APIs) that earns its tokens, but the Namespaced Streams section repeats the identical getWriter/try/finally/releaseLock boilerplate four times and sandbox guidance is restated across two sections. This matches anchor 3 (mostly efficient but some unnecessary repetition could be tightened) rather than the lean anchor 5 or the noticeably padded anchor 2.

3 / 5

Actionability

Fully executable, copy-paste-ready TypeScript throughout, concrete CLI commands ('npx workflow health --port 3001', 'npx workflow inspect runs --backend vercel --project <name>'), and precise gotchas ('do not pass a token option to createWebhook()', 'start() cannot be called directly in workflow context') covering the common cases.

5 / 5

Workflow Clarity

An explicit startup sequence exists ('1. Find docs: glob node_modules/workflow/docs/**/*.mdx; 2. Search content: grep') with verification/debug commands (npx workflow health, --json, --help). Not anchor 5: the doc-search workflow lacks a validation checkpoint (e.g. confirm the package and docs exist before advising an update) and build/verify guidance is scattered across sections rather than sequenced with feedback loops.

4 / 5

Progressive Disclosure

Section headers are clear and the body points to bundled package docs, but the skill's own bundle file references/durable-agent-patterns.md is never linked or mentioned anywhere in the body, and large self-contained chunks (namespaced streams, testing) are fully inlined. This sits between anchors 2 and 3; the orphaned reference and inlined bulk fit anchor 3, though the completely unmentioned reference file pulls toward 2.

3 / 5

Total

15

/

20

Passed

Description

73%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 solid description with an explicit and detailed 'Use when' clause anchored to a distinct product niche. Its main weakness is the vague 'what' — 'expert guidance' instead of named concrete capabilities — which caps specificity and completeness.

Suggestions

Replace 'expert guidance' with concrete actions the skill performs, e.g. 'Build durable workflows with "use workflow"/"use step" directives, hooks, streaming, and testing for Vercel Workflow DevKit'.

Add natural trigger synonyms users would say but the description currently misses, such as 'background jobs', 'job queue', or 'event-driven orchestration'.

Clarify scope boundaries to prevent triggering on generic CI/GitHub-Actions 'workflow' requests, e.g. 'Use for Vercel Workflow (not CI workflows or GitHub Actions)'.

DimensionReasoningScore

Specificity

Names the domain (Vercel Workflow DevKit) and surfaces capabilities, but they appear as use-case nouns ('pause/resume, retries, step-based execution, crash-safe orchestration') rather than named actions, and the 'what' is the generic 'expert guidance'. This matches anchor 3 (domain plus 1-2 concrete actions, not comprehensive) better than anchor 4, which expects several explicitly stated actions.

3 / 5

Completeness

Both parts are present: a 'what' ('Vercel Workflow DevKit (WDK) expert guidance') and an explicit 'Use when...' clause with concrete trigger conditions. It falls short of anchor 5 only because the 'what' is vague ('expert guidance') rather than listing concrete capabilities, matching anchor 4.

4 / 5

Trigger Term Quality

Natural phrases users would actually say are well covered ('durable workflows', 'long-running tasks', 'pause/resume', 'retries', 'crash-safe orchestration'), but common synonyms like 'background jobs', 'job queue', 'event-driven', or 'checkpointing' are missing, matching anchor 4 rather than the comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

The description is pinned to a specific product ('Vercel Workflow DevKit (WDK)... with Vercel Workflow') with tool-specific triggers, giving a clear niche with minimal conflict risk despite the generic word 'workflow'.

5 / 5

Total

16

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

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

Warning

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

13

/

16

Passed

Repository

openai/plugins

Path

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