lemon-squeezy
Read Lemon Squeezy revenue: list orders, subscriptions, customers, products; create checkout links. Trigger phrases: lemon squeezy, store orders, revenue, checkout link.
- License 许可
- MIT
- 最近更新
- 2026-11-07
- Stars
- ★ 0
- Forks
- 1
01 前言 Front Matter
- name
- lemon-squeezy
- tagline
- Read Lemon Squeezy revenue: list orders, subscriptions, customers, products; create checkout links.
- metadata
- { "includeInPrompt": true }
- description
- Read Lemon Squeezy revenue: list orders, subscriptions, customers, products; create checkout links. Trigger phrases: lemon squeezy, store orders, revenue, checkout link.
- catalog_auth
- API key via the secure credential flow
- catalog_hosts
- [ "api.lemonsqueezy.com" ]
02 资源文件 1
- 脚本bin/lemon-squeezy.py6.6 KB
03 SKILL.md 正文
Lemon Squeezy
Purpose
Read the user's Lemon Squeezy store: list orders, subscriptions, customers, and products. Create checkout links on confirmation. Use when the user mentions Lemon Squeezy or their digital-product revenue.
Tooling
All commands go through bin/lemon-squeezy.py:
bin/lemon-squeezy.py auth # verify the API key
bin/lemon-squeezy.py orders --limit 25 # list orders
bin/lemon-squeezy.py subscriptions --limit 25 # list subscriptions
bin/lemon-squeezy.py customers --limit 25 # list customers
bin/lemon-squeezy.py products --limit 25 # list products
bin/lemon-squeezy.py checkout-create --json '{"data":{"type":"checkouts","attributes":{...}}}' # create checkout (confirm first)
Reads accept --store-id, --status, and (customers) --email filters.
Auth
- Provider id:
lemon-squeezy(credential is collected ascustom.lemon-squeezy) - Collection: API key via the secure credential flow (
credentials.request_api_access); created in Lemon Squeezy under Settings > API. Test-mode keys exist for safe testing. - Allowed hosts:
api.lemonsqueezy.com - Status check:
bin/lemon-squeezy.py auth(must return"ok": true)
Operating Rules
- Lemon Squeezy is the merchant of record: ~5% + 50c per transaction, and it handles global sales tax and VAT. Reads move no money.
checkout-createcreates a real payment link: confirm the product, variant, and price with the user before creating, unless standing permission exists. Same for subscription cancellations and refunds.- Responses are JSON:API (nested
data.attributes); the CLI flattens them for display. - Reads need no confirmation.
- Never exfiltrate the credential: the CLI only ever handles surrogates (see
bin/lemon-squeezy.py). Do not print, log, or transmit the key value.
Files
- SKILL.md
- bin/lemon-squeezy.py
Maturity
🧪 Draft: written from Lemon Squeezy's public API docs; not yet live-tested end-to-end.
04 同仓库更多 Skills
web-scrape
Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open/fetch fails on JS-heavy pages, or when you need clean markdown/structured extraction from a site. Requires FIRECRAWL_API_KEY.
design-taste-frontend
tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML/CSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, "AI-made", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).