Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Discord History Reader
v1.0.0Read Discord channel and thread message history directly via the Discord Bot API, bypassing OpenClaw's session-based message visibility. Use when you need to...
⭐ 0· 384·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
high confidencePurpose & Capability
The skill's name, description, and runtime instructions align: a Discord bot token is logically required to read channel/thread history via the Discord API. However, the registry metadata declares no required credentials or primaryEnv even though the SKILL.md explicitly requires storing and reading a bot token from disk. That mismatch is noteworthy.
Instruction Scope
SKILL.md instructs the user to create a token file (~/.openclaw/.discord-bot-token), set permissions, and have the agent read that file and call Discord endpoints via curl. The instructions are narrowly scoped to calling Discord API endpoints, but they intentionally bypass OpenClaw's redaction mechanism by placing the token in a file accessible to the agent — this grants the agent broader and persistent access than a simple transient session and could be used for actions beyond read-only calls (the doc even notes the token has read/write scope).
Install Mechanism
This is an instruction-only skill with no install spec and no code files. That minimizes filesystem changes and direct supply-chain risks.
Credentials
The skill requires a Discord bot token (a high-privilege secret) but does not declare any required env vars or primary credential in the registry metadata. The recommended storage method (a file the agent can read) increases the token's exposure. While the token is necessary to perform the stated task, requesting it be stored in a file accessible to the agent is disproportionate compared with safer alternatives (e.g., platform secret storage, scoped read-only token, or an audited proxy).
Persistence & Privilege
The skill does not set always:true, but SKILL.md tells users to record the token file path in TOOLS.md so the agent can find it across sessions — effectively creating persistent, cross-session access. Combined with default autonomous invocation, that persistence increases the blast radius if the token is compromised or misused.
What to consider before installing
This skill will work as documented, but it asks you to create a file containing your Discord bot token that the agent can read — effectively giving any agent-run code that can access that file the same privileges as the bot (including sending messages if the token allows it). Before installing or using this skill, consider: 1) Use a dedicated bot with the minimal scopes (ideally only View Channel + Read Message History) and limit the bot to the specific guilds/channels required; 2) Prefer secure secret storage or OpenClaw-native credential mechanisms rather than a plaintext token file; 3) If you must use a file, restrict filesystem access tightly, keep it out of backups/git, and rotate the token frequently; 4) Remember agents can invoke skills autonomously by default — avoid recording the token path in globally-readable tool lists unless you trust all agents and users; 5) If you lack confidence about safe token handling, do not install — instead create a read-only proxy or ask platform maintainers for a vetted integration.Like a lobster shell, security has layers — review code before you run it.
latestvk976gpaxka3pn06abqkknwjs6x82ypp4
License
MIT-0
Free to use, modify, and redistribute. No attribution required.