Name: netlify-blobs
Rating: 72 (1 reviews)
Author: netlify

netlify-blobs

Guide for using Netlify Blobs for file and asset storage — images, documents, uploads, exports, cached binary artifacts. Covers getStore(), CRUD operations, metadata, listing, deploy-scoped vs site-scoped stores, and local development. Do NOT use Blobs as a dynamic data store — use Netlify Database for that.

Quality

87%

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

92%

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

A lean, highly actionable reference with strong error-recovery guidance, held back only by its monolithic single-file structure where some API reference content could be progressively offloaded.

Suggestions

Move the full CRUD/list/consistency API reference and the limits table into a references/ file (e.g., API.md), keeping SKILL.md as an overview with one-level-deep links, to better satisfy progressive disclosure.

Remove the duplicate strong-consistency getStore example (it appears both in 'Getting a Store' and 'Consistency and concurrency') to tighten the token budget.

If splitting is undesired, add a brief table of contents at the top so the long single-file reference is navigable at a glance.

Dimension	Reasoning	Score
Conciseness	The body is dense and high-signal — API specifics, gotchas, and a limits table — and assumes Claude's competence without explaining what object storage is; not a 2 because nearly every token earns its place, though the strong-consistency getStore example is repeated across sections.	3 / 3
Actionability	All examples are executable TypeScript and concrete CLI commands (netlify blobs:list/get/set/delete) plus exact build-time paths like .netlify/blobs/deploy/; not a 2 because the guidance is copy-paste ready with no pseudocode gaps.	3 / 3
Workflow Clarity	Decision guidance ("Before you build") sequences access-pattern choices, and "When a store operation fails" provides an explicit feedback loop — read the function logs first, check common causes, then report and stop; not a 2 because validation/error checkpoints are present rather than missing.	3 / 3
Progressive Disclosure	Well-organized with clear section headers and only one-level-deep sibling-skill references (netlify-database/SKILL.md), but the full API reference, limits, CLI, and build-time material all live inline in a single ~167-line file rather than being split into reference files; not a 3 because content that could be separate is inline, and not a 1 because references are shallow and clearly signaled with no nested indirection.	2 / 3
	Total	11 / 12 Passed

Description

82%

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 specific, well-scoped description with good trigger terms and clear distinctiveness, weakened only by the absence of an explicit positive 'Use when...' clause.

Suggestions

Add an explicit 'Use when ...' trigger clause (e.g., 'Use when storing or serving files and assets on Netlify — uploads, exports, generated images, or cached binaries') so the 'when to use' is stated positively, not just implied.

Lead with the trigger guidance before the method list so a user scanning skill descriptions sees the use-case first.

Consider mirroring natural phrasings users say ('store uploaded files', 'serve images', 'cache build artifacts') to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities — "getStore(), CRUD operations, metadata, listing, deploy-scoped vs site-scoped stores, and local development" — matching the anchor for multiple specific concrete actions; not a 2 because the coverage is comprehensive rather than partial.	3 / 3
Completeness	The "what" is strong, but there is no explicit "Use when..." trigger clause — only negative guidance ("Do NOT use Blobs as a dynamic data store"), so per the guideline a missing positive trigger caps completeness at 2; not a 3 because "when to use it" is only implied, and not a 1 because the capabilities are clearly stated.	2 / 3
Trigger Term Quality	Natural user-facing terms are well covered — "file and asset storage", "images, documents, uploads, exports", "cached binary artifacts" — which a user would plausibly say when reaching for blob storage; not a 2 because common variations are present rather than missing.	3 / 3
Distinctiveness Conflict Risk	Targets a clearly named, distinct product (Netlify Blobs) and explicitly differentiates it from Netlify Database, giving it a clear niche unlikely to trigger the wrong skill; not a 2 because the negative boundary removes the main overlap risk.	3 / 3
	Total	11 / 12 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: netlify/context-and-tools
Path: codex/skills/netlify-blobs/SKILL.md
Commit: b4ac277

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