Bricklink

Bricklink extends your AI assistant with the ability to brickLink Store API helper/CLI (OAuth 1.0 request signing). Covers orders, store inventory (read + write), catalog, categories, colors, feedback, and push no... Rather than leaving your conversation to handle this manually, you can ask your Claude agent directly — and it will take care of the task end-to-end, using Bricklink as its underlying capability.

Bricklink works across Claude, Cursor, OpenClaw through the Model Context Protocol (MCP) — an open standard that lets AI clients share tools and skills without lock-in. Because MCP is platform-agnostic by design, you install Bricklink once and it becomes available across all your AI clients. Whether you're working in Claude for focused sessions or Cursor for integrated workflows, the skill behaves consistently.

To install Bricklink, copy the skill folder to `~/.claude/skills/bricklink/` for use across all your projects, or `.claude/skills/bricklink/` for a single project. Restart Claude and the skill is immediately active — invoke it with `/bricklink` or just describe your goal and the AI will pick it up automatically.

Bricklink has been installed 2,406 times, making it one of the more actively used skills in the Developer & DevOps category. The install rate suggests it solves a real, recurring need rather than a niche edge case. The source code is open on GitHub — you can inspect it, contribute fixes, or fork it to adapt the skill for your specific setup. Like all skills on DiscoverAISkills, it is free to install and use. The broader AI skills ecosystem continues to expand as developers contribute new capabilities across categories like developer tools, data analysis, writing, automation, and more.