idempotency-handling
Idempotent API operations with idempotency keys, Redis caching, DB constraints. Use for payment systems, webhook retries, safe retries, or encountering duplicate processing, race conditions, key expiry errors.
97
96%
Does it follow best practices?
Impact
100%
1.35xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly defines a specific technical domain (idempotency patterns) with concrete implementation details and excellent trigger coverage. It follows the recommended format with explicit 'Use for' guidance and includes both high-level use cases (payment systems) and specific error conditions (race conditions, key expiry errors) that would naturally trigger selection.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Idempotent API operations with idempotency keys, Redis caching, DB constraints' - these are concrete technical implementations, not vague abstractions. | 3 / 3 |
Completeness | Clearly answers both what ('Idempotent API operations with idempotency keys, Redis caching, DB constraints') and when ('Use for payment systems, webhook retries, safe retries, or encountering duplicate processing, race conditions, key expiry errors') with explicit 'Use for' clause. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'payment systems', 'webhook retries', 'safe retries', 'duplicate processing', 'race conditions', 'key expiry errors' - these are exactly the terms developers use when facing these problems. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche focused on idempotency patterns with specific technical context (Redis, DB constraints) and clear problem domains (payment systems, webhooks, race conditions) - unlikely to conflict with general API or database skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
92%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality skill that provides concrete, executable patterns for idempotency handling. The code examples are complete and production-ready, covering both Redis and database-backed approaches with proper error handling. The only minor weakness is the length of the cleanup section which could benefit from being extracted to a separate reference file.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, jumping directly into executable code patterns without explaining what idempotency is or why it matters (Claude already knows). Every section provides actionable content without padding. | 3 / 3 |
Actionability | Provides fully executable JavaScript and SQL code that is copy-paste ready. The database schema, middleware pattern, and payment processing function are complete and immediately usable. | 3 / 3 |
Workflow Clarity | The database-backed pattern clearly shows the sequence: insert with processing status → execute payment → update to completed/failed. Error handling and race condition handling are explicit with clear status checks and appropriate error messages. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but the cleanup strategies section is quite lengthy and could be split into a separate reference file. The skill is approaching the threshold where external references would improve organization. | 2 / 3 |
Total | 11 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- secondsky/claude-skills
- Commit
90d6bd7
- 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.