Name: upstash-ratelimit-ts
Rating: 60 (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

69%

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

76%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 SKILL.md body is lean and well-structured with executable code and clear pointers to sibling files, but the Quick Start workflow is underspecified and the referenced skill files are absent from the bundle.

Suggestions

Expand Quick Start into a short explicit sequence (install command, Redis connection, limiter creation, applying limiter, handling the success/throttled branch) with a checkpoint to verify the limit behaves as expected.

Add a one-line concrete handling pattern for the throttled branch (e.g., return a 429 response) rather than only a // throttled comment.

Ensure the referenced Other Skill Files (algorithms.md, pricing-cost.md, features.md, methods-getting-started.md, traffic-protection.md) are present in the bundle, or remove references to files that do not exist.

Dimension	Reasoning	Score
Conciseness	The body is lean and efficient — a brief Quick Start with executable code plus one-line pointers to other files — assuming Claude's competence with no padding or over-explanation.	5 / 5
Actionability	Provides copy-paste-ready TypeScript code covering the common rate-limit case, but offers no concrete handling pattern for the failure path beyond a // throttled comment and relies on external files for deeper detail.	4 / 5
Workflow Clarity	Quick Start gives only two high-level bullets ("install and connect", "create and apply") with a code example; sequence is implied but checkpoints and explicit validation are missing, fitting the anchor for 3.	3 / 5
Progressive Disclosure	Good structure with well-signaled one-level-deep references and concise per-file descriptions, but the referenced bundle files (algorithms.md, pricing-cost.md, features.md, methods-getting-started.md, traffic-protection.md) do not exist in the skill directory, a minor organization gap.	4 / 5
	Total	16 / 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 specific and well-targeted to a distinct niche, but it omits an explicit "Use when..." trigger clause, which caps completeness and limits trigger-term coverage.

Suggestions

Add an explicit "Use when..." clause naming natural triggers, e.g. "Use when the user needs rate limiting, throttling, or API request limits in a TypeScript project."

Include common synonyms users say ("throttle", "API limits", "request limits") to improve trigger-term coverage.

Tighten the action list slightly so it reads as concrete capabilities rather than a content inventory of linked docs.

Dimension	Reasoning	Score
Specificity	Names the SDK domain and several concrete actions ("setup steps, basic usage, and pointers to advanced...docs"), with only minor coverage gaps versus the comprehensive anchor.	4 / 5
Completeness	It states a clear "what" (setup, basic usage, pointers to advanced docs) but lacks any "Use when..." trigger clause, so per the guideline completeness is capped at 3.	3 / 5
Trigger Term Quality	Relevant keywords ("rate limit", "Redis", "TypeScript SDK") are present but common natural variations users say ("throttle", "API limits", "rate limiting", ".ts") are missing.	3 / 5
Distinctiveness Conflict Risk	Targets a clear niche (Upstash Redis Rate Limit TypeScript SDK) with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	15 / 20 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: 91c0bad

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