Paywall
v1.0.0Build high-converting paywalls for mobile apps and web with proven patterns, pricing strategies, and A/B testing.
⭐ 2· 634·2 current·2 all-time
byIván@ivangdavila
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 paywalls, pricing, and A/B tests) matches the files and runtime instructions. All required capabilities are purely informational: layout, copy, placement, pricing, and testing guidance. No unrelated credentials, binaries, or config paths are requested.
Instruction Scope
SKILL.md and the included files instruct the agent to produce paywall designs, copy, layouts, and testing plans. The trigger phrases are product-oriented (e.g., "create paywall", "improve conversion") and do not instruct the agent to read system files, access secrets, or call external endpoints beyond mentioning common third-party tools as examples. No vague 'gather any context' directives or data-exfiltration steps are present.
Install Mechanism
No install spec and no code files — this is instruction-only. Nothing will be downloaded or written to disk by an installer, so install mechanism risk is minimal.
Credentials
The skill declares no required environment variables, no primary credential, and no config paths. It references third-party services (RevenueCat, Stripe, Superwall) purely as examples; those references are reasonable for a paywall/monetization guide and currently do not imply credential collection.
Persistence & Privilege
always:false and default model-invocation are set (agent may invoke the skill autonomously, which is the platform default). The skill does not request persistent system presence or modify other skills or system configuration.
Assessment
This skill is essentially a documented playbook for building paywalls and appears internally consistent and low-risk. It does not request credentials or install code. Before installing, consider: (1) If you later connect this skill to live systems (analytics, payment processors like Stripe/RevenueCat), only provide the minimum API keys you must and vet those connectors. (2) Some recommended tactics (urgency, discounts, aggressive placement) can affect user trust or violate platform policies — follow app store guidelines and your legal/UX teams. (3) Because it’s instruction-only, risks arise only if you embed or script these instructions into automated flows that then access real systems; audit any automation that uses the guidance.Like a lobster shell, security has layers — review code before you run it.
latestvk976h1mm70qsbgv3jgj755pfzx810ygz
License
MIT-0
Free to use, modify, and redistribute. No attribution required.