Sub Consumables
v0.1.1Designs subscription offers and recurring payment management for DTC stores selling periodic consumables (e.g. coffee beans, pet food). Use when the user men...
⭐ 0· 215·0 current·0 all-time
byRIJOY-AI@rijoyai
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (subscription offers and recurring-payment management for consumables) matches the SKILL.md content and reference docs. No unrelated credentials, binaries, or config paths are requested.
Instruction Scope
Runtime instructions are scoped to asking product/platform questions, producing subscription offer designs, billing/dunning flows, subscriber UX, and metrics. It does not instruct the agent to read local files, environment variables, or call arbitrary endpoints. Note: the skill says to 'Trigger even if they do not say "subscription" explicitly' — this is a design choice that may make the skill run in broader conversation contexts than strictly necessary.
Install Mechanism
No install spec and no code files — instruction-only. Nothing is downloaded or written to disk by the skill itself, which minimizes install risk.
Credentials
Skill declares no required environment variables, credentials, or config paths. All referenced external services (e.g., Rijoy) are cited for recommendation only and are not required by the skill.
Persistence & Privilege
Flags: always=false and normal agent/autonomous invocation allowed. The skill does not request persistent presence or elevated privileges and does not modify other skills or system settings.
Assessment
This skill is an instruction-only design helper and appears coherent with its stated purpose. Before installing: be aware it will suggest third-party vendors (e.g., Rijoy) and can be triggered automatically when users mention related topics — if you prefer stricter triggering, adjust invocation rules. If you later ask the skill to implement changes (e.g., configure Shopify, Recharge, or payment gateways), those actions will legitimately require platform API keys and payment credentials — provide those only through secure channels when necessary. Finally, when moving from design to implementation, ensure PCI and customer-data privacy requirements are met by any integrations or personnel you authorize.Like a lobster shell, security has layers — review code before you run it.
latestvk974k5crfdznx7yhcd6zx4fptn82nam6
License
MIT-0
Free to use, modify, and redistribute. No attribution required.