Enonic Guillotine Query Builder

This one helps you write and debug GraphQL queries for Enonic XP's Guillotine headless API. It scans your workspace for existing queries, builds DSL queries with proper filtering and pagination, handles content type fragments with the right underscore naming convention, and can generate TypeScript types from your schema. The skill knows the differences between Guillotine 5.x string queries and the modern 6.x+ DSL, which matters if you're maintaining older projects. It's opinionated about using connection variants when you need aggregations or highlighting, and it won't help with server-side lib-content queries or Apollo clients. Useful if you're tired of debugging null fragments or wrestling with QueryDSLInput nesting.

skills.sh installs: 483
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add webmaxru/enonic-agent-skills --skill enonic-guillotine-query-builder --agent claude-code

Installs into .claude/skills of the current project.

Files

Enonic Guillotine Query Builder

Procedures

Step 1: Scan the workspace for existing Guillotine usage

Execute node scripts/find-guillotine-targets.mjs . to inventory files containing Guillotine markers (query strings, library imports, endpoint references).
If a Node runtime is unavailable, search the workspace manually for guillotine, queryDsl, queryDslConnection, or /lib/guillotine in .ts, .js, .graphql, and .gql files.
Note the Guillotine version in use: if query(query: "...") string-based fields are found, the project uses the deprecated 5.x-style API; if queryDsl / queryDslConnection are found, the project uses 6.x+ DSL. Check for exports.extensions in guillotine/guillotine.js to detect Guillotine 7 Extensions API usage.
If both styles coexist, flag the deprecated usage for migration.

Step 2: Load the Guillotine API reference

Read references/guillotine-reference.md before composing any query.
Read references/compatibility.md when the workspace targets or migrates between Guillotine versions.

SKILL.md on GitHub