CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/runtime-cache/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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 strong, dense API reference with executable code, explicit API-vs-API decision guidance, and concrete limits. The only real weaknesses are a dated, off-topic Observability digression and a monolithic structure where secondary Next.js/CLI/CDN material could move to reference files.

DimensionReasoningScore

Conciseness

Nearly every section delivers product-specific facts Claude cannot know (limits table, 300ms tag propagation, tag rules, ISR isolation), with code kept tight. The Observability section digresses into dated CDN-dashboard changelog detail ('March 5, 2026', 'project-level routing') unrelated to the Runtime Cache, which is exactly the kind of trimmable, time-sensitive content that keeps this below anchor 5.

4 / 5

Actionability

Fully executable, copy-paste-ready TypeScript and CLI commands covering the common cases: cache-aside fetch handler, tag expiration from a Server Action, CLI purge/invalidate/dangerously-delete with flags, plus a limits table and a deprecated-API warning. This matches the anchor for complete, executable guidance covering common cases.

5 / 5

Workflow Clarity

As an API-reference skill it has no stepwise workflow, but decision guidance is explicit: the 'Important distinction' callouts (cache.expireTag vs invalidateByTag), the Runtime Cache vs ISR isolation rules, and When to Use / When NOT to Use sections act as clear checkpoints, and the destructive command carries a stampede-risk warning. It falls short of anchor 5 only because there is no validation step after invalidation (e.g. verifying a tag expired).

4 / 5

Progressive Disclosure

A single-file skill with clear section headers, easy navigation, and an external-links References section; no bundle files exist to reference. It stays at anchor 4 rather than 5 because ~90 lines of secondary material (Next.js Integration, CLI Commands, CDN Cache Tags) is inlined in SKILL.md instead of being split into one-level-deep reference files.

4 / 5

Total

17

/

20

Passed

Description

70%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 solid, third-person description with an explicit use clause and a well-delineated niche. Its main weakness is that it describes what the Runtime Cache is rather than what the skill concretely helps do, and the trigger guidance is phrased abstractly instead of with concrete trigger phrases.

Suggestions

Rewrite the opening as concrete actions the skill performs, e.g. 'Implement per-region key-value caching with the Vercel Runtime Cache API: set/get/delete keys with TTLs and tags, expire tags, and purge CDN/Runtime/Data caches.'

Make the 'Use when' clause concrete with trigger phrases users actually say, e.g. 'Use when the user mentions runtime cache, caching API responses, tag invalidation, expireTag, or caching beyond what Next.js/framework caching provides.'

Add one or two natural synonyms (e.g. 'cache API responses', 'cross-function data sharing') to broaden trigger-term coverage without adding length.

DimensionReasoningScore

Specificity

The description names the domain concretely ('ephemeral per-region key-value cache with tag-based invalidation') but characterizes the cache rather than listing actions the skill performs; only 'guidance' and 'implementing caching strategies' are action-shaped. This matches the anchor for domain plus 1-2 concrete actions without comprehensive coverage, and falls short of anchor 4 because no specific skill actions (e.g. set/get keys, expire tags) are enumerated.

3 / 5

Completeness

Has both a clear 'what' (Runtime Cache API guidance, per-region key-value cache with tag invalidation) and an explicit 'Use when...' clause. The 'when' is abstract ('implementing caching strategies beyond framework-level caching') rather than concrete trigger phrases, so it does not reach anchor 5; it is clearly above anchor 3 because the use condition is explicit, not merely implied.

4 / 5

Trigger Term Quality

Includes natural terms users would say — 'caching', 'cache', 'tag-based invalidation', 'Runtime Cache' — giving good keyword coverage. Not anchor 5 because common user phrasings like 'cache API responses', 'invalidate cache', or '@vercel/functions' are absent.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (Vercel Runtime Cache) and explicitly contrasts with 'framework-level caching', minimizing confusion with Next.js cache skills. Minor overlap risk remains with closely related skills such as Vercel Storage or CDN caching, fitting anchor 4 rather than anchor 5.

4 / 5

Total

15

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

13

/

16

Passed

Repository

vercel/vercel-plugin

Path

skills/runtime-cache/SKILL.md

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.