supabase-storage

Supabase Storage for file uploads, downloads, buckets, and signed URLs. Use when uploading files, managing storage buckets, generating signed URLs, or handling images.

Quality

81%

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

72%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 highly actionable, code-first reference whose snippets are copy-paste ready across all common Supabase Storage tasks. Its weaknesses are a broken reference link to a missing upload-patterns.md file, heavy inline detail that could be pushed to reference files, and no validation checkpoints around destructive/batch operations like file removal.

Suggestions

Fix the broken reference: either add references/upload-patterns.md or remove the link from the References section — a dangling link fails navigation when Claude tries to load it.

Add validation steps around destructive/batch operations, e.g. list files to confirm targets before remove(), and verify the RLS policy with a test query after creating it.

Move bulk inline detail (image transformation options, full RLS policy set, bucket-creation variants) into the existing references/storage-policies.md-style bundle files to slim the SKILL.md body toward a navigable overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean: terse comments and code-first sections with almost no explanation of concepts Claude already knows. Minor trimmable instances remain — the Quick Reference table duplicates method signatures that each later section repeats, and the per-task sections repeat the same call shape ('supabase.storage.from(...)') many times. Efficient with minor over-explanation fits the 4 anchor, not 5.	4 / 5
Actionability	Nearly every section contains copy-paste-ready executable code covering the common cases: uploads (basic, options, browser, base64), downloads, public/signed URLs, listing with search/sort, single and batch delete, move/copy, image transformations, RLS policies, and error handling. This matches the 5 anchor: fully executable guidance covering common cases.	5 / 5
Workflow Clarity	The content is organized as per-task recipes rather than sequenced workflows, and destructive/batch operations — 'remove([' for multiple files and SQL bucket/policy creation — have no validation or verification steps (no check-before-delete, no verify-policy step). Per the rubric cap for destructive/batch operations without validation, workflow clarity cannot exceed 3; the error-handling section shows recovery patterns but no validate-then-proceed checkpoints.	3 / 5
Progressive Disclosure	Section structure is clear and references are one level deep, but the References section links to 'references/upload-patterns.md' which does not exist in the bundle (only storage-policies.md is present) — a broken navigation link. Additionally, ~360 lines of inline API detail (all operation snippets, transformations, RLS policies) could partly live in the existing reference files. Good structure undermined by the dead link keeps this at 3 rather than 4.	3 / 5
	Total	15 / 20 Passed

Description

83%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 description that explicitly states both capability and trigger conditions in third person with concrete, natural trigger phrases. Its only weaknesses are slightly generic upload/image triggers and a few missing natural variations.

Dimension	Reasoning	Score
Specificity	Names the domain ('Supabase Storage') plus several concrete actions ('file uploads, downloads, buckets, and signed URLs'), with minor gaps in coverage (listing, moving, deleting files are absent). It lists several specific actions but is not comprehensive, matching the 4 anchor rather than 5.	4 / 5
Completeness	It clearly answers both 'what' ('Supabase Storage for file uploads, downloads, buckets, and signed URLs') and 'when' with an explicit 'Use when...' clause containing concrete trigger phrases ('uploading files, managing storage buckets, generating signed URLs, or handling images'). This matches the 5 anchor; a 4 would require the 'when' to be less explicit.	5 / 5
Trigger Term Quality	The trigger clause offers good natural keywords ('uploading files, managing storage buckets, generating signed URLs, or handling images') that users would plausibly say. A few natural terms are missing — e.g. 'downloading files', 'file storage', or mentioning 'Supabase' itself as a trigger — so it falls just short of the 5 anchor.	4 / 5
Distinctiveness Conflict Risk	'Supabase Storage' is a distinct niche with storage-specific triggers, but fairly generic phrases like 'uploading files' and 'handling images' could overlap with non-Supabase upload or image skills. Mostly distinct with minor overlap risk, matching the 4 anchor.	4 / 5
	Total	17 / 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-storage/SKILL.md
Commit: 93ed392

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