Agent skill

Add Integration Event

by fullstackhero in fullstackhero/dotnet-starter-kit

Publish a cross-module integration event via the Outbox and handle it idempotently in another module.

MITAuto-check passedDevelopment

Install Add Integration Event

skills CLI
$ npx skills add fullstackhero/dotnet-starter-kit --skill add-integration-event -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install fullstackhero/dotnet-starter-kit add-integration-event --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/fullstackhero/dotnet-starter-kit.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/add-integration-event .claude/skills/add-integration-event && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
add-integration-event
GitHub stars
6.8k
Token cost
~1.1k tokens
SKILL.md length
300 words
Files
1
Skills in repo
11
Repo updated
First seen
Licence
MIT

At a glance

Publish a cross-module integration event via the Outbox and handle it idempotently in another module.

  • Works in 3 steps: Define the event (source module's… → Publish via the Outbox (source handler) → Handle it (consumer module)
  • One module must react to something that happened in another
  • SKILL.md covers Step 1 — Define the event…, Step 2 — Publish via the…, Step 3 — Handle it (consumer… and Gotchas, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Add Integration Event is an agent skill from fullstackhero/dotnet-starter-kit. Publish a cross-module integration event via the Outbox and handle it idempotently in another module. Use when one module must react to something that happened in another. See .agents/rules/eventing.md.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Project scaffolding. It works with React. The repository describes itself as: Production Grade Cloud-Ready .NET 10 Starter Kit (Web API + React Client) with Multitenancy Support, and Clean/Modular Architecture that saves roughly 200+ Development Hours! All… The licence is MIT.

When your agent uses it

  • One module must react to something that happened in another
  • Tasks that involve Project scaffolding

Example prompts

  • “/add-integration-event”

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. Define the event (source module's Contracts)
  2. Publish via the Outbox (source handler)
  3. Handle it (consumer module)

What it can do on your machine

Read from SKILL.md and the folder at commit 0bd98e3. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are csharp).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Add Integration Event loads about 1.1k tokens when it runs. Until then it costs about 56 tokens; SKILL.md has 300 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~56
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from fullstackhero/dotnet-starter-kit at commit 0bd98e3, republished under its MIT licence (© fullstackhero). 300 words, ~1,117 tokens.

Download SKILL.mdSave it as .claude/skills/add-integration-event/SKILL.md (or your agent's skills folder).
name
add-integration-event
description
Publish a cross-module integration event via the Outbox and handle it idempotently in another module. Use when one module must react to something that happened in another. See .agents/rules/eventing.md.
argument-hint
[SourceModule] [EventName] [ConsumerModule]

Add Integration Event

Cross-module communication goes through integration events + the Outbox (transactional, crash-safe) — never a direct in-process call into another module's runtime, and never IEventBus.PublishAsync from a handler. Full model: .agents/rules/eventing.md.

Step 1 — Define the event (source module's Contracts)

Modules.{Source}.Contracts/Events/{Event}IntegrationEvent.cs — implement IIntegrationEvent:

csharp
public sealed record {Event}IntegrationEvent(
    Guid Id,
    DateTime OccurredOnUtc,
    string? TenantId,
    string CorrelationId,
    string Source,
    Guid {Entity}Id,
    string SomePayload) : IIntegrationEvent;

⚠️ Don't rename/move this type later — the outbox stores its assembly-qualified name; a rename makes Type.GetType() return null and the message dead-letters. Keep the type name + namespace stable.

Step 2 — Publish via the Outbox (source handler)

Publishing needs no module registration — the outbox is framework-owned and the host wires it once. Inject IOutboxWriter (from FSH.Framework.Eventing.Abstractions) and add the event in the same unit of work:

csharp
public sealed class Do{Thing}CommandHandler({Source}DbContext db, IOutboxWriter outbox)
    : ICommandHandler<Do{Thing}Command, Unit>
{
    public async ValueTask<Unit> Handle(Do{Thing}Command command, CancellationToken cancellationToken)
    {
        // … mutate entities, db.SaveChangesAsync …
        var evt = new {Event}IntegrationEvent(
            Id: Guid.CreateVersion7(),
            OccurredOnUtc: DateTime.UtcNow,
            TenantId: /* current tenant */,
            CorrelationId: Guid.NewGuid().ToString(),
            Source: "{Source}",
            {Entity}Id: entity.Id,
            SomePayload: "…");
        await outbox.AddAsync(evt, cancellationToken).ConfigureAwait(false);
        return Unit.Value;
    }
}

The OutboxDispatcherHostedService later publishes it via IEventBus.

Step 3 — Handle it (consumer module)

Modules.{Consumer}/IntegrationEventHandlers/{Event}IntegrationEventHandler.cs — sealed, implement IIntegrationEventHandler<T>:

csharp
public sealed class {Event}IntegrationEventHandler({Consumer}DbContext db /*, IHubContext<AppHub> hub */)
    : IIntegrationEventHandler<{Event}IntegrationEvent>
{
    public async Task HandleAsync({Event}IntegrationEvent @event, CancellationToken cancellationToken)
    {
        ArgumentNullException.ThrowIfNull(@event);
        // … write to the consumer's tables / push a notification …
        await db.SaveChangesAsync(cancellationToken).ConfigureAwait(false);
    }
}

Register the consumer's handlers in its ConfigureServices:

csharp
builder.Services.AddIntegrationEventHandlers(typeof({Consumer}Module).Assembly);

Gotchas

  • Idempotency is free with the in-memory bus (the Inbox dedups by {eventId, handlerName}) — don't hand-roll it.
  • The in-memory bus runs handlers synchronously in the publisher's scope — keep the handler lean; a throw surfaces to the originating request. Published via the outbox, that scope belongs to the dispatcher, so the consumer runs on the next cycle and its failures never reach the caller. Don't let a caller (or a test) assume the side effect already happened; integration tests drain with OutboxDrain.DrainAsync.
  • If the handler reads a tenant-filtered DbContext from a background path (open-generic handler, Hangfire job), restore Finbuckle context first via IMultiTenantContextSetter (see WebhookFanoutHandler).
  • Module load order: the consumer must load before the publisher if it must react (Order in [assembly: FshModule]) — e.g. Notifications (750) before Chat (800).

Checklist

  • Event in source Contracts, implements IIntegrationEvent, stable type name
  • Published via IOutboxWriter.AddAsync (not the bus); no per-module eventing registration needed
  • Consumer handler sealed : IIntegrationEventHandler<T>; AddIntegrationEventHandlers(assembly) registered
  • Background readers restore tenant context; module Order lets the consumer load first
  • Build + tests green

© fullstackhero, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/add-integration-event of fullstackhero/dotnet-starter-kit.

Open the folder on GitHubat commit 0bd98e3

Compare with similar skills

Add Integration Event next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Add Integration Event compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Add Integration Event this skillfullstackhero/dotnet-starter-kit6.8k—~1.1kAutomated safety check: PassMIT
Dynamo Webview Component ScaffoldDynamoDS/Dynamo2k—~991Automated safety check: PassApache-2.0
Nx Generatenomcopter/react-mosaic4.8k6 repos~1.9kAutomated safety check: PassCustom licence
Nextjs App Architecturejakubwarkusz/themes1231 repos~2.5kAutomated safety check: PassMIT
Better FullstackMarve10s/Better-Fullstack752—~1.5kAutomated safety check: PassMIT
Pixijs Createpixijs/pixijs-skills347—~3.1kAutomated safety check: PassMIT

Similar skills

  • Scaffolds a new Dynamo package repo that hosts a view extension with a WebView2-embedded React frontend.

    2k GitHub stars~991 tokensUpdated today
    DevelopmentAuto-check passed
  • Nx Generate

    nomcopter/react-mosaic

    Generate code using nx generators. An agent skill from nomcopter/react-mosaic.

    4.8k GitHub starsUsed in 6 repos~1.9k tokens
    DevelopmentAuto-check passed
  • Nextjs App Architecture

    jakubwarkusz/themes

    Build or audit Next.js 16 App Router apps using a next-beats-style React Server Components architecture.

    123 GitHub starsUsed in 1 repo~2.5k tokens
    DevelopmentAuto-check passed
  • Better Fullstack

    Marve10s/Better-Fullstack

    Scaffold, plan, or extend Better Fullstack projects with the generator, CLI, or MCP server.

    752 GitHub stars~1.5k tokensUpdated today
    DevelopmentAuto-check passed
  • Pixijs Create

    pixijs/pixijs-skills

    A skill your agent uses when scaffolding a new PixiJS v8 project with the create-pixi CLI or adding PixiJS to an existing project.

    347 GitHub stars~3.1k tokensUpdated 6 days ago
    DevelopmentAuto-check passed
  • Senior Fullstack

    davila7/claude-code-templates

    Comprehensive fullstack development skill for building complete web applications with React, Next.js, Node.js, GraphQL, and PostgreSQL.

    32k GitHub starsUsed in 6 repos~1.1k tokens
    DevelopmentAuto-check: notes

More from fullstackhero/dotnet-starter-kit

All 11 skills in this repo
  • Add Entity

    fullstackhero/dotnet-starter-kit

    Add a domain entity/aggregate with EF configuration and a migration to an existing FSH module.

    6.8k GitHub stars~1.2k tokensUpdated 7 days ago
    Auto-check passed
  • Add Feature

    fullstackhero/dotnet-starter-kit

    Add a vertical-slice feature (command/query + handler + validator + endpoint) to an existing FSH module.

    6.8k GitHub stars~1.1k tokensUpdated 7 days ago
    Auto-check passed
  • Add Full Slice

    fullstackhero/dotnet-starter-kit

    Build a capability end-to-end — backend vertical slice (Contracts→handler→validator→endpoint) AND the React page wired to it.

    6.8k GitHub stars~783 tokensUpdated 7 days ago
    Auto-check passed
  • Add Module

    fullstackhero/dotnet-starter-kit

    Create a new module (bounded context) — runtime + Contracts projects, IModule, DbContext, permissions, migrations, and the four registration sites.

    6.8k GitHub stars~1.5k tokensUpdated 7 days ago
    Auto-check passed
  • Add Permission

    fullstackhero/dotnet-starter-kit

    Add a new permission end-to-end — server constant + endpoint gate, and (admin app) mirror it into the permissions catalog + route guard.

    6.8k GitHub stars~849 tokensUpdated 7 days ago
    Auto-check passed
  • Add React Page

    fullstackhero/dotnet-starter-kit

    Add a list+create page to a React app (clients/admin or clients/dashboard) — API module, page, lazy route, (admin) permission gate, Playwright test.

    6.8k GitHub stars~1.5k tokensUpdated 7 days ago
    Auto-check passed

Works with

Questions about Add Integration Event

What does Add Integration Event do?

Publish a cross-module integration event via the Outbox and handle it idempotently in another module. Add Integration Event is an agent skill from fullstackhero/dotnet-starter-kit. Publish a cross-module integration event via the Outbox and handle it idempotently in another module.

When should I use Add Integration Event?

Add Integration Event fits situations like: one module must react to something that happened in another; tasks that involve Project scaffolding.

How do I install Add Integration Event in Claude Code?

Run `npx skills add fullstackhero/dotnet-starter-kit --skill add-integration-event -a claude-code`. Or copy the skill folder (.agents/skills/add-integration-event in fullstackhero/dotnet-starter-kit) into .claude/skills/add-integration-event in your project. Claude Code loads it when a task matches its description.

How do I install Add Integration Event in Codex?

Run `npx skills add fullstackhero/dotnet-starter-kit --skill add-integration-event -a codex`. Or copy the skill folder (.agents/skills/add-integration-event in fullstackhero/dotnet-starter-kit) into .agents/skills/add-integration-event in your project. Codex loads it when a task matches its description.

Can I use Add Integration Event in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add fullstackhero/dotnet-starter-kit --skill add-integration-event -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/add-integration-event, .gemini/skills/add-integration-event, .github/skills/add-integration-event and .opencode/skills/add-integration-event in your project.

What does Add Integration Event need to run?

SKILL.md names no scripts, command-line tools or credentials: Add Integration Event is instructions for the agent only.

Does Add Integration Event access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Add Integration Event safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Add Integration Event use?

Add Integration Event is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Add Integration Event use?

About 1.1k tokens (SKILL.md is roughly 4.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Add Integration Event?

Skills that share tags, products or a category with Add Integration Event: Dynamo Webview Component Scaffold (DynamoDS/Dynamo, 2k stars), Nx Generate (nomcopter/react-mosaic, 4.8k stars), Nextjs App Architecture (jakubwarkusz/themes, 123 stars) and Better Fullstack (Marve10s/Better-Fullstack, 752 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Add Integration Event?

fullstackhero (a GitHub organization) maintains it in fullstackhero/dotnet-starter-kit, which has 6,813 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on September 30, 2026.

Source: fullstackhero/dotnet-starter-kit on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.