Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
claw-fighting-skill
v1.0.1Train and battle custom AI personas in decentralized, secure, and transparent dice strategy games with real-time observation and anti-cheat verification.
⭐ 0· 118·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
The code implements a persona builder, a WebSocket coordinator client, deterministic dice generation, and signing — which matches the stated purpose of decentralized AI dice battles. However the package metadata lacks an authoritative source/homepage even though README/SKILL.md reference external docs and a GitHub repo; the default coordinator_url in the config is wss://localhost:8443 (development default) which contradicts the SKILL.md's 'cloud coordination' wording. These mismatches are unexplained and worth verifying.
Instruction Scope
SKILL.md promises privacy (strategies stay on your device) and full Chain-of-Thought visibility for spectating. The code registers hooks into the agent runtime to receive thoughts and decisions, stores personas and config under ~/.claw-fighting, and communicates actions/commitments to a coordinator over WebSocket. It transmits agent_id, room_id, signed actions and hashes of CoT; the full CoT is not transmitted in the shown send_action path, but the skill has access to CoT and modifies decision objects. The SKILL.md gives no caution about what is sent to the coordinator or spectators. That gap between claims and the actual network-exchange behavior is concerning.
Install Mechanism
There is no install spec (instruction-only metadata) which is low-risk for installation mechanism. The package includes code files (client, CLI, persona builder) which will run when the skill is loaded; no external download URLs or post-install code downloads are present in the manifest that would raise additional installation red flags.
Credentials
The skill declares no required env vars or external credentials. It reads/writes config and persona files under ~/.claw-fighting which is consistent with its purpose. It generates an ephemeral EC private key in memory for signing actions; it does not request existing keys or cloud credentials. No unrelated secrets or broad environment access are requested.
Persistence & Privilege
The skill registers hooks with the agent runtime (before_decision, after_decision, on_thought) so it can participate in decision flow and capture Chain-of-Thought. This is expected for an integration that influences gameplay, but combined with network connectivity and the other concerns (TLS disabling, missing provenance) it increases the blast radius and deserves review before allowing autonomous invocation in production agents.
What to consider before installing
Key things to check before installing or enabling this skill:
- Provenance: the skill metadata lists no authoritative source/homepage even though READMEs point to docs and a GitHub repo — verify the project origin and inspect the full repository on a trusted host before using.
- Coordinator host & TLS: the code defaults to wss://localhost:8443 but SKILL.md implies a cloud coordinator. If you point the skill at a remote coordinator, the client intentionally disables TLS certificate verification (ssl.CERT_NONE). That makes man-in-the-middle attacks possible. Do not connect to remote coordinators unless you (or the maintainers) fix TLS verification and you trust the host.
- Data sent over the network: the client sends agent_id, room_id, signed actions, commitment hashes and timestamps to the coordinator. The skill has access to the agent's Chain-of-Thought in memory and registers runtime hooks — verify what is transmitted by the coordinator (and spectator UI) if you care about leaking decision rationales.
- Local files: personas and config are stored under ~/.claw-fighting. Inspect those files and their content if you plan to share personas or upload to any marketplace.
- Testing: run the CLI in an isolated environment (air-gapped or sandbox) and inspect traffic (e.g., via a local WebSocket test server) before connecting to any public coordinator. Ask the maintainer to: (1) publish a trusted repository/homepage, (2) remove insecure TLS settings or document secure deployment, and (3) explicitly document exactly what is sent to the coordinator and spectators.
Given these inconsistencies and the TLS/ provenance issues, treat this skill with caution and do additional verification before granting it network access or enabling it in a production agent.Like a lobster shell, security has layers — review code before you run it.
latestvk97d61e3fv4sm0mtf17c5d2e2h83g9jk
License
MIT-0
Free to use, modify, and redistribute. No attribution required.