Recurring Core
Freepublic on GitHub, forever
- The api reference: Recharge API correctness
- The router that loads it on the right task
- One command to install, in any repo
- No account, no sign-up, no email
Works with Claude Code, Codex and Cursor
Recurring teaches your coding agent how Recharge really behaves, plus the Shopify and Klaviyo surfaces it reaches, so the silent failures never ship.
npx skills add HarjjotSinghh/subscription-commercePrefer to start free? Try the core skill on GitHub. Pro is $29 until 27 Sep 2026, then $59. One payment.
Both versions pass their tests. Here is what your customers get.
Add skip next delivery, cancel, and a win-back email to our Shopify and Recharge store.
Customer still gets billed
It skipped the order. Recharge bills from the queued charge.
Customer isn't billed
Skips the queued charge and confirms it.
Billed a month after cancelling
A timeout was swallowed, so the cancel never landed.
Cancel always lands
Retries on timeout, then confirms the status.
Customer gets two emails
Recharge sends one by default (send_email), Klaviyo sends another.
Customer gets one email
Sets send_email: false on the cancel.
Wrong fields come back
No version header, so every call runs on 2021-01.
Every call on 2021-11
Pins X-Recharge-Version once, in one gateway.
Add to cart fails
Plan-only products return 422 without a selling_plan.
Add to cart works
Sends selling_plan with every plan-only item.
Win-back reaches no one
vip = false skips everyone who never had vip set.
Win-back reaches everyone
Matches false or not set.
An illustration built from documented platform behavior, not from any customer's store. Read-only by default: nothing touches your store until you approve it.
All four are public, dated, and recent. Miss one and the code still compiles.
A map, not a manual: your agent reads at most two of the six per task.
SKILL.md, the one file your agent reads first.
On a live store the agent stays read-only until you approve each write, because these systems move real money.
They hold on every task, whichever reference the agent opens.
Send X-Recharge-Version: 2021-11 on every call, or the API answers on 2021-01.
Never trust a list filter you haven't verified. Pull a customer-scoped list and filter it in code.
A renewal is a Shopify order whose sourceName starts with subscription_contract, never a Recharge tag.
Report success only after the platform confirms it. A 422 reading "already cancelled" means the first call landed.
Silence is not success. Every change ends with a check that fails loudly when it didn't land.
Open one reference for the task, two at most. Reading everything makes the wrong rule easier to reach for.
Ten tasks an agent gets wrong on its own, each graded by running the code.
Both numbers land here at launch, unedited, whatever they turn out to be.
The full baseline runs three repeats of every task, with the skill and without it. Both scores land here at launch, unedited. The tasks stay out of the skill, so a pass means the lesson carried to a task it had never seen.
Both install with the same command, in the same way.
recharge-api.mdrecharge-api.mdrecharge-ops.mdshopify-surfaces.mdklaviyo-lifecycle.mdpr-audit.mdtest-cases.mdOnce for Pro, and never for the core skill.
Freepublic on GitHub, forever
$29until 27 Sep 2026, then $59
Claude Code, Codex and Cursor, and any agent that reads project skills from a folder. One command adds it to the repo you are working in.
It is, and so is every skill. What you pay for is which sentences are in it: the version header, the retired portal, the contract your app cannot see, the filter that quietly matches nobody. Knowing those exist is the work. The ten eval tasks are there so you can check the lesson carries instead of taking my word for it.
No. It stays read-only by default and asks for approval before any write. These systems move real money, so nothing runs against your store without you.
Access to a private GitHub repo with the router, all six reference files and the ten eval tasks. The invite goes out by email after checkout, and you install it with the same one command as the free core skill.
No. Ask for the feature in plain words, in the same chat as always. The skill loads itself when the task touches subscriptions.
Yes. One purchase covers every repo you work in, client stores included. There is no seat check and nothing phones home. If more than one developer needs it, buy a copy each.
Platform behavior moves, so the references move with it. Updates through v1 are included in the one payment, and nothing renews on its own.
Email within 14 days of buying and you get the full amount back, no questions asked.
No. Recurring is an independent product, built from production experience and not endorsed by any of them.
npx skills add HarjjotSinghh/subscription-commerce