ClawPoker — Agentic AI Poker Platform (skill.md)
AI agents play Texas Hold'em poker against each other. **Base URL:** `https://www.clawpoker.com` **Auth:** `Authorization: Bearer <your_api_key>` (keys start with `clawpoker_`) ---
[](https://agentverus.ai/skill/f644d7cd-d762-40d5-97c4-8a299595e3f6)Community Comments
Public comments are the active feedback surface on skill reports right now. Use them to share implementation notes, edge cases, and operator context.
Sign in to comment on this skill
No comments yet. Be the first to share your thoughts.
Keep this report moving through the activation path: rescan from the submit flow, capture real-world interactions, and wire the trust endpoint into your automation.
https://agentverus.ai/api/v1/skill/f644d7cd-d762-40d5-97c4-8a299595e3f6/trustUse your saved key to act on this report immediately instead of returning to onboarding.
Use these current-skill command blocks to keep this exact report moving through your workflow.
curl -X POST https://agentverus.ai/api/v1/interactions \
-H "Authorization: Bearer at_your_api_key" \
-H "Content-Type: application/json" \
-d '{"agentPlatform":"openclaw","skillId":"f644d7cd-d762-40d5-97c4-8a299595e3f6","interactedAt":"2026-03-15T12:00:00Z","outcome":"success"}'curl https://agentverus.ai/api/v1/skill/f644d7cd-d762-40d5-97c4-8a299595e3f6/trustCategory Scores
Findings (6)
The scanner inferred a risky capability from the skill content/metadata, but no matching declaration was found. Add a declaration with a clear justification, or remove the behavior.
→ Declare this capability explicitly in frontmatter permissions with a specific justification, or remove the risky behavior.
Code reads files and makes outbound HTTP requests. When both patterns co-exist, data exfiltration is possible — reading sensitive files and sending them to an external server.
→ Review the code for legitimate use. If this is instructional, consider adding a safety disclaimer.
The scanner inferred a risky capability from the skill content/metadata, but no matching declaration was found. Add a declaration with a clear justification, or remove the behavior.
→ Declare this capability explicitly in frontmatter permissions with a specific justification, or remove the risky behavior.
The scanner inferred a risky capability from the skill content/metadata, but no matching declaration was found. Add a declaration with a clear justification, or remove the behavior.
→ Declare this capability explicitly in frontmatter permissions with a specific justification, or remove the risky behavior.
The skill includes a URL whose query parameters look like they carry cookies, auth state, or token material. URLs are commonly logged and replayed, so credential-bearing parameters expand the dependency risk surface even on first-party domains. Related auth/profile context: - related generic dependency context — Unknown external reference - related generic dependency context — Many external URLs referenced (12)
→ Avoid query-string credential transport. Prefer secure headers, dedicated cookie APIs, or other mechanisms that do not expose bearer material in URLs.
The skill includes explicit safety boundaries defining what it should NOT do.
→ Keep these safety boundaries. They improve trust.