project-tooling

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

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Risky

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./skills/project-tooling/SKILL.md

Quality

Content

65%

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

The content is highly actionable with executable examples, but it is a long monolithic reference dump that repeats itself and lacks validation checkpoints around destructive database operations.

Suggestions

Move the CI/CD workflow YAML and per-platform setup guides into reference files, keeping SKILL.md a concise overview with one-level-deep links.

Add explicit validation/feedback steps around destructive Supabase operations (e.g., verify migrations on a preview DB before 'db push' to production).

Create the referenced scripts/verify-tooling.sh as an actual bundle file instead of inlining the full script twice.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean command snippets, but at ~280 lines it is padded with repetition (Vercel link steps appear in two sections) and reference material that could be split out rather than kept inline.	2 / 3
Actionability	It provides concrete, copy-paste-ready bash, YAML, and JSON examples throughout (verify script, gh repo create, vercel deploy, supabase migrations, render.yaml, GitHub Actions workflows).	3 / 3
Workflow Clarity	Steps are listed and a verification script plus deployment checklist exist, but destructive operations like 'supabase db reset' and 'supabase db push' lack explicit validation feedback loops, capping workflow clarity at 2.	2 / 3
Progressive Disclosure	Content is well-sectioned but monolithic — CI/CD workflows and per-platform guides that should be separate files are inline, no bundle files exist, and the referenced 'scripts/verify-tooling.sh' is embedded rather than present as a real file.	2 / 3
	Total	9 / 12 Passed

Description

72%

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 distinctive and uses natural trigger terms, but it lists tool names rather than concrete actions and omits an explicit 'Use when' trigger in the description field itself.

Suggestions

Expand 'deployment platform setup' into concrete actions (e.g., 'create repos, deploy to Vercel/Render, run Supabase migrations, configure CI/CD').

Add an explicit 'Use when...' trigger clause inside the description field rather than relying only on when-to-use.

Dimension	Reasoning	Score
Specificity	Names the domain and concrete tool nouns ('gh, vercel, supabase, render CLI') but the only action is the vague 'setup', so it is not a comprehensive list of specific actions.	2 / 3
Completeness	It states what the skill covers ('CLI and deployment platform setup') but the description field itself lacks an explicit 'Use when...' trigger clause (that guidance lives in a separate when-to-use field), capping completeness at 2.	2 / 3
Trigger Term Quality	The platform names (gh, vercel, supabase, render) plus 'deployment platform' are exactly the natural terms a user would say when they need this skill.	3 / 3
Distinctiveness Conflict Risk	Naming four specific deployment platforms creates a clear niche with distinct triggers that is unlikely to fire for unrelated skills.	3 / 3
	Total	10 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	14 / 16 Passed

Repository: alinaqi/claude-bootstrap
Path: skills/project-tooling/SKILL.md
Commit: bb6195f

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