CtrlK
BlogDocsLog inGet started
Tessl Logo

enonic-guillotine-query-builder

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.

80

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

100%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is a well-structured, actionable procedure that respects token budget, sequences work with explicit validation and recovery loops, and cleanly offloads detail to verified one-level-deep references. It meets the top anchor on every dimension.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — it never explains what GraphQL or Guillotine is, and each step delivers only actionable specifics (exact field names, type-name transformation rules, validation checks) with no padding.

3 / 3

Actionability

Guidance is concrete and specific — e.g. "Execute `node scripts/find-guillotine-targets.mjs .`", the exact descriptor→type-name rule with a worked example, and precise field requirements ("Each `QueryDSLInput` must contain exactly one expression field"); per the rubric's code-vs-instruction note, actionable instruction-only guidance is not penalized for lacking inline code.

3 / 3

Workflow Clarity

Nine explicitly sequenced steps culminate in a dedicated validation checklist (Step 9) and a separate Error Handling section that provides fix-and-retry feedback loops (e.g. "simplify to `matchAll: {}` to confirm data exists, then re-add filters one at a time").

3 / 3

Progressive Disclosure

The body is an organized overview that signals one-level-deep references to real bundle files (references/guillotine-reference.md, compatibility.md, examples.md, troubleshooting.md, scripts/find-guillotine-targets.mjs, assets/guillotine-query.template.ts), all verified to exist, with no nested-reference chains.

3 / 3

Total

12

/

12

Passed

Description

100%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, trigger-rich, and well-scoped, clearly stating capabilities, usage conditions, and exclusions in concise third-person voice. It hits every anchor at the top of the scale with no fluff or over-claims.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Composes, debugs, and optimizes Guillotine GraphQL queries" plus an enumerated coverage list ("query construction, variable usage, filtering, aggregation, pagination, sorting, and TypeScript type generation"), matching the score-3 anchor for several specific concrete actions.

3 / 3

Completeness

Explicitly answers both what (compose/debug/optimize queries + type generation) and when via a clear "Use when..." clause, and further sharpens scope with a "Don't use for..." exclusion list, satisfying the score-3 anchor for explicit triggers on both axes.

3 / 3

Trigger Term Quality

Natural trigger phrasing a user would actually say — "writing or troubleshooting Guillotine queries", "querying custom content types through GraphQL", "generating typed interfaces from Guillotine responses" — gives good coverage of plausible user requests rather than technical jargon.

3 / 3

Distinctiveness Conflict Risk

The niche is tightly bounded to Enonic XP Guillotine and the negative triggers ("non-Enonic GraphQL APIs (Apollo, Hasura)", "server-side lib-content queries", "Guillotine deployment and CORS configuration") make collision with adjacent skills unlikely.

3 / 3

Total

12

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
webmaxru/enonic-agent-skills
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.