MCPInstall

enonic-guillotine-query-builder

by webmaxruBackend & APIs

Composes, debugs, and optimizes Guillotine GraphQL queries for Enonic XP headless content delivery. Covers query construction, variable usage, filtering, aggregation, pagination, sorting, and TypeScript type generation from the auto-generated Guillotine schema. Use when writing or troubleshooting Guillotine queries, querying custom content types through GraphQL, or generating typed interfaces from Guillotine responses. Don't use for content type XML definitions, non-Enonic GraphQL APIs (Apollo, Hasura), server-side lib-content queries, or Guillotine deployment and CORS configuration.

Installs
458
Last 24h
—
Trending rank
—
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/webmaxru/enonic-agent-skills --skill enonic-guillotine-query-builder
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads enonic-guillotine-query-builder automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

Enonic Guillotine Query Builder

Procedures

Step 1: Scan the workspace for existing Guillotine usage

  1. Execute node scripts/find-guillotine-targets.mjs . to inventory files containing Guillotine markers (query strings, library imports, endpoint references).
  2. If a Node runtime is unavailable, search the workspace manually for guillotine, queryDsl, queryDslConnection, or /lib/guillotine in .ts, .js, .graphql, and .gql files.
  3. 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.
  4. If both styles coexist, flag the deprecated usage for migration.

Step 2: Load the Guillotine API reference

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

Step 3: Determine the query shape

  1. Identify the operation the user needs:
    • Single content fetch: Use get(key).
    • Direct children: Use getChildren(key) or getChildrenConnection(key) for pagination.
    • Filtered search: Use queryDsl(query) for a flat list or queryDslConnection(query) for pagination, aggregations, or highlighting.
    • Content type metadata: Use getType(name) or getTypes.
  2. If pagination is needed, prefer connection variants (queryDslConnection, getChildrenConnection) and guide the caller to pass after / first.
  3. If aggregations or highlighting are needed, require queryDslConnection — these features are not available on queryDsl.

Step 4: Construct the content type fragment

  1. Derive the GraphQL type name from the content type descriptor by replacing dots (.) and colons (:) with underscores (_), and removing hyphens (-) while capitalizing the following letter. The first letter of each segment after a colon is capitalized. Example: com.enonic.app.myapp:BlogPost → com_enonic_app_myapp_BlogPost. For built-in types: portal:template-folder → portal_TemplateFolder.
  2. Use an inline fragment to access the type-specific data field: ... on <GraphQLTypeName> { data { ... } }.
  3. For content references (ContentSelector, ImageSelector, MediaSelector), follow the reference with a nested inline fragment on the target type.
  4. For RichText / HtmlArea fields, include processedHtml and optionally links, images, macros sub-fields. Use the processHtml input argument for absolute URLs, srcset widths (imageWidths), or responsive sizes (imageSizes).

Step 5: Build query filters and sorting

  1. Use Query DSL input types. Each QueryDSLInput must contain exactly one expression field.
  2. Combine multiple conditions using boolean with must, should, mustNot, and filter arrays.
  3. For date or numeric ranges, use the range expression with gt/gte/lt/lte and the correct DSLExpressionValueInput type (localDate, localDateTime, instant, long, double).
  4. For sorting, use SortDslInput with field and direction (ASC / DESC).
  5. Read references/examples.md when the query pattern matches a documented example.

Step 6: Add aggregations and highlighting (if needed)

  1. Pass aggregations as an array of AggregationInput objects on queryDslConnection.
  2. Each aggregation requires a unique name and exactly one aggregation type field (terms, dateRange, stats, etc.).
  3. For highlighting, pass highlight with a properties array specifying propertyName for each field to highlight.
  4. Read aggregation and highlight results from aggregationsAsJson and highlightAsJson on the connection result.

Step 7: Generate TypeScript types (if requested)

  1. Read assets/guillotine-query.template.ts as the starting template.
  2. Replace __APP_KEY__, __CONTENT_TYPE__, __GRAPHQL_TYPE__, and __FIELDS__ placeholders with the actual content type values.
  3. Add typed fields to the Data interface matching the content type schema fields requested in the query.
  4. For connection queries, use the ContentConnection<T> generic with the specific content type.

Step 8: Set site context (if applicable)

  1. If the query targets a specific site, set siteKey on the guillotine field or instruct the caller to set the X-Guillotine-SiteKey HTTP header.
  2. Use ${site} placeholder in path arguments for site-relative queries.
  3. Use _path(type: siteRelative) to return site-relative paths.

