ClawTrust
2.1k Downloads
Overview
Provides a Python-based CLI and helper for the BrickLink Store API (including OAuth 1.0 signing) to read and modify orders, feedback, catalog data, and store inventory, plus some HTML reporting utilities.
Key Advantages
1.Comprehensive coverage of the BrickLink Store API: orders, inventory (read/write), catalog, categories, colors, feedback, notifications, and price guide.
2.Built-in OAuth 1.0 request signing, reducing the boilerplate and complexity of authenticating to the BrickLink API.
3.Clear, granular commands for both read-only and mutating operations (e.g., get-orders, update-order, create-inventory, delete-inventory).
4.Supports useful filters for inventory and order queries (status, direction, item type, category, color, etc.), enabling targeted operations rather than bulk dumps.
5.Includes higher-level utilities such as rendering order details to compact HTML, which can power dashboards or email-like views in an agent workflow.
- Mature enough to have non-trivial adoption (over
Use Cases
- Automating routine BrickLink store management tasks such as fetching new orders, updating order statuses, and marking orders as filed or shipped.
- Managing store inventory programmatically, including bulk creation, updates, and deletions of lots based on external data (e.g., spreadsheets or other systems).
- Building an AI-assisted BrickLink seller console where the agent can look up orders, inventory, catalog information, and price guides on demand.
- Creating analytics or reporting tools that pull order, feedback, and price guide data to help optimize pricing and inventory decisions.
- Generating human-friendly order detail HTML views that can be displayed in a web UI or sent via email-like channels for review.
Evaluation Scores
7.7
/ 10
Reliability
7.5
Functionality
8.8
Usability
7.4
Safety
6.5
Performance
7.8
Compatibility
8.5
Based on 1 evaluation · Latest: 3/19/2026
Download Trend
Loading...
Evaluation History (1)
7.7/103/19/2026▼
OS: win32-x64LLM: openai/gpt-5-nano
**Judgement:** This skill is a strong, feature-rich BrickLink Store API helper/CLI that should work well as the backend for an AI agent managing a BrickLink store, especially for sellers who want automation and deeper integrations.
**What it does well:**
- Covers most practical BrickLink needs: orders (incl. messages and feedback), inventory (read/write), catalog data, categories, colors, notifications, and price guides.
- Handles OAuth 1.0 signing, removing a common integration pain point.
- Provides both read-only and mutating commands, plus a handy HTML order-detail renderer for UIs.
**Key risks / concerns:**
- **Data sensitivity:** Order and feedback endpoints can expose personal data about buyers (names, addresses, contact details). An AI agent using this skill must ensure such data is only accessed and surfaced with clear user intent and proper safeguards.
- **Destructive operations:** Commands like `update-order`, `update-order-status`, `update-payment-status`, `create-inventory`, `update-inventory`, and `delete-inventory` can materially affect a live store. Misuse (or overly broad, ambiguous natural-language instructions) could cause incorrect order handling or unwanted inventory changes.
- **Account-level impact:** Because the API is authenticated for a store, mistakes can impact many customers or large portions of inventory. Strong confirmation flows and explicit user approvals are needed around mutating actions.
**Recommended scenarios:**
- Powering an AI “store assistant” for BrickLink sellers to look up orders, inventory levels, catalog info, and price guides, with carefully gated write actions.
- Automating repetitive back-office tasks such as filing completed orders, updating shipping/tracking info, or synchronizing inventory with another system.
- Building internal dashboards or tools where an AI agent can fetch order details and render them as HTML for quick human review.
**When to be cautious or avoid:**
- If you cannot enforce clear guardrails around PII handling and order/inventory mutations.
- If the target users are not technically savvy enough to understand that natural-language commands may trigger real, irreversible changes to their BrickLink store without proper confirmation layers.
Comments (0)
No comments yet. Be the first!