Loading...
Loading...
Found 4 Skills
Apply when implementing idempotency logic in payment connector code or handling duplicate payment requests. Covers paymentId as idempotency key, payment state machine transitions, retry semantics for cancellation and refund operations, and requestId handling. Use for preventing duplicate charges and ensuring correct Gateway retry behavior across Create Payment, Cancel, Capture, and Refund endpoints.
Create GitHub Issues for unimplemented requirements from specification files using feature_request.yml template.
Manage Things reminders and todo create/update requests with a deterministic MCP workflow that prevents duplicate tasks and date mistakes. Use when users ask to add, reschedule, or correct Things reminders, especially with relative dates or potential update-vs-create ambiguity.
When the user wants to build or improve a sales bot's ability to prevent contacting the same prospect through multiple channels simultaneously. Also use when the user mentions "duplicate prevention," "contact deduplication," "conversation collision," "multi-channel overlap," or "prospect fatigue prevention."