Agent skill
Liquid Render Skill
Locally render Liquid templates using a virtual lab (Node.js engine).
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/liquid-render
SKILL.md
Capabilities
This skill allows you to "compile" Liquid logic instantly without waiting for Shopify. You can check if your logic (loops, filters, math) is correct.
It also allows you to render a snippet into an HTML file (save_preview) so you can open it with Playwright and see the result.
Dependencies
- Local MCP Server: This skill comes with a built-in Node.js server.
- Node.js: Required to run the server.
Tools Usage Guide
1. render_liquid
Render a piece of code and get the HTML string back.
- Param
template:{% if products.size > 0 %}...{% endif %} - Param
data:{ "products": [{"title": "Shirt"}] }
2. save_preview (Best for UI Testing)
Render liquid code into a real .html file that you can inspect visually.
- Param
template: The code. - Param
data: Mock data. - Param
filename: (Optional) e.g.,my_test.html.
Workflow: Virtual Lab
- Mock Data: Agent invents JSON data describing a scenario (e.g.
product_with_50_variants.json). - Render: Agent calls
save_preview. - Verify: Agent calls
playwright_navigate(url="file:///path/to/my_test.html")to see the result.
Limitations
- This uses
liquidjs(Node.js), not the official Shopify Ruby engine. - Standard filters like
| asset_urlare mocked to return strings, so CSS/Images might not load if they rely on CDN. - Use this for LOGIC testing mainly.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?