Deside Messaging
Analysis
This is a coherent instruction-only Deside messaging skill, but using it gives an agent authenticated wallet-based access to read and send DMs through Deside.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.
Canonical Tools For This Skill ... `send_dm` ... `read_dms` ... `mark_dm_read` ... `list_conversations`
The documented tools include message-sending and read-acknowledgement actions that can change communication state. These actions match the skill purpose, but should be user-directed.
Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.
Deside MCP uses both: ... an OAuth bearer token obtained through OAuth 2.0 + PKCE ... sign the wallet challenge with the Solana wallet ... Use scopes intentionally: `dm:read` ... `dm:write`
The skill requires authenticated wallet authority and OAuth scopes that allow reading and sending DMs. This is expected for the integration, but it is sensitive account access.
Checks for exposed credentials, poisoned memory or context, unclear communication boundaries, or sensitive data that could leave the user's control.
Canonical MCP endpoint: `https://mcp.deside.io/mcp` ... read conversation history ... receive incoming realtime updates through `notifications/dm_received`
DM contents, message history, and notifications are handled through an external MCP provider. This is disclosed and central to the skill, but users should understand the data boundary.
