Name: upstash-ratelimit-ts
Rating: 56.8 (1 reviews)
Author: upstash

upstash-ratelimit-ts

Lightweight guidance for using the Redis Rate Limit TypeScript SDK, including setup steps, basic usage, and pointers to advanced algorithm, features, pricing, and traffic‑protection docs.

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./skills/SKILL.md

Quality

Content

70%

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

The content is concise and provides an executable quick-start example, but its workflow lacks validation checkpoints and every referenced sibling file is absent from the bundle, breaking progressive disclosure. Fixing the missing references and adding a verification step would raise the weaker dimensions.

Suggestions

Create or include the referenced sibling files (algorithms.md, pricing-cost.md, features.md, methods-getting-started.md, traffic-protection.md) so the navigation actually resolves.

Add a validation checkpoint to the Quick Start workflow, e.g. confirm the Redis connection succeeded and log/handle the throttled case beyond a bare comment.

If those sibling files are intentionally external, use real markdown links to their actual locations rather than listing filenames that do not exist in the bundle.

Dimension	Reasoning	Score
Conciseness	The body is lean and efficient: a short Quick Start list and one executable code example with no padding or explanation of concepts Claude already knows, so every token earns its place.	3 / 3
Actionability	The example is complete, executable, copy-paste ready TypeScript showing install-relevant imports, limiter creation, and the limit check, matching the 'fully executable code, copy-paste ready' anchor.	3 / 3
Workflow Clarity	The two Quick Start steps ('Install the SDK and connect to Redis', 'Create a rate limiter and apply it') give a sequence, but there is no validation or checkpoint for confirming the limit was applied or handling a failed connection, which caps workflow clarity at 2.	2 / 3
Progressive Disclosure	The 'Other Skill Files' section references algorithms.md, pricing-cost.md, features.md, methods-getting-started.md, and traffic-protection.md, but none of these files exist in the bundle, so navigation points to missing content and the structure is broken.	1 / 3
	Total	9 / 12 Passed

Description

57%

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 clearly scoped to a specific SDK and states concrete capabilities, but it lacks an explicit 'Use when...' trigger clause and omits common user phrasings like throttling or rate-limit error terms. These gaps cap completeness and trigger-term quality at 2.

Suggestions

Add an explicit trigger clause, e.g. 'Use when implementing request throttling, API rate limits, or handling 429 responses with Upstash Redis in TypeScript.'

Include natural user phrasings beyond the SDK name, such as 'throttling', 'API limits', 'too many requests', and '429'.

Replace the abstract 'pointers to advanced algorithm, features...' list with concrete actions to lift specificity toward the level-3 anchor.

Dimension	Reasoning	Score
Specificity	Names the SDK domain and a few concrete capabilities (setup steps, basic usage) but lists them abstractly rather than as multiple specific actions, stopping short of the 'lists multiple specific concrete actions' anchor.	2 / 3
Completeness	Clearly states what the skill does, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which the guidelines say caps completeness at 2.	2 / 3
Trigger Term Quality	Includes relevant natural terms ('Rate Limit TypeScript SDK', 'Redis', 'setup steps') but misses common variations a user would naturally say like 'throttling', 'API limits', 'too many requests', or '429'.	2 / 3
Distinctiveness Conflict Risk	It is scoped to a specific named SDK (Upstash Redis Rate Limit TypeScript SDK) with a distinct niche, making it unlikely to trigger for unrelated skills.	3 / 3
	Total	9 / 12 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: upstash/ratelimit-js
Path: skills/SKILL.md
Commit: 5b5448a

Reviewed: 1 day 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.