Step 9: Validate the query

  1. Verify all inline fragment type names use underscores, not the original descriptor format.
  2. Confirm queryDsl / queryDslConnection are used instead of the deprecated query / queryConnection.
  3. Ensure QueryDSLInput objects contain exactly one expression field.
  4. Verify DSLExpressionValueInput objects contain exactly one value type field.
  5. Check that aggregation and highlight are only used on connection variants.
  6. For Guillotine 7+ projects, verify pageUrl / mediaUrl / imageUrl / attachmentUrl use Json type for params argument, not String.
  7. Read references/troubleshooting.md if the query returns unexpected nulls, empty results, or type errors.

Error Handling

  • If get returns null, verify the key is a valid content path or ID and that the correct branch (draft vs master) is targeted.
  • If inline fragment fields are null, confirm the GraphQL type name uses underscores and matches the content type descriptor exactly.
  • If queryDsl returns empty results, simplify to matchAll: {} to confirm data exists, then re-add filters one at a time.
  • If aggregation or highlight results are null, verify the query uses queryDslConnection, not queryDsl.
  • If the deprecated query field is used, read references/compatibility.md to migrate to queryDsl with DSL syntax.
  • If scripts/find-guillotine-targets.mjs cannot run, scan the workspace manually for Guillotine markers and continue.

FAQ

What does the enonic-guillotine-query-builder skill do?

Composes, debugs, and optimizes Guillotine GraphQL queries for Enonic XP headless content delivery. Covers query construction, variable usage, filtering, aggregation, pagination, sorting, and TypeScript type generation from the auto-generated Guillotine schema. Use when writing or troubleshooting Guillotine queries, querying custom content types through GraphQL, or generating typed interfaces from Guillotine responses. Don't use for content type XML definitions, non-Enonic GraphQL APIs (Apollo, Hasura), server-side lib-content queries, or Guillotine deployment and CORS configuration.

How do I install enonic-guillotine-query-builder?

Run npx skills add https://github.com/webmaxru/enonic-agent-skills --skill enonic-guillotine-query-builder in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/enonic-guillotine-query-builder/ (personal) or .claude/skills/enonic-guillotine-query-builder/ (project).

Which AI agents can use enonic-guillotine-query-builder?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is enonic-guillotine-query-builder safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains enonic-guillotine-query-builder?

It is published by webmaxru in webmaxru/enonic-agent-skills. It has 458 recorded installs.

More from webmaxru/enonic-agent-skills

View all →

enonic-nextxp-integration

webmaxru/enonic-agent-skills

Guides setup, development, and troubleshooting of the Next.js and Enonic XP headless integration (Next.XP framework). Covers Enonic adapter configuration, content type to React component mapping, Guillotine GraphQL data fetching, Content Studio preview mode, and draft/master branch switching. Use when building a Next.js frontend powered by Enonic XP, configuring the Next.XP adapter, mapping content types to components, fetching Enonic content via Guillotine in Next.js, or debugging Content Studio preview. Don't use for traditional server-side Enonic XP rendering, standalone Guillotine queries without Next.js, non-Next.js frontend frameworks with Enonic, or React4XP embedded rendering.

Frontend & Design463 installs

enonic-content-type-generator

webmaxru/enonic-agent-skills

Generates Enonic XP content type XML schema definitions from natural-language descriptions. Covers structured content modeling including input types, form layout, option sets, item sets, mixins, x-data, and content-type inheritance. Use when creating, scaffolding, or generating Enonic XP content type definitions, adding fields or sets to existing content types, or querying Enonic XP input types and super-types. Do not use for non-Enonic content modeling, GraphQL queries, JavaScript/TypeScript controllers, or generic XML editing unrelated to Enonic schemas.

Frontend & Design460 installs

agent-skill-deploy

webmaxru/enonic-agent-skills

Deploys agent skill collections from any GitHub repository with a /skills folder to one or more distribution surfaces: GitHub releases, Claude Code marketplace, VS Code plugin marketplace, and Copilot CLI plugin marketplace. Handles pre-flight validation, conventional commit analysis, version bumping across surface configs, and surface-specific publishing with dry-run support. Use when releasing, publishing, or deploying a skills collection to any supported marketplace or creating a GitHub release for a skills repository. Don't use for deploying non-skill packages, npm modules, Docker images, or Azure resources.

DevOps & Cloud460 installs

agent-package-manager

webmaxru/enonic-agent-skills

