Economic Calendar Pro
AdvisoryAudited by Static analysis on Apr 30, 2026.
Overview
No suspicious patterns detected.
Findings (0)
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.
Using the skill runs code from the installed skill directory on the local machine.
The skill's intended workflow is to execute a local Python script via uv. This is expected for the stated purpose, but it is still local code execution.
uv run /root/.openclaw/workspace/skills/economic-calendar-pro/src/main.py <START_DATE> <END_DATE>
Install only if you trust the supplied files, and invoke it with the documented date arguments.
A TradingEconomics credential in the environment or a nearby .env file may be used for API access; unrelated .env values may also be loaded into the process environment.
The code can load values from local .env files and then use TRADING_ECONOMICS_API_KEY if present. This is disclosed and purpose-aligned, but it touches local credential configuration.
for base in (Path.cwd(), repo_root()): ... candidate.read_text(encoding="utf-8").splitlines() ... os.environ.setdefault(key, value) ... api_key = os.environ.get(API_KEY_ENV_VAR, "").strip()
Prefer a dedicated TradingEconomics key and avoid running from directories whose .env files contain unrelated sensitive secrets.
The requested date range, and the TradingEconomics API credential when used, are sent to the relevant external provider.
The skill sends requests to external calendar providers. These endpoints are disclosed and aligned with the skill purpose.
API_BASE_URL = "https://api.tradingeconomics.com" ... YAHOO_CALENDAR_API_URL = "https://query1.finance.yahoo.com/ws/screeners/v1/finance/calendar-events"
Use the skill only if you are comfortable with those providers receiving the calendar request and, for TradingEconomics, the configured API credential.