CtrlK
BlogDocsLog inGet started
Tessl Logo

tessl-fe/rapid-deploy

Use for deployments, shipping, releasing, pushing to production, hotfixes, rollbacks, and any task related to getting code live

94

1.32x
Quality

97%

Does it follow best practices?

Impact

86%

1.32x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

Overview
Quality
Evals
Security
Files

Quality

Content

92%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A strong, actionable skill with executable commands, a well-sequenced pre-merge validation checklist, and an efficient troubleshooting table. Content is concise and project-specific throughout. The only weakness is that all content lives in a single file with no use of progressive disclosure via external references.

Suggestions

Consider extracting the troubleshooting table and detailed pre-merge checklist into separate reference files (e.g., references/troubleshooting.md) to improve progressive disclosure and keep the main skill lean.

DimensionReasoningScore

Conciseness

Lean and efficient. No explanation of what Vercel is or how deployments work. Every section provides project-specific facts Claude wouldn't know: specific env var names (NEXT_PUBLIC_BACKEND_URL), expected build times (60-90s), and the exact git diff command for debug artifact detection.

3 / 3

Actionability

Fully executable commands throughout: 'npm run build', 'vercel ls tessl-fe/frontend-app --prod', 'vercel rollback <previous-deployment-url>', and a specific git diff command for console.log detection. The troubleshooting table maps exact error messages to concrete fixes.

3 / 3

Workflow Clarity

The pre-merge checklist provides a clear 5-step validation sequence before the destructive merge-to-main. Includes conditional handling ('If a key is missing, add it in Vercel and re-deploy the preview before merging'). The rollback section provides an explicit recovery path for post-deploy failures. The troubleshooting table adds structured error recovery.

3 / 3

Progressive Disclosure

Well-organized with clear section headers (Pre-Merge Checklist, Deploy, Rollback, Common Build Failures), but all content is inline in a single ~80-line file with no external references. The detailed checklist and troubleshooting table could be split into separate files for better progressive disclosure.

2 / 3

Total

11

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

An excellent description that clearly names the platform (Vercel), project (Forge's frontend-app), and lists specific capabilities with explicit 'Use when' triggers. Third-person voice is used correctly throughout. Natural trigger terms cover the key deployment scenarios a user would mention.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: 'running vercel deploy commands, configuring environment variables, monitoring build status, and reverting to previous deployments.' Each names a distinct, concrete capability.

3 / 3

Completeness

Clearly answers both what ('Manages Vercel deployment workflows... including running vercel deploy commands, configuring environment variables...') and when ('Use when shipping to production, handling hotfixes, performing rollbacks, reviewing preview deployments, diagnosing failed Vercel builds').

3 / 3

Trigger Term Quality

Strong coverage of natural terms users would say: 'shipping to production', 'hotfixes', 'rollbacks', 'preview deployments', 'failed Vercel builds', 'Vercel'. These match how developers naturally describe deployment tasks.

3 / 3

Distinctiveness Conflict Risk

Highly specific to Vercel deployments for a named project (Forge's frontend-app). The combination of platform (Vercel), project name, and deployment-specific triggers makes conflict with other skills very unlikely.

3 / 3

Total

12

/

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.

Reviewed

Table of Contents