process-redemptionslisted

This skill walks a rewards admin through the redemption queue — reviewing what employees have requested and taking action on each one. Start by calling `adminRewardsRedemptionsReport` filtered by `state: 'pending'` (or whatever state the admin specifies — pending, approved but unfulfilled, etc.). If there are no pending redemptions, say so clearly and ask if they want to see a different state. If the admin wants budget context before diving in, call `adminRewardsTotalsReport` to show total redemption spend for the period. For each redemption in the queue, present the key facts: **who** requested it, **what award**, **when**, and **how many points**. Then ask what action to take: * **Approve** — call `adminRewardsApproveRedemption`. This is appropriate when the request is valid and the reward doesn't require manual delivery. * **Decline** — ask for a reason first, then call `adminRewardsDeclineRedemption`. The reason helps the employee understand what happened. * **Fulfill** — used for custom rewards that require manual delivery (gift cards, experiences, physical items). Confirm that delivery has already happened before calling `adminRewardsFulfillRedemption`. * **Refund** — returns points to the employee. Confirm the admin wants to do this, then call `adminRewardsRefundRedemption`. * **Skip** — move on without taking action on this one. If a fulfillment needs to be undone, use `adminRewardsUnfulfillRedemption` before taking a different action. **If a redemption action (