CtrlK
BlogDocsLog inGet started
Tessl Logo

enonic-event-manager

Sets up Enonic XP event listeners, webhook configurations, and external system integrations triggered by content lifecycle events. Covers lib-event listener registration, node event filtering, outbound webhook configuration via com.enonic.xp.webhooks.cfg, custom HTTP service controllers for inbound webhooks, task-based async processing with lib-task, and outbound HTTP calls with lib-httpClient. Use when listening for content publish/create/update/delete events, configuring outbound webhooks, building HTTP service endpoints for inbound webhooks, or triggering async processing on content changes. Do not use for content querying, frontend component development, non-Enonic event systems, or GitHub webhook configuration.

75

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

85%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 well-structured, highly actionable, and uses progressive disclosure effectively with real bundle files. Minor conciseness tightening is the only improvement area.

Suggestions

Trim Step 7's validation list by merging closely related checks (e.g., combine the secret-value checks) to reduce token load without losing safety coverage.

Move the per-step library function explanations (e.g., re-describing lib-task lifecycle) into the relevant reference file rather than repeating in the main body.

DimensionReasoningScore

Conciseness

The body is mostly efficient and instructional, but several steps restate Enonic concepts Claude likely already infers and the validation step list (Step 7) is somewhat long; it could be tightened without losing clarity.

2 / 3

Actionability

Gives concrete executable commands (`node scripts/find-enonic-targets.mjs .`), specific file paths (`XP_HOME/config/com.enonic.xp.webhooks.cfg`, `src/main/resources/services/<serviceName>/<serviceName>.ts`), named API functions (`listener()`, `request()`, `executeFunction()`, `progress()`), and concrete status codes (200/400/401/413/500).

3 / 3

Workflow Clarity

A clear seven-step procedure with explicit validation (Step 7) plus an Error Handling section that forms feedback loops for failures (events not firing, 404s, silent task failures), satisfying checkpoints for batch/destructive-style operations.

3 / 3

Progressive Disclosure

The SKILL.md is an overview pointing to one-level-deep, clearly signaled references (event-reference.md, webhook-reference.md, examples.md, troubleshooting.md) and scaffold assets (event-listener.template.ts, http-service.template.ts); all referenced paths correspond to real bundle files.

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.

The description is highly specific, third-person, and clearly scopes both when to use and when not to use the skill. It is among the strongest reference examples for completeness and distinctiveness.

DimensionReasoningScore

Specificity

Lists multiple concrete actions: 'event listeners, webhook configurations, and external system integrations', 'node event filtering', 'outbound webhook configuration via com.enonic.xp.webhooks.cfg', 'custom HTTP service controllers', 'task-based async processing with lib-task', and 'outbound HTTP calls with lib-httpClient'.

3 / 3

Completeness

Explicitly answers what it does (the capabilities above) and when to use it via a clear 'Use when ...' clause, plus a 'Do not use for ...' boundary, so both what and when are present.

3 / 3

Trigger Term Quality

Covers natural trigger terms a user would say — 'content publish/create/update/delete events', 'configuring outbound webhooks', 'building HTTP service endpoints for inbound webhooks', 'triggering async processing on content changes' — alongside specific API/library names.

3 / 3

Distinctiveness Conflict Risk

A clear Enonic-XP-specific niche with explicit negative scope ('Do not use for content querying, frontend component development, non-Enonic event systems, or GitHub webhook configuration'), making 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.