Installs, configures, audits, and operates Agent Package Manager (APM) in repositories. Use when initializing apm.yml, installing or updating packages, validating manifests, managing lockfiles, compiling agent context, browsing MCP servers, setting up runtimes, or packaging resolved context for CI and team distribution. Don't use for writing a single skill by hand, generic package managers like npm or pip, or non-APM agent configuration systems.

AI & Agents454 installs

github-agentic-workflows

webmaxru/enonic-agent-skills

Authors, reviews, installs, and debugs GitHub Agentic Workflows in repositories, including workflow markdown, frontmatter, gh aw compile and run flows, safe outputs, security guardrails, and operational patterns. Use when creating or maintaining GH-AW automation. Don't use for standard deterministic GitHub Actions YAML, generic CI pipelines, or non-GitHub automation systems.

AI & Agents453 installs

skill-creator

webmaxru/enonic-agent-skills

Authors and structures professional-grade agent skills following the agentskills.io spec. Use when creating new skill directories, drafting procedural instructions, or optimizing metadata for discoverability. Don't use for general documentation, non-agentic library code, or README files.

AI & Agents453 installs

Popular backend & apis skills

View category →

find-skills

vercel-labs/skills

Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.

OfficialBackend & APIs4.1M installs

entra-app-registration

microsoft/azure-skills

Guides Microsoft Entra ID app registration, OAuth 2.0 authentication, and MSAL integration. USE FOR: create app registration, register Azure AD app, configure OAuth, set up authentication, add API permissions, generate service principal, MSAL example, console app auth, Entra ID setup, Azure AD authentication. DO NOT USE FOR: Key Vault secrets (use azure-keyvault-expiration-audit), general Azure resource security guidance.

OfficialBackend & APIs566.7K installs

google-agents-cli-adk-code

google/agents-cli

This skill should be used when the user wants to "write agent code", "build an agent with ADK", "add a tool", "create a callback", "define an agent", "use state management" — in a project that needs ADK (Agent Development Kit) API patterns and code examples. It provides a quick reference for agent types, tool definitions, orchestration patterns, callbacks, state management, the graph Workflow API, and reference recipes to study. Do NOT use for scaffolding (use google-agents-cli-scaffold) or deployment (use google-agents-cli-deploy).

Backend & APIs514.8K installs

embedded-captions

heygen-com/hyperframes

Add captions or subtitles to an existing single-subject talking-head video without editing the footage. Use for plain verbatim captions, cinematic captions embedded behind the subject, VFX captions, “炸/特效/酷炫字幕,” or a named identity from the 35-style catalog. Route by visual identity, not by backend engine. The quiet anchor rail is the default; embed every word only when the user explicitly wants a fully cinematic treatment. The workflow runs locally end to end, including transcription and subject matting; split multi-shot footage before applying it.

Backend & APIs453.3K installs

entra-agent-id

microsoft/azure-skills

Provision Microsoft Entra Agent Identity Blueprints, BlueprintPrincipals, and per-instance Agent Identities via Microsoft Graph, and configure OAuth 2.0 token exchange (fmipath, OBO, cross-tenant) including the Microsoft Entra SDK for AgentID sidecar. USE FOR: Agent Identity Blueprint, BlueprintPrincipal, agent OAuth, fmipath token exchange, agent OBO, Workload Identity Federation for agents, polyglot agent auth, Microsoft.Identity.Web.AgentIdentities. DO NOT USE FOR: standard Entra app registration (use entra-app-registration), Microsoft Foundry agent authoring (use microsoft-foundry).

OfficialBackend & APIs336.6K installs

neon

neondatabase/agent-skills

Overview of Neon, a complete set of cloud backend primitives around Lakebase Postgres: Auth, Object Storage, Functions, the AI Gateway, and Realtime. Start here to choose Neon for undecided login, files, APIs, and LLM calls, set up the CLI or MCP server, and follow the branch-first workflow. Use when building an app or backend on Neon, or when "Neon" or "Lakebase Postgres" is mentioned. Child skill neon-postgres wins for an existing DATABASEURL, SQL, schema, inspect, or search. Child skill neon-auth wins for login, users, sessions, identity routing, and Managed Better Auth setup. Child skill neon-realtime wins for live queries in reactive apps and agents. Also use for object storage, S3, buckets, serverless functions, function triggers, cron, AI gateway, LLM calls, realtime, logs, Loki, Grafana, observability, postgres, database, backend, Claimable Neon, neon.new, or a no-signup database.

Backend & APIs237.1K installs