Synth Data

PassAudited by ClawScan on May 1, 2026.

Overview

This skill appears to do what it says: it uses a Synthdata API key to fetch market volatility data, with only optional user-directed scheduling examples.

Before installing, confirm you are comfortable giving the skill access to a Synthdata API key. Treat its trading and volatility outputs as informational, and only set up Slack, Telegram, cron, or alert integrations if you want ongoing automated messages.

Findings (2)

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.

What this means

Installing and using the skill means the agent can use your Synthdata API key for market-data queries and consume any associated quota or account access.

Why it was flagged

The script reads the user's Synthdata API key from the environment and sends it to Synthdata for authentication, which matches the skill's stated purpose.

Skill content
API_KEY = os.environ.get("SYNTHDATA_API_KEY", "") ... "Authorization": f"Apikey {API_KEY}"
Recommendation

Use a dedicated, revocable Synthdata API key if possible, and avoid sharing the key in prompts, logs, or screenshots.

What this means

If you create the suggested scheduled reports, volatility data may continue to be sent to team or messaging channels until you disable the schedule.

Why it was flagged

The documentation describes optional scheduled reporting, which could keep running and posting messages if the user sets it up.

Skill content
Create a cron job for daily Slack/Telegram forecasts (see examples/use-cases.md).
Recommendation

Only enable scheduled reports deliberately, review the destination channel or webhook, and document how to disable the cron job or alert.