enonic-app-manager

Guides developers through Enonic CLI commands for sandbox management, project scaffolding, local development, app deployment, and CI/CD pipeline generation. Use when creating Enonic XP sandboxes, starting or stopping local instances, scaffolding projects from starters, running dev mode with hot-reload, deploying apps, or generating CI/CD workflows for Enonic apps. Don't use for writing XP application code (controllers, content types), querying via Guillotine or lib-content APIs, configuring non-Enonic environments, or Docker/Kubernetes deployment of XP.

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

87%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.

A well-structured, command-driven procedure guide with executable instructions and clean progressive disclosure to real bundle files. Its main gap is the absence of explicit validation/confirmation checkpoints around destructive sandbox operations (delete, force flags).

Suggestions

Add a pre-destruction validation checkpoint before 'enonic sandbox delete <name> -f' — e.g., confirm the target via 'enonic sandbox ls' and prompt for confirmation before running the delete.

Insert an explicit verify step after Step 4 (scaffolding) to confirm 'build.gradle' and '.enonic' exist before proceeding to Step 5 dev workflow, making the validation loop explicit rather than a passing instruction.

Treat the CI/CD generation (Step 7) as a batch/generated-artifact operation and add a closing validation step (e.g., run 'actionlint' on .github/workflows/enonic-ci.yml or a dry-run check) before declaring the workflow complete.

Dimension	Reasoning	Score
Conciseness	The body is command-dense and avoids explaining concepts Claude already knows; annotations (e.g., '-f auto-starts unless --skip-start') capture non-obvious flag behavior, so nearly every token earns its place.	3 / 3
Actionability	Commands are concrete and copy-paste ready with full flag sets, e.g. 'enonic sandbox create <name> [-v <version>] [-t <template>] [--skip-template] [-i <image>] [-f]', matching the fully-executable anchor.	3 / 3
Workflow Clarity	Steps 1-8 are clearly sequenced with an install-verification checkpoint and an Error Handling feedback section, but destructive operations like 'enonic sandbox delete <name> -f' lack explicit pre-deletion validation/confirmation, which the rubric guidelines say should cap this dimension at 2.	2 / 3
Progressive Disclosure	The SKILL.md is a concise overview pointing to well-signaled, one-level-deep references (references/cli-reference.md, troubleshooting.md, compatibility.md, assets/enonic-ci.template.yml, scripts/find-enonic-targets.mjs) that all exist as real files, matching the clear-overview-with-one-level-deep-references anchor.	3 / 3
	Total	11 / 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.

A strong, third-person description that pairs a concrete capability list with an explicit trigger clause and a sharp negative-scope boundary. It is both comprehensive and tightly scoped to the Enonic CLI/local-dev domain.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities — 'sandbox management, project scaffolding, local development, app deployment, and CI/CD pipeline generation' — matching the anchor that enumerates several specific actions.	3 / 3
Completeness	Clearly answers both 'what' (first sentence lists capabilities) and 'when' (explicit 'Use when...' clause), and additionally a 'Don't use for...' boundary clause, exceeding the bar for a 3.	3 / 3
Trigger Term Quality	The 'Use when' clause enumerates natural developer phrasings — 'creating Enonic XP sandboxes, starting or stopping local instances, scaffolding projects from starters, running dev mode with hot-reload, deploying apps' — giving good coverage of terms users would actually say.	3 / 3
Distinctiveness Conflict Risk	The 'Don't use for writing XP application code... querying via Guillotine or lib-content APIs... Docker/Kubernetes deployment' carve-out establishes a clear niche with distinct triggers unlikely to conflict with adjacent skills.	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-app-manager/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.