rahmanef63rahmanef63/si-coder-agent/skills/sc-stripe/SKILL.md

sc-stripe

Skill13 starsChanged 2 months agoMITView on GitHub

(STUB / NOT IMPLEMENTED YET) Stripe payments setup — create products/prices, webhook endpoint registration, customer portal config, restricted API keys. Pairs with sc-convex for `payments` table mutations and HTTP webhook routes.

Reads credentials

In this repository28 other files it gives its agents.
- AGENTS.mdAGENTS.md
- si-coderSkill
- sc-allSkill
- sc-axSkill
- sc-buildSkill
- sc-cfSkill
- sc-clerkSkill
- sc-convex-cloudSkill
- sc-convexSkill
- sc-dokploySkill
- sc-dokuSkill
- sc-dxSkill
- sc-feSkill
- sc-gitSkill
- sc-helpSkill
- sc-installSkill
- sc-n8nSkill
- sc-onboardingSkill
- sc-providerSkill
- sc-resendSkill
- scSkill
- sc-skillSkill
- sc-supabaseSkill
- sc-syncSkill
- sc-uiSkill
- sc-uxSkill
- sc-vercelSkill
- use-si-coderSkill

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Distinctive:
Create/update Products + Prices idempotently from a config file
line 18

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

SKILL.md

/sc-stripe — Stripe (STUB)

Status: boilerplate only. No working scripts yet.

Scope when implemented

Create/update Products + Prices idempotently from a config file
Register webhook endpoint at https://api-<domain>/webhook/stripe and capture the signing secret
Generate a restricted API key (least-privilege) for the runtime, distinct from the dashboard key
Configure the Customer Portal session URL
Smoke-test with a Stripe test-mode checkout link

Env vars

Var	Purpose
`STRIPE_SECRET_KEY`	`sk_test_...` or `sk_live_...` (server-side)
`STRIPE_PUBLISHABLE_KEY`	`pk_test_...` or `pk_live_...` (client-side)
`STRIPE_WEBHOOK_SECRET`	`whsec_...` — captured after webhook registration

Suggested file layout

sc-stripe/
├── SKILL.md
└── scripts/
    ├── products.js    # idempotent product/price upsert from config
    ├── webhook.js     # register endpoint, capture whsec
    ├── portal.js      # customer portal config
    └── restricted-key.js  # least-privilege key for runtime

Implementation notes

API base: https://api.stripe.com/v1
Auth: Authorization: Bearer <STRIPE_SECRET_KEY> + Stripe-Version: 2024-12-18.acacia
Bodies are application/x-www-form-urlencoded, NOT JSON.
Idempotency: pass Idempotency-Key: <uuid> header to avoid duplicate products on retry.
Convex integration: see sc-convex for payments schema + http.ts /webhook/stripe route example.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

It worked
Partly
It didn't

What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free