My redemptions
Bonusly's Claude Plugin
npx -y skills add bonusly/bonusly-claude-plugin --skill my-redemptionsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use when someone wants to see their own reward redemptions — what they've redeemed, the status of a reward, where a gift card or claim link is, or whether a redemption went through.
SKILL.md
1.8 KB, 383 tokens by cl100k_base, as published. Nobody here has run it
This skill is the employee-facing view of your own reward redemptions — "what have I redeemed?", "where's my gift card?", or "did my redemption go through?". It's read-only and scoped to the calling user. For admins processing other people's redemptions, use process-redemptions; for company-wide spend reporting, use rewards-spend-report.
For a list of the caller's redemptions, call getMyRedemptions. It returns redemptions newest-first with each one's state, catalog/reward details, and claim and certificate URLs. total_count is the caller's full count; redemptions is one page. It's cursor-paginated:
- Pass
limit(1–100, default 20) on the first call. - When
next_cursoris non-null there are more pages — pass it back ascursorand keeplimitidentical across pages.
For a single redemption the user is asking about specifically, call getRedemption with its id. The caller can always read their own redemptions; reading someone else's requires a rewards-admin role, so for the personal use case this is fine.
When summarizing, lead with what the user actually wants: the current state of each redemption and, when it's fulfilled, the claim or certificate URL so they can get to their reward. If a redemption is still pending or unfulfilled, say so plainly and set expectations rather than implying it's ready.
If the user has no redemptions, say so simply. If they're looking for a specific reward and it's not on the first page, offer to paginate before giving up.
Access note: listing your own redemptions requires rewards:read. If a call fails on permissions, surface the required scope.