agentleFS
Sign inStart free
aborroyaborroy/aiup-alfresco/skills/event-api-topology-checker/SKILL.md

event-api-topology-checker

Skill14 starsChanged 5 months agoApache-2.0View on GitHub

Validates ActiveMQ topic names and consumer group patterns against Alfresco event API conventions. Applies to Out-of-Process SDK (Spring Boot) only. Trigger when generating event-driven code with /events.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Default Alfresco topic: alfresco.repo.event2

    line 15
  2. Very specific:

    Verify spring.activemq.broker-url is set

    line 27
  3. Distinctive:

    Verify event filters match expected node types/aspects

    line 28

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Event API Topology Checker

Validate Out-of-Process event-driven code against Alfresco Java Event API conventions.

This skill applies exclusively to the Spring Boot Out-of-Process SDK (alfresco-java-sdk). In-Process extensions (behaviours, actions) run inside the ACS JVM and do not use this event bus — use behaviours/policies instead.

Topic Naming

  • Default Alfresco topic: alfresco.repo.event2
  • Custom topics must not collide with built-in topics
  • Consumer group names should follow: {extension-prefix}.{purpose}

Event Types

Valid event types from org.alfresco.event.sdk.model.v1:

  • NodeCreatedEvent, NodeUpdatedEvent, NodeDeletedEvent
  • ContentCreatedEvent, ContentUpdatedEvent, ContentDeletedEvent
  • ChildAssocCreatedEvent, ChildAssocDeletedEvent
  • PeerAssocCreatedEvent, PeerAssocDeletedEvent

Configuration Validation

  • Verify spring.activemq.broker-url is set
  • Verify event filters match expected node types/aspects
  • Warn if no error handling or dead-letter queue is configured

Output

Report topology issues, naming violations, and missing error handling.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free