tessl install https://github.com/secondsky/claude-skills --skill idempotency-handlinggithub.com/secondsky/claude-skills
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.
Average Score
94%
Content
92%
Description
100%
Generated
Validation
Total
12/16Score
PassedWarnings & errors only
| Criteria | Score |
|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') |
metadata_version | 'metadata' field is not a dictionary |
license_field | 'license' field is missing |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow |
Content
Total score
11/12| Dimension | 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 |
Overall Assessment
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.
Description
Total score
12/12| Dimension | 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 |
Overall Assessment
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.