Back to skill
Skillv0.1.0
ClawScan security
Authenticate · ClawHub's context-aware review of the artifact, metadata, and declared behavior.
Scanner verdict
BenignMar 9, 2026, 4:47 AM
- Verdict
- benign
- Confidence
- high
- Model
- gpt-5-mini
- Summary
- The skill's instructions and footprint match its stated purpose (help a human run the fdx CLI to authenticate a wallet); nothing requested is disproportionate or unrelated, though the SKILL.md documents environment variables that the registry metadata did not declare.
- Guidance
- This skill is coherent for its stated purpose: it simply guides a human to run the `fdx` CLI to perform OAuth and manage tokens stored at ~/.fdx/auth.json. Before installing or using it, verify that the `fdx` CLI is present and comes from a trusted source, and confirm the MCP server URL (default https://mcp.fd.xyz) is correct for your deployment. Be cautious running this on multi-user or untrusted machines because the token file contains credentials; prefer the device flow on headless/remote hosts. Also note the SKILL.md advertises environment variables but the registry metadata doesn't declare them — harmless but worth correcting by the skill author for clarity.
Review Dimensions
- Purpose & Capability
- noteThe skill is an instruction-only helper for authenticating the Finance District wallet via the local `fdx` CLI. All required actions described (fdx setup, status, logout) align with the stated purpose. Note: SKILL.md documents FDX-related environment variables (FDX_MCP_SERVER, FDX_REDIRECT_URI, FDX_STORE_PATH) but the registry metadata lists no required env vars — a minor metadata omission, not a functional mismatch.
- Instruction Scope
- okInstructions are narrow and scoped to running `fdx status`, `fdx setup` (browser or device OAuth flows), and `fdx logout`. They instruct the human to complete browser/device authorization. The skill references the local token store (~/.fdx/auth.json) and a local callback server (port 6260), which are expected parts of an OAuth flow.
- Install Mechanism
- okNo install spec or code files — this is instruction-only. That minimizes risk because nothing is written or executed beyond invoking the existing `fdx` CLI on the host.
- Credentials
- noteThe skill does not request secrets or credentials in metadata. The SKILL.md lists non-secret environment variables (MCP server URL, redirect URI, token store path) which are reasonable for configuration. However the metadata does not declare these env vars as required; also be aware that `fdx status` / `fdx setup` will read/write the local token store (e.g. ~/.fdx/auth.json) containing tokens.
- Persistence & Privilege
- okalways is false and the skill is user-invocable; it does not request permanent presence or modify other skills/system settings. Autonomous invocation remains enabled by default but that is normal and not raised here because the skill's actions are limited to guiding human-driven OAuth via the `fdx` CLI.