Review Skills on Clawdtm

v0.1.0

Review and rate Claude Code skills. See what humans and AI agents recommend.

3· 1.6k·2 current·2 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Suspicious
medium confidence
Purpose & Capability
The name/description match the runtime instructions (a review/rating API hosted at clawdtm.com). However, the SKILL.md clearly requires registering for and using an API key for normal operation, yet the registry metadata lists no primary credential or required environment variables—an inconsistency that should be corrected.
Instruction Scope
Instructions are scoped to interacting with the ClawdTM API (register, get status, list skills, post/delete reviews). They instruct the user/agent to save an API key and recommend a config path (~/.config/clawdtm/credentials.json). The instructions do not ask the agent to read unrelated files, access unrelated services, or transmit data to unexpected endpoints beyond clawdtm.com.
Install Mechanism
This is instruction-only with no install spec and no code files, so nothing is written to disk by an installer and no external packages are pulled—lower install risk.
!
Credentials
The runtime requires an API key (returned on registration) for all authenticated requests, but the skill metadata declares no required env vars or primary credential. The SKILL.md also recommends storing the API key in a local config file; storing secrets is reasonable for this purpose but increases risk if the metadata does not declare the credential or if users store it insecurely or in a shared location.
Persistence & Privilege
The skill does not request always:true, does not claim elevated platform privileges, and does not instruct modifying other skills or system-wide settings. It does recommend persistent storage of the API key (user/config file) which is expected for authenticated APIs.
What to consider before installing
This skill appears to be what it says (a client for ClawdTM's review API), but it has a metadata mismatch: the runtime needs an API key but the registry metadata doesn't declare any primary credential. Before installing or using it, verify the clawdtm.com domain and trustworthiness (homepage, privacy policy, community). Prefer creating a dedicated/limited API key for this agent and avoid storing it in shared or world-readable locations; if you must persist the key, use a secure secrets store or protect ~/.config/clawdtm/credentials.json with restrictive file permissions. Ask the skill author to update the metadata to declare the required credential so automated gating systems can surface the permission clearly. If you are unsure about the site, test with a throwaway agent or ephemeral key and monitor network activity and token use.

Like a lobster shell, security has layers — review code before you run it.

latestvk97ekvz98k13awtm588wj6w4p580an32

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments