enonic-content-type-generator

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.

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

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 body is a tight, actionable five-step workflow with explicit validation and error-recovery feedback loops, correctly deferring detailed reference material to one-level-deep bundle files that exist. It assumes Claude's competence without padding.

Dimension	Reasoning	Score
Conciseness	The body is lean and instruction-focused with numbered steps and no exposition of concepts Claude already knows (e.g., no explanation of what Enonic XP or XML is); detail is delegated to reference files, so every token earns its place.	3 / 3
Actionability	Provides concrete executable commands ('node scripts/find-enonic-targets.mjs [workspaceRoot]'), exact target paths, and per-input-type config element lists (e.g., 'allowContentType, allowPath, treeMode, hideToggleIcon'); guidance is specific and copy-paste ready.	3 / 3
Workflow Clarity	A clear five-step sequence culminates in explicit validation (well-formed XML, type cross-reference, unique names, occurrences consistency) with a feedback loop in Error Handling (validation fails -> read troubleshooting.md -> correct -> regenerate), appropriate for XML manipulation.	3 / 3
Progressive Disclosure	The overview body signals one-level-deep references that all resolve to real files ('references/content-type-reference.md', 'references/examples.md', 'references/troubleshooting.md', 'scripts/find-enonic-targets.mjs', 'assets/content-type.template.xml'), with content appropriately split and easy to navigate.	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 third-person, concise, and concrete, covering what the skill does and when to use it with explicit positive and negative triggers. It distinguishes itself clearly from adjacent skills via the 'Do not use for ...' clause.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions and capabilities — 'Generates Enonic XP content type XML schema definitions', 'Covers structured content modeling including input types, form layout, option sets, item sets, mixins, x-data, and content-type inheritance' — matching the anchor for listing multiple specific concrete actions.	3 / 3
Completeness	Explicitly answers both what (generates XML schema definitions from natural-language descriptions, covers specific modeling constructs) and when via a clear 'Use when ...' clause, plus explicit exclusions.	3 / 3
Trigger Term Quality	Includes natural user phrasing such as 'creating, scaffolding, or generating Enonic XP content type definitions, adding fields or sets to existing content types', giving good coverage of terms a user would actually say.	3 / 3
Distinctiveness Conflict Risk	Targets a clear niche (Enonic XP content types) and adds explicit non-trigger boundaries ('Do not use for non-Enonic content modeling, GraphQL queries, JavaScript/TypeScript controllers, or generic XML editing'), making conflict unlikely.	3 / 3
	Total	12 / 12 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: webmaxru/enonic-agent-skills
Path: skills/enonic-content-type-generator/SKILL.md
Commit: 029e044

Reviewed: 16 days ago

Table of Contents

Discovery Implementation Validation

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.