liquid

Enforce standardized Liquid coding conventions for Jekyll templates.

1|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/hschne/pi-stuff --skill liquid
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: liquid
Source: https://github.com/hschne/pi-stuff/tree/main/skills/liquid
Command: npx skills add https://github.com/hschne/pi-stuff --skill liquid

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Writing inconsistent, unoptimized Liquid templates for Jekyll sites leads to rendering errors, stray whitespace in output, and hard-to-maintain code that breaks when site structure changes.

Core Features & Use Cases

  • Standardized Conventions: Enforces consistent whitespace control, snake_case variable naming, and explicit include parameter passing to reduce template bugs.
  • Jekyll-Specific Best Practices: Provides clear rules for using Jekyll objects, filters, and tags to avoid common pitfalls like implicit scope leaking and stale loop variables.
  • Use Case: When building a multi-page Jekyll portfolio, use this skill to standardize layout and include templates across the site, eliminating fragile code and ensuring consistent rendered output.

Quick Start

Use the liquid skill to write a new Jekyll include template that displays post metadata with properly documented parameters and whitespace control.

Frequently Asked Questions about liquid

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

FAQPage Schema
How do I fix stray whitespace in Jekyll Liquid templates?

Stray whitespace in Jekyll Liquid templates is fixed by enforcing standardized whitespace control conventions. Applying explicit hyphen syntax in tags ensures consistent rendered output without unexpected blank lines.

What is the best way to pass variables to Jekyll includes?

The best way to pass variables to Jekyll includes is through explicit parameter passing. This prevents implicit scope leaking and ensures the include receives the correct data without relying on global variables.

How do I write clean Liquid templates for static sites?

Writing clean Liquid templates for static sites requires using idiomatic syntax, snake_case variable naming, and explicit variable scoping. This eliminates fragile code and ensures maintainable template structure aligned with Jekyll best practices.

Does this Liquid skill work with Jekyll collection templates?

Yes, this Liquid skill works with Jekyll collection templates, applying standardized coding conventions to eliminate error-prone development. It supports creating and editing layouts, includes, and pages using Jekyll-specific objects.

Why do my Jekyll layouts break when the site structure changes?

Jekyll layouts break during site structure changes due to inconsistent variable scoping and implicit scope leaking. Enforcing explicit include parameter passing and standardized conventions prevents these rendering errors and hard-to-maintain code.