bricklink

bricklink provides a command line helper over the bricklink store api for orders, inventory, catalog lookups, pricing, feedback, and push notifications, handling the oauth 1.0 request signing that makes these calls awkward by hand. The friction is provisioning. Four separate values are required, a consumer key and secret plus a token value and secret, and the signing depends on python being present. Read paths cover order and feedback retrieval, while inventory write access means mistakes can alter a live store, so the separate setup document is worth reading first.

Use case: checking new orders without the web interface

This skill wraps a marketplace for a construction toy, covering orders, store inventory, the catalogue of parts and colours, feedback and notifications. The notable part is the signing scheme: every request is authorised with a four part key rather than a single token. ## What it does - Lists orders in either direction with status filters. - Reads order details, line items, messages and feedback. - Reads and writes store inventory lots. - Reads catalogue categories and colours. - Lists unread notifications. ## When it is the wrong choice The four part credential is the main obstacle. A consumer key and secret plus a token and token secret all have to be present, and the signing scheme includes a timestamp, so a request built once and replayed later is refused. That makes it a poor fit for a cached script that assumes one static token. Setup also lives in a separate document rather than in the skill text itself, so a first run without reading it stalls on missing values. Inventory operations are not read only, which means a mistake changes what a store is selling, and notifications are polled rather than pushed, so an unread list only reflects the last call. The catalogue reads are the safe half of the tool and the inventory half is where the risk sits, which matters when the skill is handed to an agent without supervision. ```bash python3 scripts/bricklink.py get-orders python3 scripts/bricklink.py get-categories ``` ## Working notes - Two keys and two secrets are all required for signing. - Notifications are fetched rather than delivered. - Inventory writes change what the store offers.