MCPInstall

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.

Installs
295
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-app-manager
  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-app-manager 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 CLI & Local Dev Environment Helper

Procedures

Step 1: Detect Workspace Context

  1. Execute node scripts/find-enonic-targets.mjs from the skill root to scan the current workspace for Enonic project markers (.enonic, build.gradle with com.enonic.xp plugin, gradle.properties with xpVersion).
  2. If markers are found, note the project name, linked sandbox, and XP version from the output. Use these values as defaults for subsequent commands.
  3. If no markers are found, treat the request as a greenfield setup and proceed to sandbox creation or project scaffolding as appropriate.

Step 2: Ensure CLI is Available

  1. Verify the Enonic CLI is installed by running enonic --version.
  2. If the command fails, read references/cli-reference.md for installation instructions and guide through the appropriate method for the detected OS:
    • npm (any OS): npm install -g @enonic/cli
    • macOS: brew tap enonic/cli && brew install --no-quarantine enonic
    • Linux: wget -qO- https://repo.enonic.com/public/com/enonic/cli/installer/cli-linux/1.0.0/cli-linux-1.0.0.sh | sh
    • Windows: scoop bucket add enonic https://github.com/enonic/cli-scoop.git && scoop install enonic
  3. After installation, verify with enonic --version.

Step 3: Sandbox Management

  1. Read references/cli-reference.md for the full sandbox command catalog.
  2. Match the request to the correct operation:
    • Create: enonic sandbox create <name> [-v <version>] [-t <template>] [--skip-template] [-i <image>] [-f]
    • List: enonic sandbox ls
    • Start: enonic sandbox start <name> [--detach] [--prod] [--debug]
    • Stop: enonic sandbox stop
    • Upgrade: enonic sandbox upgrade <name> -v <version>
    • Delete: enonic sandbox delete <name> -f
    • Copy: enonic sandbox copy <source> <target>
  3. When creating a sandbox, prompt for the XP version if not specified. Use -f flag for non-interactive execution when the version and name are known. Note: with -f, the sandbox auto-starts after creation unless --skip-start is also provided.
  4. If the request mentions templates, list available templates or use -t <template> flag. Use --skip-template to create a bare sandbox with no pre-installed apps.
  5. If the request mentions Docker, use -i <image> (e.g., enonic/xp:latest-sdk) to back the sandbox with a Docker image instead of a downloaded XP distribution. Requires docker on $PATH.

Step 4: Project Scaffolding

  1. For new project creation, use the simplified command: enonic create <name> [-r <starter>] [-s <sandbox>] [-f]
  2. Common starters include starter-vanilla, starter-headless, and starter-nextjs. Read references/cli-reference.md for the full list of options.
  3. To link an existing project to a different sandbox: enonic project sandbox <name>
  4. Ensure the project folder contains build.gradle and .enonic configuration after creation.

Step 5: Development Workflow

  1. Determine the appropriate development command:
    • Dev mode (hot-reload): enonic dev — starts the sandbox in detached mode and runs the app with file watching. Execute from the project root.
    • Build only: enonic project build
    • Deploy to sandbox: enonic project deploy [sandbox-name] [-c] — use -c for continuous deployment.
    • Install to running XP: enonic project install
    • Run tests: enonic project test
    • Clean build artifacts: enonic project clean
    • Arbitrary Gradle task: enonic project gradle <tasks>
  2. If the sandbox is not running, start it first: enonic sandbox start <name> -d
  3. To terminate dev mode, use Ctrl-C. The CLI will attempt to stop the detached sandbox automatically.

Step 6: App Management on Running XP

  1. For managing applications on a running XP instance, read references/cli-reference.md for the XP app commands.
  2. Match the operation:
    • Install from URL: enonic app install --url <jar-url>
    • Install from file: enonic app install --file <path-to-jar>
    • Start app: enonic app start <app-key>
    • Stop app: enonic app stop <app-key>
  3. Authentication is required for XP commands. Use --cred-file <path> (XP 7.15+), --client-key <path> + --client-cert <path> for mTLS (XP 7.15+), or set ENONIC_CLI_REMOTE_USER and ENONIC_CLI_REMOTE_PASS environment variables.

Step 7: CI/CD Pipeline Generation

  1. Read assets/enonic-ci.template.yml for the GitHub Actions workflow template.
  2. Customize the template based on the project:
    • Set the correct XP version in the sandbox creation step.
    • Set the app name and Gradle build parameters.
    • Configure deployment targets (sandbox for staging, cloud for production).
  3. Place the generated workflow file at .github/workflows/enonic-ci.yml in the project repository.

Step 8: Troubleshooting

  1. If a sandbox fails to start or a deployment fails, read references/troubleshooting.md for common issues and resolutions.
  2. Key diagnostic commands:
    • enonic sandbox ls — check sandbox status and XP version.
    • enonic system info — check running XP instance details.
    • Check port 8080 (HTTP) and 5005 (debug) availability.
  3. Read references/compatibility.md for CLI-to-XP version compatibility if version mismatch errors occur.

