Rebuy Booster

v1.1.0

Design post-purchase sequences, loyalty incentives, and re-order triggers that turn one-time buyers into repeat customers for ecommerce brands.

0· 88·0 current·0 all-time
byLeroyCreates@leooooooow
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The name, description, and all included reference documents focus on post-purchase sequences, loyalty programs, re-order triggers, and platform-specific setup (Klaviyo, LoyaltyLion, Yotpo, Smile.io). There are no unrelated dependencies, env vars, or binaries requested in the registry metadata — the requested resources match the skill's stated purpose.
Instruction Scope
SKILL.md repeatedly asks the agent to use order history, repurchase intervals, and platform properties (e.g., Klaviyo profile props) to calculate triggers and build flows. That is appropriate for the purpose, but the instructions assume access to store/order data and platform configuration. The skill is instruction-only and does not include code to fetch those things; at runtime the agent will need the user to provide order data or platform credentials to act on those instructions.
Install Mechanism
No install specification and no code files mean nothing will be written to disk or downloaded during install. This is the lowest-risk install profile and is appropriate for a content/instructions skill.
Credentials
The skill declares no required environment variables or credentials. The content does reference third-party platforms and implies needing access to order history and ESP/loyalty integrations; that is proportionate to the purpose but users should be aware the agent may request API keys, exported order data, or platform access during a consultation. No unexpected or unrelated credential requests are embedded in the skill files.
Persistence & Privilege
Flags show the skill is not always-on and uses default autonomous invocation behavior. There is no persistent install behavior, no modification of other skills, and no requests to change agent/system-level settings.
Assessment
This skill is instruction-only and appears coherent for designing post-purchase and loyalty programs. Before using it: (1) do not hand over admin API keys or broad-scope credentials—provide least-privilege keys or an exported CSV of order history instead; (2) confirm what data the agent needs (order history, segment definitions, platform names) and supply only that data; (3) validate any segmentation, offer, or suppression logic in a staging environment and check GDPR/CAN-SPAM/CASL compliance before sending campaigns; (4) if the agent asks to connect to your ESP/loyalty platform, limit the connection scope and monitor activity; (5) treat the delivered templates as starting points — test A/B, suppression, and unsubscribe behavior before full deployment.

Like a lobster shell, security has layers — review code before you run it.

latestvk97atdqhyht3q5dhsta3mx5vv983xp06

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments