Name: upstash-redis
Rating: 56.8 (1 reviews)
Author: membranedev

upstash-redis

Upstash Redis integration. Manage data, records, and automate workflows. Use when the user wants to interact with Upstash Redis data.

Quality

65%

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 ./skills/upstash-redis/SKILL.md

Quality

Content

67%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.

The body is a strong, actionable integration guide with concrete commands and a well-checked connection workflow. Its weaknesses are minor filler, slightly disjointed section numbering, and the absence of any progressive-disclosure split despite a moderately long single file.

Suggestions

Remove filler lines like 'When to use which actions: Use action names and parameters as needed.' and trim the introductory 'Upstash Redis is a serverless...' paragraph to tighten token efficiency.

Fix the step numbering so 'skip to Step 2' resolves to a clearly labeled Step 2 section, removing the '1b' ambiguity in the connection flow.

Consider extracting the proxy request flag table and the detailed clientAction state handling into a separate reference file linked from SKILL.md to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly command-dense and practical, but includes filler such as 'When to use which actions: Use action names and parameters as needed.' and introductory context about what Upstash Redis is, matching the 'mostly efficient but includes some unnecessary explanation' anchor rather than the lean level above.	3 / 5
Actionability	It provides concrete, mostly copy-paste-ready commands across the full flow (install, login, connection ensure, action list/run, request proxy) with flags and a parameter table, but relies on unsubstituted placeholders like CONNECTION_ID and repeats the action-list command, leaving minor gaps below the fully-ready level.	4 / 5
Workflow Clarity	The connection flow is clearly sequenced with explicit checkpoints (poll until READY, handle CLIENT_ACTION_REQUIRED, check CONFIGURATION_ERROR/SETUP_FAILED), but the 'skip to Step 2' reference is slightly confusing given the '1b' numbering and the structure is somewhat disjointed, so it stays just below the explicit-feedback-loop anchor.	4 / 5
Progressive Disclosure	The content is well organized into clear sections (install, auth, connect, search, run, proxy, best practices) with no nested or buried references and no bundle files present, but everything is inlined in one ~140-line file rather than split, so it does not reach the cleanly-split one-level-deep reference level.	4 / 5
	Total	15 / 20 Passed

Description

62%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.

The description is competent: it identifies a distinct niche and includes an explicit 'Use when' trigger covering both what and when. Its main weakness is generic, non-specific action verbs that under-sell the concrete Redis capabilities.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Redis operations, e.g. 'Read and write keys, run pipelines, manage TTLs, and automate workflows on Upstash Redis.'

Add natural trigger synonyms and file/URL cues users would actually say, such as caching, sessions, rate limiting, or upstash.com links, to broaden trigger-term coverage.

Tighten the 'when' clause to be more specific, e.g. 'Use when the user wants to cache data, manage sessions, or read/write keys in Upstash Redis.'

Dimension	Reasoning	Score
Specificity	The description names the Upstash Redis domain and lists a few actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete Redis-specific operations, so it matches the '1-2 concrete actions, not comprehensive' anchor rather than the comprehensive level above.	3 / 5
Completeness	It states both the 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Upstash Redis data'), and since the 'Use when' clause is present it is not capped at 3, though the 'when' could be more specific so it does not reach 5.	4 / 5
Trigger Term Quality	It surfaces the product name 'Upstash Redis' as the primary natural trigger and includes a 'Use when' clause, but it lacks synonyms or variations users might say (e.g. caching, sessions, keys, .upstash), matching the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The 'Upstash Redis' niche and trigger are clearly distinct from most other skills, but the generic action phrasing ('manage data, records, automate workflows') leaves minor overlap risk with broad data-management skills, placing it just below the minimal-conflict anchor.	4 / 5
	Total	14 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/upstash-redis/SKILL.md
Commit: f484c82

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