Ultimate Flashcards and Podcast Tutor
PassAudited by ClawScan on May 1, 2026.
Overview
The skill is coherent for EchoDecks study workflows, but it requires an API key and can send study content to EchoDecks while performing account-changing or credit-using actions.
This appears safe to install if you trust EchoDecks and the skill publisher. Before use, confirm you are comfortable providing an EchoDecks API key, sending study text to the service, and allowing the agent to perform actions that create content, update reviews, or spend EchoDecks credits.
Findings (4)
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.
Anyone using this skill must trust it with their EchoDecks API key and the account permissions that key provides.
The client authenticates every API request with the user's ECHODECKS_API_KEY, giving the skill delegated access to the user's EchoDecks account.
"X-API-KEY": get_api_key()
Use a scoped or revocable EchoDecks key if available, and revoke or rotate the key if you stop using the skill.
If invoked, the agent can spend EchoDecks credits and create new study or podcast content in the user's account.
The skill exposes actions that generate content and consume EchoDecks credits; this is disclosed and purpose-aligned, but still affects the user's account balance.
echodecks_generate_cards ... Cost: 10 credits ... echodecks_generate_podcast ... Cost: 50 credits
Confirm expensive generation requests before letting the agent create cards or podcasts, especially for broad prompts.
Text you provide for flashcard generation may be transmitted to EchoDecks for processing.
Raw text supplied for card generation is posted to the remote EchoDecks API, so private study material may leave the local agent environment.
if args.text:
data["text"] = args.text
return make_request("POST", "generate", action="cards", data=data)Avoid sending confidential, regulated, or highly sensitive material unless you trust EchoDecks' handling of that data.
The install listing may not fully communicate the credential requirement or provenance before a user reads the artifacts.
The registry metadata does not identify a source/homepage or declare the API-key requirement, although the included SKILL.md and README.md do disclose ECHODECKS_API_KEY.
Source: unknown; Homepage: none; Required env vars: none; Env var declarations: none
Verify that the publisher and EchoDecks API endpoint are trustworthy before adding an API key.
