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

netlify-blobs

Store and retrieve unstructured objects, file uploads, and cache-like state on Netlify using the @netlify/blobs key/value API from Functions, Edge Functions, and Build Plugins. Use when a task involves saving user file or image uploads, persisting form or contact-form submissions, storing generated output from Background Functions (sitemaps/processed media/bulk-email results), building read-only asset stores, adding client-side blob expiration, or wiring file-based blob uploads at deploy time. Not for per-user, transactional, or relational data (counters/balances/sessions) — reach for Netlify DB there instead.

Quality

82%

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

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.

A dense, highly actionable reference with excellent executable examples and thorough gotchas, weakened by an appended house-rules block that duplicates inline guidance and by the absence of validation feedback loops around destructive operations.

Suggestions

Remove or de-duplicate the trailing 'Netlify house rules' section, since each rule already appears in the body (access control, deploy-context sharing, no counters, build-plugin read/write, error surfacing).

Add explicit validation checkpoints for destructive/batch operations — e.g., confirm keys before deleteAll, and a surface-error-and-check-logs retry loop for failed writes — to lift workflow clarity above the destructive-op cap.

Split the full 'API surface' reference into a one-level-deep reference file linked from the body to improve progressive disclosure and reduce inline bulk.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with no concept over-explanation, but the appended 'Netlify house rules' block restates guidance already in the body (access control, deploy-context sharing, no counters, build-plugin read/write, error surfacing), which is noticeable padding that could be trimmed.	3 / 5
Actionability	Fully executable, copy-paste-ready code covers the common cases — set/setJSON, null-checked get, atomic conditional writes, list/pagination, delete/deleteAll, build plugin, expiration, and ETag conditional reads — with concrete signatures and return shapes.	5 / 5
Workflow Clarity	Sections are logically ordered, but destructive/batch operations (deleteAll, destructive tests from previews) carry warnings without explicit validate-then-proceed checkpoints or fix-and-retry feedback loops, which caps this dimension at 3 per the rubric.	3 / 5
Progressive Disclosure	Well-organized into clear sections, but the file is monolithic with no bundle references (references/scripts/assets absent) and bulk API-reference plus duplicated house-rules content inlined rather than split into one-level-deep files.	3 / 5
	Total	14 / 20 Passed

Description

100%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, third-person description that concretely states capabilities, provides rich natural trigger phrases, and explicitly marks both when to use and when not to use the skill. No vague fluff or over-claims.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Store and retrieve unstructured objects, file uploads, and cache-like state', plus persisting submissions, storing generated output, building read-only asset stores, adding expiration, and wiring file-based uploads — giving comprehensive coverage of the skill's capabilities.	5 / 5
Completeness	Explicitly answers both 'what' (store/retrieve unstructured objects via @netlify/blobs) and 'when' (an explicit 'Use when a task involves...' clause listing concrete triggers), and adds a negative boundary ('Not for per-user, transactional, or relational data').	5 / 5
Trigger Term Quality	Comprehensive natural trigger phrases users would actually say — 'file or image uploads', 'form or contact-form submissions', 'sitemaps/processed media/bulk-email results', 'blob expiration', 'file-based blob uploads' — with synonyms and concrete variants throughout.	5 / 5
Distinctiveness Conflict Risk	Clear niche scoped to Netlify Blobs with distinct triggers and an explicit steer-away to Netlify DB for transactional data, minimizing conflict risk with adjacent skills.	5 / 5
	Total	20 / 20 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: 47848e2

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