Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →hashgraph-online/billing-sdk
Guide for building billing UI with BillingSDK - the open-source React component library for pricing tables, subscription management, usage meters, invoice history, and customer portal flows wired to Dodo Payments.
Passed 22 of 23 test cases with the skill, and 6 of 23 without it.
and 27 more in the full report
16 fixed6 passed either way1 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 16 test cases the skill fixed. Same model, same prompt, with and without the skill.
I am configuring environment variables for our Dodo Payments SDK and webhook handling in Next.js. What environment variable name does the SDK expect for verifying incoming webhook signatures?
| Checked | Without skill | With skill |
|---|---|---|
| The environment configuration specifies DODO_PAYMENTS_WEBHOOK_KEY as the variable name for webhook verification. | Missed | Passed |
| The solution avoids using DODO_PAYMENTS_WEBHOOK_SECRET for the webhook key variable. | Missed | Passed |
The instructions your model reads when the skill loads.
BillingSDK is an open-source React component library for billing interfaces, maintained by Dodo Payments
at github.com/dodopayments/billingsdk. Components are copied into your repository as source files
(shadcn/ui model) rather than imported from a runtime npm package.
Use this skill when building the front end. All Dodo Payments API calls belong in server-side route handlers; the components are presentation only.
@billingsdk/cli init or add individual components.Source-installed, not a dependency. The repository root package billingsdk is private. There is no
verified general-purpose runtime npm component package. You install components through the CLI or the
shadcn registry, and the .tsx files land in your project under components/billingsdk/.
The installed file is the prop contract. Because components are vendored into your repo, the exported
props type in components/billingsdk/<component>.tsx is authoritative for your version. Read it before
wiring callbacks. Do not assume prop names from another project.
The registry is the installability source of truth. Use
registry.json. The docs navigation
has drifted from it — for example payment-success-dialog appears in navigation but not in the current
registry. If add fails, the block is not in the registry.
Components never call Dodo. They receive data and fire callbacks. Every Dodo Payments call runs on your
server with DODO_PAYMENTS_API_KEY. That key is dodo_test_... or dodo_live_... and must never reach
the browser.
Scaffold a new integration (framework config, API routes, useBilling hooks, lib/dodopayments.ts,
dependencies, and env vars DODO_PAYMENTS_API_KEY, DODO_PAYMENTS_ENVIRONMENT,
test cases passed, vs 6 / 23 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.