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.
Install with Tessl CLI
npx tessl i github:secondsky/claude-skills --skill idempotency-handlingOverall
score
94%
Does it follow best practices?
Validation for skill structure
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 effectively communicates both capabilities and use cases. It uses third person voice, lists specific technical implementations, and provides excellent trigger terms that match how developers naturally describe idempotency-related problems. The description is concise yet comprehensive.
| 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'). | 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 idempotency issues. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche focused specifically on idempotency patterns with clear technical scope (idempotency keys, Redis, DB constraints) and specific 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 that the cleanup strategies section adds significant length that could potentially be referenced externally.
| 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 cleanup jobs are all complete and functional implementations. | 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 detailed and could be split into a separate reference file. The skill is somewhat long for a single file, though not egregiously so. | 2 / 3 |
Total | 11 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 12 / 16 Passed | |
- 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.