AFOL BrickEconomy
PassAudited by ClawScan on May 10, 2026.
Overview
This appears to be a read-only BrickEconomy API helper, but it uses an API key and can retrieve private collection and sales-ledger data.
This skill is reasonable to install if you want BrickEconomy valuation and portfolio analysis and are comfortable providing a BrickEconomy API key. Be aware that collection and sales-ledger commands may return private financial/account details; ask for scoped summaries when appropriate, keep the API key out of transcripts, and do not point the base URL at an untrusted server.
Findings (3)
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.
If installed and configured with an API key, the agent can retrieve private BrickEconomy collection values, paid prices, sale records, fees, dates, and notes when asked.
The skill requires a BrickEconomy API key and can access authenticated personal collection and sales-ledger data. This is purpose-aligned and disclosed, but it is sensitive account/financial information.
Required environment variable: export BRICKECONOMY_API_KEY=... ... Treat returned collection and sales-ledger data as private financial/account data.
Only configure the API key if you are comfortable sharing BrickEconomy account data with the agent, and ask for summaries or scoped analysis when you do not want full details returned.
An agent that over-trusts this reference could try to use unavailable or external pricing tools instead of the included BrickEconomy CLI.
This reference prompt gives broader tool-use instructions involving a separate LegoTools/BrickLink fallback that is not implemented by the included CLI and is narrower in SKILL.md, which says not to use other providers unless the user explicitly asks.
ALWAYS use bd_get_price for price inquiries about specific items ... Automatic fallback: Tries BrickEconomy first → Falls back to BrickLink if unavailable
Treat SKILL.md as authoritative: use the included CLI for BrickEconomy queries, and only use BrickLink or other fallback providers when the user explicitly requests multi-provider lookup.
The documented command may fail unless the user invokes the Python script directly or adds a wrapper.
The file manifest provides scripts/brickeconomy_cli.py but not a scripts/brickeconomy wrapper, and there is no install spec that creates one. This looks like a packaging/documentation mismatch rather than hidden code.
Primary interface: `scripts/brickeconomy`.
Verify the actual command path before use, for example by running the provided Python file directly if no scripts/brickeconomy wrapper exists.