supabase-functions

Supabase Edge Functions development and deployment using Deno runtime. Use when creating serverless functions, webhooks, API endpoints, or scheduled tasks.

Quality

67%

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 ./skills/supabase-functions/SKILL.md

Quality

Content

65%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.

The skill body is highly actionable with complete, executable examples and commands, but it is verbose with duplicated boilerplate, lacks an explicit build→test→deploy workflow with validation checkpoints, and ships a broken reference link (deno-imports.md).

Suggestions

Add a short sequenced workflow with a validation checkpoint before deploy, e.g. create → serve locally → test with curl → verify response → deploy, to satisfy the destructive-operation validation requirement.

Consolidate the repeated corsHeaders / import / Deno.serve boilerplate into a single 'Basic structure' example and reference it (or the _shared pattern) from later examples instead of repeating full blocks.

Either create references/deno-imports.md or remove its link from the References section, and move the bulk of the repeated pattern code into references/function-patterns.md to reduce the inline footprint.

Dimension	Reasoning	Score
Conciseness	The body is mostly executable code without basic-concept padding, but it is long (~400 lines) with redundant blocks: the corsHeaders object and the import/Deno.serve boilerplate are repeated across several examples and could be consolidated.	3 / 5
Actionability	Provides copy-paste-ready CLI commands and complete executable TypeScript examples covering the common cases (CORS, Supabase client, JWT user extraction, Stripe webhook, cron, shared code) plus a config.toml and limits table.	5 / 5
Workflow Clarity	Content is organized by task but presented as a reference catalog rather than a sequenced workflow, and the outward-facing deploy step has no validation checkpoint (e.g. test locally / verify endpoint after deploy); the rubric caps destructive operations without validation at 3.	3 / 5
Progressive Disclosure	A References section signals one-level-deep links, but references/deno-imports.md is referenced yet missing from the bundle, and a large amount of pattern code is inlined rather than moved into the existing reference files.	3 / 5
	Total	14 / 20 Passed

Description

70%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.

The description is well-formed with an explicit 'Use when' clause, third-person voice, and a clear niche. Its main weakness is that the 'what' is stated generically ('development and deployment') rather than as concrete actions, keeping specificity and completeness just below the top anchors.

Suggestions

Replace the generic 'development and deployment' with concrete actions, e.g. 'Create, test, and deploy serverless Deno functions, handle CORS, manage secrets, and configure webhooks and cron schedules.'

Add the natural term 'Edge Functions' and the file extension '.ts' to the trigger phrase list for better keyword coverage.

Consider tightening the 'what' to mirror the body's actual capabilities (e.g. mention secrets and config.toml) so the description previews the skill's scope.

Dimension	Reasoning	Score
Specificity	Names the domain (Edge Functions, Deno runtime) and lists concrete function types (webhooks, API endpoints, scheduled tasks), but the stated actions ('development and deployment') are generic rather than specific concrete operations.	3 / 5
Completeness	Explicitly answers both 'what' ('Supabase Edge Functions development and deployment using Deno runtime') and 'when' ('Use when creating serverless functions, webhooks, API endpoints, or scheduled tasks'), though the 'what' could be more specific.	4 / 5
Trigger Term Quality	Includes natural trigger phrases users would say ('serverless functions, webhooks, API endpoints, or scheduled tasks') via an explicit 'Use when' clause, though it misses some synonyms like 'Edge Functions' and file extensions.	4 / 5
Distinctiveness Conflict Risk	The 'Supabase Edge Functions' + 'Deno runtime' niche is clearly distinct with Supabase-specific triggers, with only minor overlap risk against general Deno or serverless skills.	4 / 5
	Total	15 / 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
relative_links	Relative link issues: 1 missing	Warning
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	14 / 16 Passed

Repository: fernandezbaptiste/Skrillz
Path: skills/supabase-functions/SKILL.md
Commit: 93ed392

Reviewed: 1 day 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.