Error Handling

  • If scripts/find-enonic-targets.mjs returns no results, proceed with greenfield setup instructions rather than failing.
  • If enonic --version fails, guide through CLI installation per Step 2 before proceeding.
  • If sandbox creation fails with a version error, read references/compatibility.md and suggest a compatible XP version.
  • If port conflicts occur during sandbox start, read references/troubleshooting.md for resolution steps.
  • If enonic dev fails, verify the project has a Gradle dev task (present in all official starters) and that the linked sandbox exists and is not already running in another terminal.

FAQ

What does the enonic-app-manager skill do?

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.

How do I install enonic-app-manager?

Run npx skills add https://github.com/webmaxru/enonic-agent-skills --skill enonic-app-manager 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-app-manager/ (personal) or .claude/skills/enonic-app-manager/ (project).

Which AI agents can use enonic-app-manager?

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-app-manager 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-app-manager?

It is published by webmaxru in webmaxru/enonic-agent-skills. It has 295 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

enonic-guillotine-query-builder

webmaxru/enonic-agent-skills

Open the skill to read its SKILL.md instructions.

AI & Agents457 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

Popular devops & cloud skills

View category →

microsoft-foundry

microsoft/azure-skills

Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and resources end to end. USE FOR: foundry, azd ai agent, azd provision/deploy, hosted agent scaffold/develop/run/deploy/troubleshoot, prompt agent create, managed harness agent create, GitHub Copilot harness agent, create agent, update agent, add tool to agent, invoke agent, agent insights, evaluate agent, batch eval, continuous eval, continuous monitoring, agent CI/CD, optimize prompt, improve prompt, optimize agent instructions, Agent Optimizer scaffold, dataset curation from traces, deploy model, model fine-tuning (SFT/DPO/RFT), Foundry project, RBAC, role assignment, permissions, quota, capacity, region, deployment failure, AI Services, create Foundry resource, knowledge index, customize deployment, onboard, availability, training-data, grader, distillation, large file upload. DO NOT USE FOR: Azure Functions, App Service, general Azure deploy (use azure-deploy), general Azure prep (use azure

OfficialDevOps & Cloud579.1K installs

azure-diagnostics

microsoft/azure-skills

Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe triage. WHEN: debug production issues, troubleshoot app service, app service high CPU, app service deployment failure, troubleshoot container apps, container app 503 or target port mismatch, troubleshoot functions, function telemetry missing or stopped after a config/connection-string change, troubleshoot AKS, VM RDP, Linux SSH, VM black screen, can't connect to VM, reset VM password, NSG or firewall blocking, kubectl cannot connect, kube-system/CoreDNS failures, pod pending, crashloop, node not ready, upgrade failures, analyze logs, KQL, insights, image pull failures, cold start issues, health probe failures, resource health, root cause of errors, troubleshoot event hubs, troubleshoot service bus, messaging SDK error, AMQP connection failure, message lock lost, lock renewal during long-running processing, service bus dead letter.

OfficialDevOps & Cloud569.8K installs

azure-prepare

microsoft/azure-skills

Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Terraform), and Dockerfiles for the Azure Developer CLI (azd) workflow. USE ONLY when the user explicitly wants to use azd as the deployment tool, or the project already has an azure.yaml file. DO NOT USE FOR: non-azd deployments, Python App Service code-only deploys (use python-appservice-deploy), or cross-cloud migration (use azure-cloud-migrate). WHEN: prepare app for azd, create azure.yaml, set up azd infrastructure, modernize app for Azure with azd, deploy with azd, function app, timer trigger, service bus trigger, event-driven function, managed identity, generate Bicep, generate Terraform, create and deploy to Azure.

OfficialDevOps & Cloud569K installs

azure-ai

microsoft/azure-skills

Use for Azure AI: Search, Speech, OpenAI, Document Intelligence. Helps with search, vector/hybrid search, speech-to-text, text-to-speech, transcription, OCR. WHEN: AI Search, query search, vector search, hybrid search, semantic search, speech-to-text, text-to-speech, transcribe, OCR, convert text to speech.

OfficialDevOps & Cloud568.8K installs

azure-deploy

microsoft/azure-skills

Execute Azure deployments for ALREADY-PREPARED applications that have existing .azure/deployment-plan.md and infrastructure files. DO NOT use this skill when the user asks to CREATE a new application — use azure-prepare instead. This skill runs azd up, azd deploy, terraform apply, and az deployment commands with built-in error recovery. Requires .azure/deployment-plan.md from azure-prepare and validated status from azure-validate. WHEN: "run azd up", "run azd deploy", "execute deployment", "push to production", "push to cloud", "go live", "ship it", "bicep deploy", "terraform apply", "publish to Azure", "launch on Azure". DO NOT USE WHEN: "create and deploy", "build and deploy", "create a new app", "set up infrastructure", "create and deploy to Azure using Terraform" — use azure-prepare for these.

OfficialDevOps & Cloud568.6K installs

azure-validate

microsoft/azure-skills

Pre-deployment validation for Azure readiness. Run deep checks on configuration, infrastructure (Bicep or Terraform), RBAC role assignments, managed identity permissions, and prerequisites before deploying. WHEN: validate my app, check deployment readiness, run preflight checks, verify configuration, check if ready to deploy, validate azure.yaml, validate Bicep, test before deploying, troubleshoot deployment errors, validate Azure Functions, validate function app, validate serverless deployment, verify RBAC roles, check role assignments, review managed identity permissions, what-if analysis, validate Container Apps deployment.

OfficialDevOps & Cloud568K installs