mercurjs/mercur-blocks
.claude/skills/mercur-blocks/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add mercurjs/mercur mercur-blocksInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 7, 2026, 8:37 AM4.9s1 file scanned
SKILL.md
- name:
- mercur-blocks
- description:
- 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.
- argument-hint:
- [block-name]
Mercur Blocks Workflow
Use this skill when:
- evaluating whether a block fits a project
- adding a block through Mercur CLI
- reviewing the impact of an installed block
- updating a block and checking for drift
Read first
Start with:
- project root
blocks.json - the Mercur CLI command that matches the task:
search,view,add, ordiff
blocks.json alias model
In the basic starter, aliases route block files into:
api->packages/api/srcadmin->apps/admin/srcvendor->apps/vendor/src
Always reason about a block by alias destination, not just by the block name.
Decision flow
- Search for the block if the exact name is not known.
- View the block before adding it.
- Identify which aliases and workspaces it will touch.
- Add the block.
- Inspect installed files and configuration impact.
- Run the smallest relevant verification set.
Post-install checklist
- Which aliases were used:
api,admin,vendor? - Did the block add routes, modules, links, workflows, or subscribers?
- Does
packages/api/medusa-config.tsneed module registration or options? - Did the block add API routes that require route type codegen?
- Did the block add UI routes that require admin or vendor build verification?
- Did the block include docs telling the user to configure env vars, providers, or middleware?
Useful commands
npx @mercurjs/cli@canary search --query <keyword>
npx @mercurjs/cli@canary view <block>
npx @mercurjs/cli@canary add <block>
npx @mercurjs/cli@canary diff <block>
Verification defaults
- Backend touched: run backend build and the relevant tests
- Admin touched: run admin build or lint
- Vendor touched: run vendor build or lint
- Routes or SDK types touched: run codegen and confirm generated types still make sense
Avoid
- adding a block without checking its docs or install impact first
- assuming a block only writes into one workspace
- leaving
medusa-config.tsor env setup stale after install - updating blocks blindly without checking
diff
Output expectations
When summarizing a block task:
- name the block
- list which aliases/workspaces it touched
- state any config, codegen, or verification follow-up
Related Skills
mercurjs/migration-guide
documentation
VerifiedTrustedCommunity
Analyze a Mercur 1.x project and guide migration to 2.0. Self-contained — works without access to the mercur monorepo.
1,470SKILL.mdUpdated Apr 7, 2026
mercurjs/migration-guide
documentation
VerifiedTrustedCommunity
Plan and execute migration from Mercur 1.x to 2.0. Classifies project difficulty, reads relevant migration docs, and follows stop conditions.
1,470SKILL.mdUpdated Apr 7, 2026
mercurjs/code-review
development
VerifiedTrustedCommunity
Review code changes for contract compliance, type safety, and regression risk. Use after completing any non-trivial implementation, before merging PRs, or when asked to review code quality across any mercur package.
1,470SKILL.mdUpdated Apr 7, 2026
mercurjs/mercur-cli
tools
VerifiedTrustedCommunity
Use Mercur CLI commands correctly inside a project created from the Mercur basic starter. Use when choosing between `create`, `init`, `add`, `search`, `view`, and `diff`.
1,452SKILL.mdUpdated Apr 7, 2026