CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./skills/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%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 an exemplar of token-efficient skill writing: a minimal quick start, one complete executable example, and a clean index of advanced topics. Its two real defects are the missing install command in the quick start and the fact that all five referenced bundle files are absent from the skill directory, leaving the otherwise-excellent progressive disclosure structure unresolvable.

Suggestions

Ship the five referenced files (algorithms.md, pricing-cost.md, features.md, methods-getting-started.md, traffic-protection.md) in the bundle or correct their paths — currently every 'Other Skill Files' link is dangling.

Add the concrete install command to Quick Start (e.g. `npm install @upstash/ratelimit @upstash/redis`) so the first step is executable rather than descriptive.

Use markdown links for the file references (e.g. [algorithms.md](references/algorithms.md)) so the paths and their location in the bundle are unambiguous.

DimensionReasoningScore

Conciseness

The body is lean with zero padding: two terse quick-start bullets, one complete code example, and a five-line file index. No concepts Claude already knows are explained, and every token earns its place — a direct match for the anchor-5 example pattern of a heading plus a single code block.

5 / 5

Actionability

The TypeScript example is executable and copy-paste ready (constructing Redis, a slidingWindow limiter, and handling the denied case), covering the common case. The gap: "Install the SDK and connect to Redis" never gives the actual install command (e.g. `npm install @upstash/ratelimit @upstash/redis`), so the first instructed step cannot be executed as written — matching anchor 4's 'concrete code with minor gaps' rather than anchor 5.

4 / 5

Workflow Clarity

This is a simple, single-purpose skill and the single action is unambiguous: the quick-start bullets sequence install → connect → create limiter → apply, and the code demonstrates the full happy path plus the throttled branch. No destructive or batch operations are involved, so no validation checkpoints are required; the simple-skill exception applies.

5 / 5

Progressive Disclosure

The structure itself matches the anchor-5 pattern — a concise quick start plus a well-signaled, one-level-deep index of five topic files with one-line descriptions. However, scoring against the actual bundle: none of the referenced files (algorithms.md, pricing-cost.md, features.md, methods-getting-started.md, traffic-protection.md) exist in references/ or anywhere in the bundle, so every navigation pointer is broken and the disclosure structure cannot actually be used. This drops it to anchor 3's 'references present but not reliably usable' territory rather than anchor 4's 'minor organization gaps'.

3 / 5

Total

17

/

20

Passed

Description

53%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 clearly identifies its niche (Redis-based rate limiting in TypeScript) and honestly scopes the skill, but it is missing any 'when to use' trigger guidance and lacks the natural vocabulary (throttling, Upstash, 429) users would actually employ. It is serviceable but below the good-example bar, which pairs a concrete capability list with an explicit 'Use when...' clause.

Suggestions

Add an explicit trigger clause, e.g. "Use when implementing rate limiting or throttling in a TypeScript/Node.js project, especially with Upstash Redis, or when the user mentions 429s, API limits, or request quotas."

Replace topical labels with concrete actions: "Implement sliding-window, token-bucket, and fixed-window rate limits" instead of "pointers to advanced algorithm... docs".

Include the natural synonyms users say — "throttling", "rate limiting", "Upstash", "429", "too many requests" — to improve trigger matching.

DimensionReasoningScore

Specificity

Names the domain ("Redis Rate Limit TypeScript SDK") and enumerates coverage areas ("setup steps, basic usage, and pointers to advanced algorithm, features, pricing, and traffic-protection docs"), but the actions are topical labels rather than concrete verbs — it says what topics are covered, not what actions are performed. Anchor 4 requires several specific actions like "extracts text" or "fills forms"; this stays one notch below.

3 / 5

Completeness

The 'what' is clear (guidance for setup and basic usage of the SDK plus doc pointers), but there is no 'Use when...' clause or equivalent trigger guidance anywhere, capping completeness at 3 per the rubric guidelines. It is a solid clear-what/missing-when match, not the vague-what/no-when of anchor 2.

3 / 5

Trigger Term Quality

Relevant keywords are present ("Redis Rate Limit", "TypeScript", "setup", "pricing"), but the most natural user phrases are missing: "throttling", "Upstash", "429", "API limits", "too many requests". Terms like "traffic-protection" are doc titles, not phrases a user would naturally say, matching the anchor for relevant-but-missing-synonyms rather than the good-coverage anchor.

3 / 5

Distinctiveness Conflict Risk

"Redis Rate Limit TypeScript SDK" is a clear niche with minimal conflict risk against unrelated skills, but it omits the Upstash brand and could overlap with generic Redis or rate-limiting skills. Mostly distinct with minor overlap risk against closely related skills fits anchor 4; anchor 5 requires distinct triggers this description lacks.

4 / 5

Total

13

/

20

Passed

Validation

100%

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

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.