mercur-blocks

Validate Mercur blocks for safe inclusion using blocks.json aliases and the Mercur CLI.

Updated Apr 3, 2026

Search Tags:#workflow #cli #verification #blocks #mercur #blocks.json

Ready to run

npx skills add https://github.com/OZVE/cuarta-avenida --skill mercur-blocks

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: mercur-blocks
Source: https://github.com/OZVE/cuarta-avenida/tree/main/.claude/skills/mercur-blocks
Command: npx skills add https://github.com/OZVE/cuarta-avenida --skill mercur-blocks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Discover, evaluate, install, and verify Mercur blocks safely using blocks.json aliases and Mercur CLI workflows. Use when adding or updating blocks in a Mercur project to minimize drift and misconfigurations.

Core Features & Use Cases

Discover and evaluate blocks using blocks.json aliases to understand where they fit in the project.
Install and verify blocks via the Mercur CLI, ensuring correct integration with target workspaces and configurations.
Use cases include adding new blocks to extend marketplace functionality or updating existing blocks while preserving compatibility.

Quick Start

Install and verify a Mercur block by using the CLI to search for the block, view its details, and run a diff to confirm changes.

Frequently Asked Questions about mercur-blocks

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

FAQPage Schema

How do I verify Mercur blocks before installing them in a project?▼

To verify Mercur blocks before installing, you can use the Mercur CLI to search for the block, view its details, and run a diff. This workflow surfaces the install impact and evaluates compatibility using blocks.json aliases.

How do I check for drift when updating existing Mercur blocks?▼

Checking for drift when updating Mercur blocks involves using the Mercur CLI to run drift checks against your current configuration. This process parses alias destinations from blocks.json to identify and prevent misconfigurations during updates.

What is the best way to safely add new blocks to a Mercur project?▼

The best way to safely add new blocks to a Mercur project is by evaluating them through blocks.json aliases and using the Mercur CLI. This structured workflow ensures correct integration with target workspaces and verifies compatibility before installation.

Can I use the Mercur CLI to evaluate block compatibility without causing configuration drift?▼

Yes, you can use the Mercur CLI to evaluate block compatibility without causing drift. The workflow specifies requirements to parse alias destinations, verify compatibility, and surface install impact through structured evaluation results before applying changes.

Do I need a blocks.json file to manage Mercur block installations?▼

Yes, a blocks.json file is required to manage Mercur block installations. The workflow relies on blocks.json aliases to discover, evaluate, and verify blocks, ensuring they fit correctly within your project and target workspaces.

Why does installing a Mercur block cause workspace misconfigurations?▼

Installing a Mercur block causes workspace misconfigurations when you skip the verification workflow. To prevent this, use the Mercur CLI to run a diff and confirm changes, ensuring the block integrates correctly with your target workspaces.