How do I install the Elsa Add Event Contribution skill?

Run npx skillmds@latest add elsa-workflows/elsa-add-event-contribution in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Elsa Add Event Contribution safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Elsa Add Event Contribution?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Elsa Add Event Contribution free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Elsa Add Event Contribution?

elsa-workflows (@elsa-workflows) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Elsa Add Event Contribution by elsa-workflows

Name: Elsa Add Event Contribution
Author: elsa-workflows

Elsa Add Event Contribution

Plan or implement Elsa event contributions and independent event subscribers using the AI-provider-neutral event/contribution workflow. Use when adding fan-in contributors, Source/Contributor/PreProcessor/PostProcessor implementations, action-named contributors, aggregating handlers, or non-fan-in event subscribers.

File contents

User Input

$ARGUMENTS

Outline

Read docs/skills/catalog.md#add-event-contribution and, if relevant, docs/skills/catalog.md#add-independent-event-subscriber.
Read framework event/contribution gates and the owning domain's EXTENSION_POINTS.md.
Decide whether the change is a fan-in contribution or an independent subscriber.
For fan-in contribution, choose the contributor-interface kind and keep one owning aggregating event handler for that contribution purpose.
For independent subscribers, document handler behavior, registration, failure behavior, and tests.
Update extension-point catalogs and tests when implementing.

Important: event delivery strategy roles are still tracked as unfinished work. If publisher/subscriber ownership of strategy selection matters, stop and plan the event-handling strategy-role unit instead of guessing. After the user approves the event contribution/subscriber plan, required tests, extension-point catalog updates, generated-map refreshes, and small docs follow-through are part of completing the approved work.

Frequently asked questions