Content
22%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is a skeleton: section headers and a sharp-edges table gesture at real content, but every substantive section is a stub — no code, no commands, no sequenced workflows, and visibly corrupted/truncated text. A model loading this skill would learn almost nothing actionable about actually using QStash.
Suggestions
Replace the one-line Pattern stubs with executable examples — e.g. a curl call to https://qstash.upstash.io/v2/publish/{endpoint}, JSON body, and the signature-verification code for an endpoint (JWT with both current and next signing keys).
Complete the truncated "core philosophy" list, fill in the empty Anti-Pattern sections with what to do instead, and turn the Sharp Edges "Solution" column entries into actual code/snippets instead of comment labels.
Add a sequenced workflow with validation for critical flows (e.g. publish → verify signature in handler → return 200 fast → configure retries/deduplication) so signature verification and delivery failures have explicit checkpoints.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The ~60-line body avoids beginner-concept explanations, but contains noticeable padding: the persona narrative ("You've scheduled millions of messages, set up cron jobs that run for years"), a filler "When to Use" sentence ("This skill is applicable to execute the workflow or actions described in the overview."), and a truncated line ("1. HTTP is the universal language - no c") — mostly efficient but could be tightened, matching anchor 3 rather than 2 since padding is a minority of a short document. | 3 / 5 |
Actionability | There is no executable guidance anywhere: the Patterns sections are one-line descriptions ("Sending messages to be delivered to endpoints"), the Sharp Edges "Solution" column holds only comment-label stubs ("# Always verify signatures with both keys:", "# Configure retries per message:") with no code, commands, API URLs, or SDK names, and the Anti-Patterns have no content at all. It only describes rather than instructs — anchor 1, not 2, since even high-level hints naming specific tools or steps are absent. | 1 / 5 |
Workflow Clarity | No multi-step process is ever sequenced: publishing a message, setting up cron, or verifying signatures (a security-critical operation) each get at most a one-line label, with no steps and no validation checkpoints. This matches anchor 1 ("steps missing or incoherent; no sequence; no validation"), not anchor 2, which requires at least a rough sequence to be present. | 1 / 5 |
Progressive Disclosure | No bundle files exist or are referenced, and the body does have labeled sections (Capabilities, Patterns, Anti-Patterns, Sharp Edges table), but the structure is hollow — empty stub sections, a broken numbered list, and a filler section — so it "could be better organized," matching anchor 3 rather than 4. | 3 / 5 |
Total | 8 / 20 Passed |