CtrlK
BlogDocsLog inGet started
Tessl Logo

deploy-release-test

Validate a commit-specific Next.js preview package and manually trigger the entire Next.js deployment test suite through the test_e2e_deploy_release.yml GitHub Actions workflow. Use only when asked to run the full deploy test suite or this workflow specifically from an internal vercel/next.js PR branch. Do not use for focused deployment-test sanity checks; run the relevant tests locally with pnpm test-deploy instead. Covers resolving the latest branch SHA, waiting for vercel-packages, preserving default workflow inputs, dispatching the workflow, and verifying the run.

75

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

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

An exemplary workflow skill: fully executable, tightly sequenced with validation checkpoints and error-recovery loops, and concise without assuming domain knowledge it shouldn't. Structure is clean and self-contained with one-level navigation only.

DimensionReasoningScore

Conciseness

Lean and command-driven throughout; the prose present is exclusively non-obvious gotchas (redirect-while-404 behavior, cross-repo restriction, branch race conditions) that Claude would not already know, with no padding of familiar concepts.

5 / 5

Actionability

Every step gives copy-paste-ready executable commands — `gh pr view`, `node scripts/wait-for-preview-tarball.mjs`, `gh workflow run`, `gh run list` — with explicit placeholders and flags covering the common cases.

5 / 5

Workflow Clarity

A 6-step sequenced workflow with explicit validation gates (validate tarball before dispatch, re-resolve PR after validation, verify run headSha) and clear feedback loops (timeout→abort, branch moved→return to step 2, headSha mismatch→stop).

5 / 5

Progressive Disclosure

Self-contained body with clear sections (Scope, Inputs, Workflow, Completion Report, Related Skills) and only one-level references (Related Skills pointers, one external contributing-doc link); no nested references and no bundle files to organize.

5 / 5

Total

20

/

20

Passed

Description

92%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 highly specific, well-scoped description that clearly states both capability and trigger conditions with strong negative guidance. Trigger-term coverage is good but tied to a narrow internal domain, leaving it just short of fully comprehensive natural phrasing.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Validate a commit-specific Next.js preview package', 'trigger the entire Next.js deployment test suite', and an explicit coverage list ('resolving the latest branch SHA, waiting for vercel-packages, preserving default workflow inputs, dispatching the workflow, and verifying the run') — giving comprehensive, not vague, coverage.

5 / 5

Completeness

Explicitly answers both what ('Validate...and manually trigger the entire Next.js deployment test suite through the test_e2e_deploy_release.yml GitHub Actions workflow') and when ('Use only when asked to run the full deploy test suite...from an internal vercel/next.js PR branch'), plus a concrete exclusion clause.

5 / 5

Trigger Term Quality

Includes natural phrases a user would say — 'run the full deploy test suite', 'this workflow specifically', 'pnpm test-deploy' — with synonyms ('deploy test suite'/'deployment test'), but a few natural variations and the workflow filename are the main hooks in a narrow niche.

4 / 5

Distinctiveness Conflict Risk

Pinned to a named workflow file, an internal vercel/next.js PR branch, and full-suite-only scope with an explicit 'Do not use for focused deployment-test sanity checks' boundary, giving a clear niche with minimal conflict risk.

5 / 5

Total

19

/

20

Passed

Validation

75%

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

Validation — 12 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

relative_links

Relative link issues: 1 suspicious

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

12

/

16

Passed

Repository
vercel/next.js
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.