CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

65

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

87%

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

The content is highly actionable and token-efficient with well-organized, self-contained sections, but workflow clarity is held back by the absence of validation/verification checkpoints around destructive and batch operations.

Suggestions

Add an explicit validation or verification step around store.delete() and batch/list operations (e.g., confirm key existence via getMetadata before deleting).

Surface a short end-to-end sequence tying 'Before you build' decisions to a concrete getStore → set → serve flow with a checkpoint.

Optionally note how to verify a blob was written correctly (e.g., re-read with getWithMetadata) after set operations.

DimensionReasoningScore

Conciseness

The body is lean and skill-specific — it avoids explaining concepts Claude already knows and every section (CRUD, limits, local dev) earns its place with concrete guidance.

3 / 3

Actionability

Provides complete, copy-paste-ready TypeScript for getStore, set/setJSON, typed get variants, getWithMetadata, list with prefix, and delete, plus concrete package names and a limits table.

3 / 3

Workflow Clarity

A decision sequence exists in 'Before you build' and operations are grouped logically, but there are no explicit validation checkpoints, and destructive operations like store.delete() lack verification guidance, capping clarity at 2.

2 / 3

Progressive Disclosure

The skill is a single self-contained file with clearly organized sections (Before you build, Getting a Store, CRUD, Store Types, Limits, Local Development) and easy navigation; no external references are needed for content of this scope.

3 / 3

Total

11

/

12

Passed

Description

67%

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 specific and well-scoped to a distinct Netlify niche, but it omits an explicit 'Use when...' trigger clause and only partially covers natural user phrasing, capping completeness and trigger quality at 2.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers, e.g. 'Use when storing user uploads, generated images, exports, or cached binaries on Netlify.'

Broaden trigger terms with common variations users might say, such as 'object storage', 'blob storage', or 'file uploads'.

Move the dynamic-data disambiguation into the 'when' framing so the positive use case is as clear as the negative one.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities — 'getStore(), CRUD operations, metadata, listing, deploy-scoped vs site-scoped stores, and local development' — matching the anchor for enumerating specific actions.

3 / 3

Completeness

Clearly states what the skill covers, but lacks an explicit positive 'when to use' trigger clause; only a negative 'Do NOT use Blobs as a dynamic data store' is given, so per the guidelines completeness is capped at 2.

2 / 3

Trigger Term Quality

Natural terms like 'file and asset storage', 'images, documents, uploads, exports' are present, but coverage is incomplete and there is no explicit 'Use when...' enumeration of common variations (e.g., object/blob storage).

2 / 3

Distinctiveness Conflict Risk

The Netlify-Blobs niche is distinct, and the explicit redirect to 'Netlify Database' for dynamic data disambiguates it from the related database skill, making wrongful triggering unlikely.

3 / 3

Total

10

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
netlify/context-and-tools
Reviewed

Table of Contents

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.