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.
68
81%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
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.
This is a strong description with excellent specificity, good trigger terms, and clear distinctiveness including an explicit anti-pattern to reduce skill conflicts. The main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill. The anti-pattern guidance is a notable strength that helps disambiguate from related Netlify skills.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user needs to store, retrieve, or manage files, images, or binary assets on Netlify, or mentions Netlify Blobs, blob storage, or asset uploads.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and concepts: getStore(), CRUD operations, metadata, listing, deploy-scoped vs site-scoped stores, and local development. Also specifies concrete use cases like images, documents, uploads, exports, cached binary artifacts. | 3 / 3 |
Completeness | Clearly answers 'what does this do' (guide for Netlify Blobs covering specific operations) but lacks an explicit 'Use when...' clause. The description implies when to use it through the listed asset types, but does not explicitly state trigger conditions. The anti-pattern guidance ('Do NOT use Blobs as a dynamic data store') partially compensates but doesn't replace a proper 'when' clause. | 2 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Netlify Blobs', 'file and asset storage', 'images', 'documents', 'uploads', 'exports', 'cached binary artifacts', 'getStore()', 'CRUD operations', 'deploy-scoped', 'site-scoped'. These cover a wide range of terms a developer working with Netlify would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — clearly scoped to Netlify Blobs specifically, with explicit differentiation from Netlify Database. The anti-pattern note ('Do NOT use Blobs as a dynamic data store — use Netlify Database for that') actively reduces conflict risk with a related skill. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
79%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, concise API reference skill that provides fully executable code examples and clear constraints. Its main weakness is the lack of workflow guidance for common multi-step patterns (upload → store → retrieve → verify) and missing error handling/validation steps. The progressive disclosure is adequate for a standalone file but could benefit from deeper references for advanced use cases.
Suggestions
Add a brief error handling pattern showing how to handle null returns from get() and common failure modes beyond the single 'common error' note.
Consider adding a short end-to-end workflow example (e.g., receiving a file upload in a function, storing it, and returning a reference) with validation checkpoints.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. The opening paragraph establishes scope and the anti-pattern (not for dynamic data) concisely. Every section delivers concrete information without explaining concepts Claude already knows. The 'Not for dynamic data' callout is valuable project-specific guidance, not filler. | 3 / 3 |
Actionability | All code examples are fully executable TypeScript with real imports, method calls, and return type annotations. The CRUD section covers every method with copy-paste ready examples including typed retrieval variants, metadata operations, and JSON helpers. The explicit note 'These are the only store methods. Do not invent others.' is a highly actionable constraint. | 3 / 3 |
Workflow Clarity | The skill is organized as an API reference rather than a multi-step workflow, which is appropriate for a CRUD storage API. However, there's no guidance on error handling, no validation steps (e.g., checking null returns after get), and no workflow for common patterns like 'upload an image from a function request.' For a storage API that could involve destructive deletes or overwrites, some validation guidance would strengthen this. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and a good reference to `netlify-database/SKILL.md` for the alternative. However, with no bundle files, there are no deeper references for advanced topics like deploy-scoped stores, streaming patterns, or error handling. The deploy-scoped store section is thin and could benefit from a linked reference. The content is borderline monolithic for a single file but stays manageable at its current length. | 2 / 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- netlify/context-and-tools
- Commit
cffaf74
- 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.