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

88%

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

Quality

Content

88%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 tightly structured, highly actionable bootstrap workflow with explicit ordering, validation checkpoints, and error-recovery guidance. The only meaningful gap is minor redundancy and a sizable inline variant section that could be split into a referenced file.

Suggestions

Consolidate the gating rules currently restated across the Rules, App Setup, and Bootstrap Verification sections into one canonical " Preconditions" checkpoint to remove redundancy.

Move the next-forge variant block into a separate references file and link to it one level deep, mirroring the existing `=> skill: next-forge` pointer, to keep the core flow scannable.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence (no explanation of what Vercel or env files are), with minor redundancy between the gating Rules, the App Setup guard, and the Bootstrap Verification checklist that could be tightened.	4 / 5
Actionability	Copy-paste-ready, executable commands cover the common cases throughout (vercel link, vercel env pull, vercel integration add, the node:crypto AUTH_SECRET generation, the comm env-diff, npm run db:push).	5 / 5
Workflow Clarity	Strict ordered phases (Preflight → Resource Setup → AUTH_SECRET → Env Verification → App Setup → Verification) with explicit gating ("Proceed only when missing key list is empty") and a feedback loop ("If verification fails, stop and report exact failing step plus remediation") satisfy the destructive/db-operation validation requirement.	5 / 5
Progressive Disclosure	Well-organized into clearly signaled sections with a one-level-deep pointer ("=> skill: next-forge — Full next-forge monorepo guide"); the inline next-forge variant block is large enough that it could arguably live in its own reference, keeping this just short of ideal.	4 / 5
	Total	18 / 20 Passed

Description

87%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, specific description that clearly states both purpose and trigger conditions with concrete, domain-appropriate terminology. Minor specificity gaps (AUTH_SECRET, integration add) keep it just short of perfect on action coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ("repos that depend on Vercel-linked resources (databases, auth, and managed integrations)") and several concrete actions ("linking, environment provisioning, env pulls, and first-run db/dev commands"), but a few subordinate actions (e.g. AUTH_SECRET generation, integration add) are not surfaced, so it sits just below comprehensive.	4 / 5
Completeness	Explicitly answers both what ("Project bootstrapping orchestrator for repos that depend on Vercel-linked resources...") and when ("Use when setting up or repairing a repository so ... happen in the correct safe order") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural trigger phrasing ("Use when setting up or repairing a repository") plus concrete terms ("linking", "env pulls", "db/dev commands", "bootstrap") give good coverage, though a few common synonyms are absent.	4 / 5
Distinctiveness Conflict Risk	The Vercel-linked-resources niche with distinct triggers (vercel link, env pull, integration provisioning) is clearly scoped and unlikely to fire for unrelated skills.	5 / 5
	Total	18 / 20 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: 1e28582

Reviewed: 7 days 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.