Loyalty Designer
v1.1.0Design points-based, tiered, or referral loyalty programs with reward structures calibrated to your margin and customer purchase frequency.
⭐ 0· 64·0 current·0 all-time
byLeroyCreates@leooooooow
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description (designing points, tiers, referrals) matches the provided SKILL.md and reference files. There are no unrelated env vars, binaries, or install steps requested — everything is documentation and templates appropriate for a design/consulting skill.
Instruction Scope
SKILL.md and the supporting files contain only procedural guidance, formulas, templates, and checklists for designing loyalty programs. There are no commands, system file reads, external endpoints, or instructions to access credentials. The runtime instructions stay within the stated design scope.
Install Mechanism
No install spec or code files are present; this is instruction-only. That minimizes disk/writing/execution risk and is proportionate for a documentation/template skill.
Credentials
The skill does not request environment variables, credentials, or config paths. The materials do not require secrets or external service access; requested resources are proportionate to the stated purpose.
Persistence & Privilege
always is false and the skill does not request elevated or persistent system privileges. It does not modify other skills' configs or require permanent presence.
Assessment
This skill is a documentation/template package for designing loyalty programs and appears internally consistent. Things to consider before installing: (1) provenance — the source and owner are unknown, so confirm you trust the provider before using company-sensitive data; (2) do not paste real customer PII, credentials, or raw financial exports into the skill's prompts or outputs unless you control where that data goes; (3) validate the financial model outputs against your actual margin and transaction data before acting on recommendations; and (4) if you plan to integrate any of these designs with production systems (points ledger, referral attribution), audit the actual implementation code or vendor you will use — the guidance here is conceptual and must be implemented securely.Like a lobster shell, security has layers — review code before you run it.
latestvk973ss4tdvae0yq8hrng684w15840dtp
License
MIT-0
Free to use, modify, and redistribute. No attribution required.