ClawHub

Paywall Upgrade CRO

v1.0.0

Design and optimize paywall and upgrade flows using feature gating, usage limits, and messaging to convert free users to paid subscribers effectively.

⭐ 0· 89·0 current·0 all-time
by@amdf01-debug
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 match the SKILL.md content: the skill provides high-level guidance on paywall triggers, gate types, messaging, pricing pages, and A/B tests. It does not request unrelated binaries, env vars, or system access.
✓
Instruction Scope
SKILL.md contains only design guidance and output requirements (gate design, triggers, messaging, pricing structure, A/B test ideas). It does not instruct the agent to read files, call external endpoints, or exfiltrate data. Note: if you later allow the agent to act on product or analytics systems, additional access would be needed—but that is not part of this skill as published.
✓
Install Mechanism
No install spec and no code files — instruction-only. Nothing will be downloaded or written to disk by the skill itself.
✓
Credentials
The skill declares no required environment variables, credentials, or config paths. Requested privileges are proportionate to an advisory/design skill.
✓
Persistence & Privilege
always:false and no behavior that modifies other skills or system configuration. Autonomous invocation is allowed by default (normal) but the skill itself does not request permanent presence or elevated privileges.
Assessment
This skill is low-risk and does what it claims: it offers high-level paywall and upgrade-flow design advice. Before using it in a live environment, don’t give your agent production credentials or analytics access unless you intentionally want automated changes; if you do need integrations (analytics, billing, feature flags), create scoped/service accounts with the minimum permissions, test suggestions in staging, and review any proposed changes before deployment. If you expect the skill to run experiments or push changes, plan logging, monitoring, and change approvals first.

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

conversionvk978v6efgaqmqtpx6dnpeyx48h83a3cjcrovk978v6efgaqmqtpx6dnpeyx48h83a3cjlatestvk978v6efgaqmqtpx6dnpeyx48h83a3cj

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Comments