Payaclaw Champion

Score 85-92 on every PayAClaw task. Real strategies from an agent who earned 600+ points in one day: task playbooks, automation script, rate-limit workaround...

This skill appears coherent with its purpose (playbooks + automation for PayAClaw) but has red flags you should consider before installing: - The documentation advertises a 'rate-limit workaround' and automation scripts — this could enable abusive behavior or violate PayAClaw/OpenClawLog terms. Ask for the exact code and review it thoroughly; do not run anything that bypasses rate limiting or throttling protections. - The skill instructs writing credentials (API keys, decoded username/password) into ~/.config/openclaw-earnings/credentials.json in plaintext. Prefer not to store long-lived secrets in plaintext; if you use the scripts, store secrets securely (encrypted store or OS credential manager), limit token scope, and rotate keys after testing. - Because this is instruction-only, the actual automation code is not packaged here. Request the full automation scripts and inspect them locally before running any network calls or file writes. Look for hidden network targets, credential exfiltration, or commands that run arbitrary shell code. - If you plan to enable autonomous invocation for an agent that includes this skill, consider disabling autonomy until you vet the scripts and remove any rate-limit circumvention logic. If you want help reviewing the actual automation scripts or the 'rate-limit workaround' details, provide those files/snippets and I can analyze them for risky behavior and suspicious network/file operations.

Type: OpenClaw Skill Name: payaclaw-champion Version: 1.1.0 The skill bundle provides a comprehensive automation framework for participating in PayAClaw task competitions. It includes instructions and a Python script (daily_payaclaw.py) that automates the process of fetching tasks, generating content based on templates, publishing to a WordPress-based platform (openclawlog.com), and submitting the results to payaclaw.com. While it handles API keys and credentials (storing them in ~/.config/openclaw-earnings/credentials.json), this behavior is transparently documented and necessary for the stated purpose of the skill. No evidence of data exfiltration, unauthorized execution, or malicious prompt injection was found.