vercel-kv
Integrate Redis-compatible Vercel KV for caching, session management, and rate limiting in Next.js. Powered by Upstash with strong consistency and TTL support. Use when implementing cache strategies, rate limiters, or troubleshooting environment variables, serialization errors, rate limit issues, scanIterator hangs, or Next.js cache stale reads.
Overall
score
87%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
100%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 skill description that clearly defines its scope around Vercel KV/Redis integration with Next.js. It excels at providing specific capabilities, natural trigger terms, and explicit usage guidance. The troubleshooting scenarios add valuable specificity that helps distinguish it from generic caching skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'caching, session management, and rate limiting' with technical details like 'strong consistency and TTL support'. Also mentions specific troubleshooting scenarios. | 3 / 3 |
Completeness | Clearly answers both what (integrate Redis-compatible Vercel KV for caching, session management, rate limiting) AND when (explicit 'Use when' clause covering implementation and troubleshooting scenarios). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'Redis', 'Vercel KV', 'caching', 'session management', 'rate limiting', 'Next.js', 'Upstash', 'environment variables', 'serialization errors', 'TTL', 'scanIterator', 'cache stale reads'. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche combining Vercel KV, Upstash, Redis, and Next.js. The combination of these technologies plus specific error types (scanIterator hangs, serialization errors) makes it highly distinctive and unlikely to conflict. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality, actionable skill with excellent code examples and comprehensive coverage of known issues and edge cases. The main weakness is length - the 15 documented issues section, while valuable, makes the file quite long and could benefit from progressive disclosure to a separate troubleshooting reference. The content is well-structured and provides genuine value beyond what Claude would know by default.
Suggestions
Extract the Known Issues section (Issues #1-15) into a separate TROUBLESHOOTING.md file, keeping only the 3-4 most critical issues inline with links to the full reference
Consider moving Version Migration Guide and Known Limitations to separate reference files, keeping only brief summaries in the main skill
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some verbose explanations in the Known Issues section that could be condensed. The 'Why It Happens' explanations are helpful but add length; the core patterns and quick start sections are appropriately lean. | 2 / 3 |
Actionability | Excellent executable code examples throughout - all patterns include copy-paste ready TypeScript with proper imports, error handling, and real-world usage. Workarounds for known issues include complete, runnable code snippets. | 3 / 3 |
Workflow Clarity | Clear workflows with explicit validation steps, especially in the Critical Rules section with do/don't lists. The Known Issues section provides clear error → cause → prevention sequences. Version migration guide has explicit before/after code comparisons. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but the Known Issues section is quite long (15 issues inline) and could benefit from being split into a separate reference file. The skill is over 300 lines which pushes the boundary of what should be in a single file. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 12 / 16 Passed | |
- 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.