refund-customer

Issues customer refunds and records them in the accounting ledger.

1|Updated Jul 1, 2026
One-click install
npx skills add https://github.com/ginaecho/skill-achievability-compiler --skill refund-customer-ginaecho
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: refund-customer
Source: https://github.com/ginaecho/skill-achievability-compiler/tree/main/corpus/skills/missing_tool_chain
Command: npx skills add https://github.com/ginaecho/skill-achievability-compiler --skill refund-customer-ginaecho

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Processing a customer refund requires coordinating multiple steps: finding the order, issuing the payment reversal, and recording the transaction in the accounting ledger. Missing any step leaves the books inconsistent with actual payouts. ## Core Features & Use Cases - Order Lookup: Locates the customer's order using the lookup tool before any money moves. - Refund Execution: Issues the refund against the found order using the refund tool, which requires the order to be located first. - Ledger Recording: Records the refund outcome in the accounting ledger via update_ledger so the books match what was paid out. - Use Case: A support agent needs to refund a customer for a returned item; the workflow looks up the order, issues the refund, and updates the ledger in one guided sequence. ## Quick Start Refund the customer for order 12345 and record the transaction in the accounting ledger.

Frequently Asked Questions about refund-customer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I refund a customer and update the accounting ledger?▼

Look up the customer's order first, then issue the refund against that order, and finally record the outcome in the ledger via update_ledger. All three steps are required so the books match what was actually paid out.

What tools are required to process a customer refund?▼

The workflow requires three tools: lookup to find the order, refund to issue the payment reversal, and update_ledger to record the transaction. The refund tool only works after the order has been found.

Why must the order be looked up before issuing a refund?▼

The refund tool requires the order to be marked as found before it can execute. This ordering constraint ensures refunds are always tied to a verified order rather than issued blindly.

What happens if the ledger is not updated after a refund?▼

The task is considered incomplete if the ledger is not updated. Money that never reaches the ledger leaves the accounts wrong, so both the refund and the ledger entry must succeed.

Can this refund workflow run if update_ledger is unavailable?▼

No. The workflow explicitly depends on update_ledger to record the outcome, so an environment lacking that tool cannot complete the task as written and would be flagged as missing a required capability.