mercur-cli

Manage Mercur projects with command-line tools for creation, search, and diffing.

Updated May 2, 2026
One-click install
npx skills add https://github.com/nathangalea/plants-direct --skill mercur-cli-nathangalea
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mercur-cli
Source: https://github.com/nathangalea/plants-direct/tree/main/.claude/skills/mercur-cli
Command: npx skills add https://github.com/nathangalea/plants-direct --skill mercur-cli-nathangalea

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill simplifies managing Mercur projects by providing command-line tools for creation, initialization, searching, viewing, adding, and diffing blocks.

Core Features & Use Cases

  • Project setup and management: Easily create new projects or initialize configuration files such as blocks.json.
  • Registry exploration: Search and review available blocks before installation.
  • Component integration: Install blocks and validate their integration with existing project files.
  • Comparison and update: Check for differences between local blocks and registry versions to maintain up-to-date components.
  • Use Case: A developer wants to add a new feature block to their project; they will search, view details, and incorporate the block seamlessly.

Quick Start

Use the mercur-cli skill to initialize your project by creating blocks.json and then search for available blocks in your registry.

Frequently Asked Questions about mercur-cli

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage Mercur project blocks from the command line?

You can manage Mercur project blocks from the command line by using CLI tools to create projects, initialize configuration files, search available blocks, and install components directly within your project directory.

How do I set up a new Mercur project and initialize blocks.json?

To set up a new Mercur project, use the CLI to create the project structure and generate the blocks.json configuration file, streamlining the initialization process for your development workflow and registry environment.

Can I compare local Mercur blocks with registry versions to check for updates?

Yes, you can compare local Mercur blocks with registry versions by running diff commands, which detect differences between your installed components and the registry to help maintain up-to-date project files.

What is the best way to search for and review available components before installation?

The best way to search for available components is using the CLI registry exploration commands, which let you query and view block details to validate integration before installing them into your project.

Do I need a registry environment configured to install Mercur blocks?

Yes, a registry environment is required to search, review, and install Mercur blocks, as the CLI relies on it to fetch components and validate their integration with your existing project files.

Why should I use a command line tool for Mercur block management instead of manual file edits?

Using a command line tool for Mercur block management automates project setup, block installation, and change detection, preventing manual configuration errors and streamlining your software development workflow.