Back to skill
Skillv1.0.0
ClawScan security
tytyt · ClawHub's context-aware review of the artifact, metadata, and declared behavior.
Scanner verdict
SuspiciousFeb 12, 2026, 9:18 PM
- Verdict
- suspicious
- Confidence
- medium
- Model
- gpt-5-mini
- Summary
- The skill's instructions are for a Teneo Protocol SDK that expects an Ethereum private key and connects to an external WebSocket, but the package metadata, name/description, and declared requirements are inconsistent or missing — proceed only after clarifying origin and secret-handling.
- Guidance
- This skill's runtime instructions are a guide to using the Teneo SDK, which legitimately requires an Ethereum private key and connects to an external service — but the distributed metadata is inconsistent and the skill does not declare any required credentials. Before installing or using it: - Confirm the publisher and origin (the listing ownerId, _meta.json ownerId, and slug mismatch). Do not trust this skill if you can't verify who published it. - Do not paste your real Ethereum private key into examples or public code. If you try this SDK, use a dedicated wallet address with minimal funds and never reuse high-value keys. - Ask the publisher whether secrets should be supplied via environment variables or a secure secret store; prefer ephemeral or hardware-backed signing rather than raw privateKey strings. - Verify the SDK package on npm/github (check @teneo-protocol/sdk official repo and release artifacts) and confirm the WebSocket endpoint is legitimate before sending traffic or funds. - If you can't verify provenance and secret-handling, avoid installing or invoking the skill.
Review Dimensions
- Purpose & Capability
- concernThe SKILL.md is a full integration guide for the Teneo SDK (@teneo-protocol/sdk) (wallet auth, room management, micropayments), but the skill's name is 'tytyt' and there's no description or coherent registry metadata in the provided header. The _meta.json slug/owner differ from the registry owner ID in the listing, suggesting metadata mismatch or packaging errors. These inconsistencies make it unclear who published this and whether the content matches the declared purpose.
- Instruction Scope
- concernThe runtime instructions explicitly require an Ethereum private key (example: privateKey: '0x...') and show connecting to an external WebSocket (wss://backend.developer.chatroom.teneo-protocol.ai/ws) and performing payments/invites/messages. That behavior is coherent with a Teneo SDK, but the SKILL.md contains sensitive operations (wallet auth, sending paid requests) and does not limit or explain secure secret handling. The instructions do not reference unrelated files or system paths, but they do tell the agent how to use a private key directly in code, which raises secret-management concerns.
- Install Mechanism
- okThis is an instruction-only skill with no install spec and no bundled code files to execute. That reduces installation risk because nothing will be downloaded or written by the platform during install.
- Credentials
- concernAlthough the SKILL.md clearly expects an Ethereum private key (a highly sensitive secret) and payment setup, the skill declares no required environment variables or primary credential. The absence of declared secrets/credentials in the registry metadata is inconsistent with the instructions and could mask secret requirements or lead users to embed private keys directly in code. No unrelated external credentials are requested, but the missing declaration is a proportionality and transparency issue.
- Persistence & Privilege
- okThe skill does not request permanent presence (always: false) and does not declare modifications to other skills or system-wide settings. Autonomous invocation is enabled by default but is not combined here with other broad privileges in the metadata.