ClawPrint - Captchas for AI verification
v1.0.0Issue ClawPrint reverse-CAPTCHA challenges to verify that another user or agent is a real AI, not a human. Uses the ClawPrint API to generate speed or pattern challenges that only machines can solve within the time limit.
⭐ 1· 1.6k·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
Name, description, required binaries (curl, jq), and the three environment variables (server URL, site key, secret key) are consistent with an API-driven challenge/verification workflow. The bundled helper script performs only the expected API calls (challenge, verify, validate).
Instruction Scope
SKILL.md instructs the agent to request challenges, present the full challenge data to the other agent, accept replies, and post answers to the configured server for verification and validation. That is coherent for the stated purpose, but it explicitly directs the agent to transmit challenge payloads (grids, operands) and — during validation — the secret key to the configured CLAWPRINT_SERVER_URL. Presenting full grid data to third parties is necessary for pattern challenges but increases the amount of data shared with conversation partners. The instructions also advise using validation with the secret key (server-side) — which sends a sensitive secret to the server; the skill assumes the server is trusted.
Install Mechanism
No install spec; the skill is instruction-only plus a small helper shell script. No downloads or external installers are used. This is low-risk from an install/execution standpoint.
Credentials
The registry declares CLAWPRINT_SECRET_KEY as required, but the helper script only needs the secret for the 'validate' action; issuing and verifying can work with just server URL and site key. Requiring a private secret by default is disproportionate. More importantly, the skill's functionality requires sending that secret to the configured CLAWPRINT_SERVER_URL for server-side validation — meaning you must trust that remote server with a high-value secret. There is no homepage or trusted upstream source listed, which increases the risk of secret exfiltration.
Persistence & Privilege
The skill does not request elevated platform privileges, does not set always:true, and does not modify other skills' configuration. Autonomous invocation is allowed (platform default) but not combined here with other privilege escalations.
What to consider before installing
This skill appears to implement a legitimate challenge/verify flow, but exercise caution because the skill requires a private secret that will be sent to whatever CLAWPRINT_SERVER_URL you configure. Before installing: (1) verify the ClawPrint server endpoint and operator are trustworthy (there's no homepage or known owner listed); (2) don't supply high-value production secrets — test with disposable keys first; (3) consider whether you truly need server-side validation (validate uses the secret) or if verify alone is sufficient; (4) be aware that presenting full challenge data to other agents may disclose data you wouldn't otherwise share; and (5) if you can't confirm the server's trustworthiness, do not provide CLAWPRINT_SECRET_KEY. Confidence is medium because the code is coherent with its purpose but the unknown source and default requirement for a secret create meaningful risk.Like a lobster shell, security has layers — review code before you run it.
latestvk9780r2j4wqwnxafyeafw5tnp980gybh
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🐾 Clawdis
Binscurl, jq
EnvCLAWPRINT_SERVER_URL, CLAWPRINT_SITE_KEY, CLAWPRINT_SECRET_KEY