Skillv1.0.3

ClawScan security

Macro-Driver-Pro: 宏观晴雨表 · ClawHub's context-aware review of the artifact, metadata, and declared behavior.

BenignMar 10, 2026, 1:21 AM

Verdict: benign
Confidence: medium
Model: gpt-5-mini
Summary: The skill's requests and instructions are internally consistent with its stated purpose (fetching DXY and US10Y via a Vercel backend), but it forwards data to an external API and uses an external micro-billing flow (SkillPay) that you should review before use.
Guidance: This skill is coherent for fetching DXY and US10Y via an external API, but it will send requests (including a user_id) to macro-driver-pro.vercel.app and use SkillPay for micro-billing. Before installing: (1) confirm you trust the external endpoint and review the project's GitHub source if you can; (2) ask the developer or platform how SkillPay billing is authorized and billed to avoid unexpected charges; (3) avoid sending any secrets or sensitive data in requests (only send the minimal user_id); (4) test with a low-volume call to observe behavior and logs; (5) verify privacy/logging and retention policies if you plan to send production data.

Purpose & Capability: okName/description promise real-time DXY and US10Y data. The manifest and SKILL.md point to a Vercel backend (macro-driver-pro.vercel.app) that uses yfinance for Yahoo Finance data — this aligns with the stated purpose.
Instruction Scope: noteSKILL.md instructs callers to use the backend endpoint and to include a user_id for SkillPay micro-billing. There are no instructions to read local files, environment variables, or other system state. However, runtime traffic (queries and the user_id) will be sent to the external service; the doc does not specify data retention, logging, or exact billing mechanics.
Install Mechanism: okThis is an instruction-only skill with no install spec and no code files to write to disk, so there is no installation risk introduced by the skill itself.
Credentials: okThe skill declares no required environment variables or credentials. It does rely on an external SkillPay billing flow (requiring a user_id param) but does not request unrelated secrets. The lack of declared payment credential requirements is plausible if billing is handled by the platform, but it would be helpful to clarify how SkillPay authenticates and charges users.
Persistence & Privilege: okalways is false and the skill does not request persistent system-level privileges or modify other skills. It is not force-included and operates via external API calls only.