project-tooling

gh, vercel, supabase, render CLI and deployment platform setup

Quality

32%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Risky

Do not use without reviewing

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/project-tooling/SKILL.md

Quality

Discovery

22%

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

This description is a bare-bones list of tool names with a vague action ('setup'). It lacks concrete actions, explicit trigger guidance ('Use when...'), and sufficient detail for Claude to confidently select this skill over others. The mention of specific platform names is its only distinguishing feature.

Suggestions

Add a 'Use when...' clause specifying triggers, e.g., 'Use when the user needs to authenticate, configure, or deploy using gh, Vercel, Supabase, or Render CLI tools.'

List specific concrete actions the skill covers, e.g., 'Authenticates CLI tools, configures project settings, deploys applications, links repositories, provisions databases, and manages environment variables.'

Include common user-facing synonyms and variations like 'deploy', 'hosting', 'GitHub CLI', 'cloud deployment', 'production setup' to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	The description only names tools/platforms ('gh, vercel, supabase, render CLI') and uses vague language ('setup'). It does not list concrete actions like 'deploy applications', 'configure environment variables', 'link repositories', or 'provision databases'.	1 / 3
Completeness	The description weakly addresses 'what' (setup of CLI and deployment platforms) but completely lacks any 'when' clause or explicit trigger guidance. There is no 'Use when...' or equivalent.	1 / 3
Trigger Term Quality	It includes some natural keywords users might say ('gh', 'vercel', 'supabase', 'render', 'CLI', 'deployment'), but misses common variations like 'deploy', 'hosting', 'GitHub CLI', 'serverless', 'database setup', 'cloud platform', or 'production deployment'.	2 / 3
Distinctiveness Conflict Risk	Naming four specific platforms (gh, vercel, supabase, render) provides some distinctiveness, but 'deployment platform setup' is broad enough to overlap with general DevOps or infrastructure skills. The lack of specificity about what kind of setup increases conflict risk.	2 / 3
	Total	6 / 12 Passed

Implementation

42%

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

The skill provides highly actionable, executable commands and configurations for multiple deployment platforms, which is its primary strength. However, it is severely over-long for a SKILL.md, inlining content that should be in separate referenced files (CI/CD configs, validation scripts, platform-specific guides). It also explains many patterns Claude already knows and lacks validation checkpoints after critical deployment operations.

Suggestions

Split platform-specific sections (Vercel, Supabase, Render, GitHub Actions) into separate referenced files (e.g., VERCEL.md, SUPABASE.md, RENDER.md, CI-CD.md) and keep SKILL.md as a concise overview with links.

Move the validation bash script to an actual file reference (scripts/verify-tooling.sh) rather than inlining the entire script in the skill body.

Remove explanations of basic CLI patterns Claude already knows (e.g., how to run `gh auth login`, what `vercel whoami` does) and focus on project-specific conventions and decisions.

Add explicit validation/verification steps after deployment operations (e.g., 'After `vercel --prod`, verify deployment: `vercel inspect <url>`' or 'After `supabase db push`, verify: `supabase db remote commit`').

Dimension	Reasoning	Score
Conciseness	The skill is extremely verbose at ~350+ lines. It explains basic CLI patterns Claude already knows (how to run `gh auth login`, `vercel login`, etc.), includes a lengthy bash validation script that could be referenced as a file, and repeats deployment connection steps in multiple formats (CLI, dashboard, todos). The Render section alone has 5 sub-steps for what is essentially 'connect repo and set API key'. Much of this is reference documentation Claude could derive from tool help.	1 / 3
Actionability	The skill provides fully executable, copy-paste ready commands throughout — bash scripts, YAML CI/CD configs, curl commands, package.json snippets, and render.yaml templates. All commands are concrete with specific flags and arguments.	3 / 3
Workflow Clarity	Steps are listed for various workflows (GitHub setup, Vercel deployment, Supabase migrations, Render setup) and there's a deployment checklist. However, there are no explicit validation checkpoints after destructive operations like `supabase db push` or `vercel --prod`. The validation script only checks tool installation, not deployment success. Missing feedback loops for deployment verification.	2 / 3
Progressive Disclosure	This is a monolithic wall of text with no references to external files despite being well over 300 lines. The validation script, CI/CD templates, render.yaml, and platform-specific setup guides should be split into separate referenced files. Everything is inlined, making the skill consume excessive context window space.	1 / 3
	Total	7 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: alinaqi/claude-bootstrap
Commit: 65efb33

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.