supabase-node

Express/Hono with Supabase and Drizzle ORM

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

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 body is highly actionable with complete, executable code and a logical layout, but it is a monolithic ~830-line template that inlines boilerplate and full route/schema files rather than progressively disclosing them via bundled references, and lacks validation checkpoints in its build flow.

Suggestions

Move stable reference material (schema definitions, full route handlers, query functions) into files under references/ and link to them one level deep, keeping SKILL.md as a concise overview.

Trim boilerplate Claude already knows (Express/cors/helmet setup, generic error and validation middleware) to only the Supabase/Drizzle-specific parts.

Add explicit validation checkpoints to the setup flow, e.g. run `npm run db:generate` and confirm a migration file appears, then verify auth with a test request before proceeding.

Dimension	Reasoning	Score
Conciseness	The ~830-line body avoids conceptual prose padding, but it inlines substantial boilerplate Claude already knows (Express app setup, centralized error handler, Zod validate middleware, cors/helmet wiring) and is far longer than a lean skill needs to be.	2 / 3
Actionability	It provides fully executable, copy-paste-ready TypeScript with real imports and real Supabase/Drizzle APIs, plus concrete install commands, env vars, and package.json scripts.	3 / 3
Workflow Clarity	Sections imply a sensible order (structure -> setup -> config -> DB -> client -> middleware -> routes -> app -> testing), but there are no explicit validation checkpoints for the database migration or auth flows, which the rubric caps at 2 for DB operations.	2 / 3
Progressive Disclosure	No bundle files exist (references/, scripts/, assets/ absent) and the entire project template is inlined in SKILL.md; section organization is clear, but hundreds of lines of code that belong in separate reference files are inline, fitting the 'content that should be separate is inline' anchor.	2 / 3
	Total	9 / 12 Passed

Description

57%

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 names a specific, distinctive stack but reads as a label rather than a capability statement, lacking concrete actions and an inline 'when to use' trigger. It is distinguishable but incomplete as a self-contained discovery string.

Suggestions

Add concrete verbs/actions, e.g. 'Build Node.js backends with Express or Hono, Supabase Auth/Storage, and Drizzle ORM for typed database queries.'

Append an explicit 'Use when...' trigger to the description itself (e.g. 'Use when building a Node.js/TypeScript API with Supabase and Drizzle') rather than relying solely on the when-to-use field.

Include common user terms like 'Node.js', 'backend', 'API', and 'REST' to improve trigger coverage.

Dimension	Reasoning	Score
Specificity	The description 'Express/Hono with Supabase and Drizzle ORM' names a concrete, specific technology stack but contains no verbs or concrete actions (e.g. build, configure, query), matching the 'names domain and some actions' anchor only on the domain axis.	2 / 3
Completeness	The description field answers 'what' (the stack) but contains no 'Use when...' trigger clause; explicit trigger guidance exists only in the separate when-to-use frontmatter field, so per the rubric the missing trigger in the description caps completeness at 2.	2 / 3
Trigger Term Quality	It includes solid natural keywords (Express, Hono, Supabase, Drizzle ORM) but misses common variations a user would say such as 'Node.js', 'backend', 'API', or 'REST', fitting the 'some relevant keywords but missing common variations' anchor.	2 / 3
Distinctiveness Conflict Risk	The Supabase + Drizzle + Express/Hono combination is a clear, specific niche with distinct triggers that is unlikely to fire for unrelated skills.	3 / 3
	Total	9 / 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
skill_md_line_count	SKILL.md is long (837 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: alinaqi/claude-bootstrap
Commit: 9dacc46

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