bootstrap

Project bootstrapping orchestrator for repos that depend on Vercel-linked resources (databases, auth, and managed integrations). Use when setting up or repairing a repository so linking, environment provisioning, env pulls, and first-run db/dev commands happen in the correct safe order.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/vercel/skills/bootstrap/SKILL.md

Quality

Content

77%

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

The skill body is highly actionable and well-sequenced with strong validation checkpoints, but it is somewhat long and monolithic for a single SKILL.md, with some rule repetition and several inline branches that would benefit from being split into one-level-deep reference files.

Suggestions

Extract the per-resource setup details (Postgres paths, AUTH_SECRET generation, Next.js UI baseline, next-forge guide) into separate reference files and link to them, keeping SKILL.md as a lean overview that preserves the strict ordering.

De-duplicate the env-template discovery logic: the Preflight step 4 and the Env Verification block both search .env.example/.env.sample/.env.template; consolidate into one place to trim tokens.

Remove the trailing '=> skill: next-forge' line's dangling pointer since no next-forge skill is bundled here, or convert it into a proper one-level reference link.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with command-first structure, but repeats the gating rule across the Rules, Preflight, and App Setup sections and the env-verification template search is restated after the Preflight already covered template discovery, adding tokens Claude doesn't need.	2 / 3
Actionability	Provides fully executable, copy-paste-ready commands at every step (vercel link, integration add, env pull, the comm-based env diff, AUTH_SECRET generation), with concrete fallback paths and a package-manager-aware App Setup section.	3 / 3
Workflow Clarity	Strictly ordered bootstrap with explicit gating ("Proceed only when missing key list is empty"), a dedicated Bootstrap Verification checklist with failure remediation ("stop and report exact failing step"), and feedback loops for re-pulling env and re-running failed db steps.	3 / 3
Progressive Disclosure	No bundle files exist in references/scripts/assets, yet the body is one long monolithic file (~160 lines) covering Postgres, auth, Next.js UI, next-forge, and summaries inline rather than splitting detailed branches into reference files, so structure could be better separated.	2 / 3
	Total	10 / 12 Passed

Description

80%

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

The description is specific, third-person, and clearly answers both what and when with an explicit trigger clause. It is strong overall, with the main weakness being slightly jargon-heavy trigger language that omits a few natural user phrasings.

Suggestions

Add a couple of plain-language trigger phrases (e.g. "connect a database to Vercel," "set up environment variables") alongside the Vercel-specific terms so it matches how users actually ask.

Dimension	Reasoning	Score
Specificity	Names concrete actions — "linking, environment provisioning, env pulls, and first-run db/dev commands" — and specifies they must happen "in the correct safe order," matching the multiple-specific-actions anchor.	3 / 3
Completeness	Explicitly answers what (orchestrates linking, provisioning, env pulls, db/dev commands) and when ("Use when setting up or repairing a repository so..."), satisfying the explicit-trigger requirement.	3 / 3
Trigger Term Quality	Includes plausible trigger phrases like "setting up or repairing a repository," "linking," and "env pulls," but is somewhat jargon-heavy ("Vercel-linked resources," "managed integrations") and omits common variations users might say like "connect database" or "set up env vars."	2 / 3
Distinctiveness Conflict Risk	Scoped to Vercel-linked repos with a specific bootstrap ordering niche; the "Use when" clause ties it to repo setup/repair, making it unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning

	Total	14 / 16 Passed

Repository: openai/plugins
Path: plugins/vercel/skills/bootstrap/SKILL.md
Commit: 11c74d6

Reviewed: about 9 hours ago

Table of Contents

Discovery Implementation Validation

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.