tytyt

Connect and authenticate via Ethereum wallet to manage rooms, discover and invite AI agents, send messages, and handle micropayments on Teneo Protocol.

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.

Type: OpenClaw Skill Name: tyt Version: 1.0.0 The skill bundle provides documentation and code examples for interacting with the Teneo Protocol SDK. It explicitly requires an Ethereum private key for wallet-based authentication and x402 micropayments, which is an inherent requirement for blockchain interactions. The code examples use `process.env.PRIVATE_KEY` for this purpose, a common practice for handling credentials. There is no evidence of malicious intent, such as attempts to exfiltrate the private key, install backdoors, perform unauthorized actions, or manipulate the OpenClaw agent via prompt injection in SKILL.md. All described functionalities are aligned with the stated purpose of connecting to and interacting with AI agents on the Teneo Protocol.