CtrlK
BlogDocsLog inGet started
Tessl Logo

enonic-nextxp-integration

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.

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 concise, highly actionable, well-sequenced with validation checkpoints, and uses clean one-level-deep progressive disclosure to real bundle files. It assumes Claude's competence and adds only domain-specific detail.

DimensionReasoningScore

Conciseness

The body is lean and action-oriented — numbered steps with specific file paths, env variables, and commands, and no padding explaining what Next.js, Enonic, or GraphQL are. Every line earns its place.

3 / 3

Actionability

Concrete executable guidance throughout: 'npm install @enonic/nextjs-adapter', exact env var names with example values, GraphQL patterns like '$path:ID!', and explicit registry calls such as 'ComponentRegistry.addContentType()'. A few steps are 'Read references/X.md' pointers, but the direct instructions are copy-paste ready.

3 / 3

Workflow Clarity

Seven clearly sequenced procedures with explicit validation: Step 7 validates the integration, Step 1 stops cleanly when the skill does not apply, and the Error Handling section provides a validate→diagnose→retry feedback loop for preview and query failures.

3 / 3

Progressive Disclosure

The overview body signals one-level-deep references to real files (references/nextxp-reference.md, examples.md, compatibility.md, troubleshooting.md) and a real script (scripts/find-nextxp-targets.mjs) plus an asset template, each cited at the point of need — 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, complete, and distinctive. It names concrete capabilities, provides explicit 'Use when' triggers, and guards against mis-invocation with a clear exclusion list.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities — 'adapter configuration', 'content type to React component mapping', 'Guillotine GraphQL data fetching', 'Content Studio preview mode', and 'draft/master branch switching' — matching the top anchor of several specific concrete actions.

3 / 3

Completeness

Clearly answers both 'what' (the enumerated capabilities) and 'when' via an explicit 'Use when...' trigger clause, plus a 'Don't use for...' exclusion list.

3 / 3

Trigger Term Quality

The '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' clause covers the natural phrasings a user would say.

3 / 3

Distinctiveness Conflict Risk

A clearly defined niche (Next.js + Enonic XP headless) with explicit exclusions ('Don't use for traditional server-side Enonic XP rendering, standalone Guillotine queries...') makes triggering for the wrong skill 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.