runtime-cache

Vercel Runtime Cache API guidance — ephemeral per-region key-value cache with tag-based invalidation. Shared across Functions, Routing Middleware, and Builds. Use when implementing caching strategies beyond framework-level caching.

Quality

70%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/vercel/skills/runtime-cache/SKILL.md

Quality

Content

65%Weight 40%Scale 1-3

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

The body is highly actionable with executable API and CLI examples and good decision guidance, but loses points on a time-sensitive Observability paragraph, missing validation steps for destructive cache operations, and no progressive disclosure via bundle files.

Suggestions

Move the 'March 5, 2026' CDN dashboard detail and marketing language out of the main Observability section or into a clearly marked changelog/deprecated area so time-sensitive content does not burden the core reference.

Add an explicit validation step to destructive operations (e.g., verify the tag exists or confirm --yes scope before 'vercel cache dangerously-delete') to introduce a feedback/checkpoint loop.

Split the CLI Cache Commands and Next.js Integration sections into one-level-deep reference files (e.g., CLI.md, NEXTJS.md) linked from the overview to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean API reference with executable examples and no padding of concepts Claude already knows, but the Observability section injects time-sensitive detail ('March 5, 2026') and marketing-style language not placed in a deprecated/old-patterns section, which the rubric penalizes.	2 / 3
Actionability	It provides copy-paste-ready, executable code for getCache set/get/delete/expireTag, invalidateByTag, Next.js integration, and concrete CLI commands with flags, fully matching the strong anchor.	3 / 3
Workflow Clarity	Content is organized by topic with useful 'When to Use'/'When NOT to Use' guidance, but there is no explicit sequenced workflow, and destructive operations like dangerouslyDeleteByTag and vercel cache purge lack validation/verification checkpoints, capping the score at 2.	2 / 3
Progressive Disclosure	Sections are well organized and external references are clearly signaled in a References section, but no bundle files exist and sizable content (CLI commands, Next.js integration) is inline rather than split into one-level-deep reference files.	2 / 3
	Total	9 / 12 Passed

Description

75%Weight 40%Scale 1-3

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 clearly states what the skill covers and when to use it, with a distinctive Vercel-scoped niche. It is somewhat weaker on concrete action framing and natural trigger-term breadth, leaning technical over colloquial.

Dimension	Reasoning	Score
Specificity	It names the domain ('Vercel Runtime Cache API guidance', 'ephemeral per-region key-value cache with tag-based invalidation') and where it applies ('Shared across Functions, Routing Middleware, and Builds'), but frames the skill as 'guidance' rather than listing multiple concrete actions, so it is not fully comprehensive.	2 / 3
Completeness	It explicitly answers both what ('ephemeral per-region key-value cache with tag-based invalidation') and when ('Use when implementing caching strategies beyond framework-level caching'), matching the strong anchor.	3 / 3
Trigger Term Quality	Relevant keywords are present ('caching strategies', 'framework-level caching', 'tag-based invalidation'), but the trigger phrasing is fairly technical and misses common variations a user might say like 'Vercel cache', 'cache invalidation', or 'runtime cache'.	2 / 3
Distinctiveness Conflict Risk	The 'Vercel Runtime Cache API' niche is specific and the trigger is scoped to Vercel caching beyond framework-level caching, making it unlikely to fire for unrelated skills.	3 / 3
	Total	10 / 12 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
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning

	Total	14 / 16 Passed

Repository: openai/plugins
Path: plugins/vercel/skills/runtime-cache/SKILL.md
Commit: 11c74d6

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