TRIGGER when user asks to listen for, subscribe to, or handle an event emitted by another microservice.
$ npx skills add microbus-io/fabric --skill add-inbound-event -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install microbus-io/fabric add-inbound-event --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/microbus-io/fabric.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/microbus/add-inbound-event .claude/skills/add-inbound-event && rm -rf skills-srcUse ~/.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/
Install the "add-inbound-event" agent skill from https://github.com/microbus-io/fabric/tree/main/.claude/skills/microbus/add-inbound-event into .claude/skills/add-inbound-event/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-inbound-event", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/microbus-io/fabric/tree/main/.claude/skills/microbus/add-inbound-eventType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add microbus-io/fabric --skill add-inbound-event -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install microbus-io/fabric add-inbound-event --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/microbus-io/fabric.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/microbus/add-inbound-event .agents/skills/add-inbound-event && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "add-inbound-event" agent skill from https://github.com/microbus-io/fabric/tree/main/.claude/skills/microbus/add-inbound-event into .agents/skills/add-inbound-event/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-inbound-event", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add microbus-io/fabric --skill add-inbound-event -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install microbus-io/fabric add-inbound-event --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/microbus-io/fabric.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/microbus/add-inbound-event .cursor/skills/add-inbound-event && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "add-inbound-event" agent skill from https://github.com/microbus-io/fabric/tree/main/.claude/skills/microbus/add-inbound-event into .cursor/skills/add-inbound-event/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-inbound-event", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/microbus-io/fabric.git --path .claude/skills/microbus/add-inbound-event--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add microbus-io/fabric --skill add-inbound-event -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install microbus-io/fabric add-inbound-event --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/microbus-io/fabric.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/microbus/add-inbound-event .gemini/skills/add-inbound-event && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "add-inbound-event" agent skill from https://github.com/microbus-io/fabric/tree/main/.claude/skills/microbus/add-inbound-event into .gemini/skills/add-inbound-event/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-inbound-event", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install microbus-io/fabric add-inbound-eventInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add microbus-io/fabric --skill add-inbound-event -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/microbus-io/fabric.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/microbus/add-inbound-event .github/skills/add-inbound-event && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "add-inbound-event" agent skill from https://github.com/microbus-io/fabric/tree/main/.claude/skills/microbus/add-inbound-event into .github/skills/add-inbound-event/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-inbound-event", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add microbus-io/fabric --skill add-inbound-event -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install microbus-io/fabric add-inbound-event --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/microbus-io/fabric.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/microbus/add-inbound-event .opencode/skills/add-inbound-event && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "add-inbound-event" agent skill from https://github.com/microbus-io/fabric/tree/main/.claude/skills/microbus/add-inbound-event into .opencode/skills/add-inbound-event/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-inbound-event", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
add-inbound-eventTRIGGER when user asks to listen for, subscribe to, or handle an event emitted by another microservice.
Add Inbound Event is an agent skill from microbus-io/fabric. TRIGGER when user asks to listen for, subscribe to, or handle an event emitted by another microservice.
Its SKILL.md is about 1.4k 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 Backend & APIs, covering Microservices. The repository describes itself as: Microbus is the only fabric where every agentic workflow runs on a true microservice substrate - giving your workflows security, scale, observability, and prompt-driven authoring. The licence is Apache-2.0.
8 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit fb98098. It shows what the files ask for, not the result of running them.
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.
Shell commands in SKILL.md call:
goFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Add Inbound Event loads about 1.4k tokens when it runs. Until then it costs about 30 tokens; SKILL.md has 631 words of instructions outside code blocks.
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.
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.
The full file from microbus-io/fabric at commit fb98098, republished under its Apache-2.0 licence (© microbus-io). 631 words, ~1,375 tokens.
.claude/skills/add-inbound-event/SKILL.md (or your agent's skills folder).CRITICAL: Do NOT explore or analyze other microservices unless explicitly instructed to do so. The instructions in this skill are self-contained to this microservice.
CRITICAL: An inbound event sink is declared as a define.InboundEvent var in myserviceapi/definition.go referencing the source microservice's OutboundEvent, and implemented as a handler in service.go. Add the declaration and run cmd/genservice.
CRITICAL: Keep the // MARKER: OnMyEvent comment on the define.InboundEvent var.
CRITICAL: Inbound event sinks are not exposed via OpenAPI. The connector's built-in :888/openapi.json handler enforces this filter automatically.
Copy this checklist and track your progress:
Creating or modifying an inbound event sink:
- [ ] Step 1: Read local CLAUDE.md file
- [ ] Step 2: Locate the source outbound event and determine the signature
- [ ] Step 3: Determine a description
- [ ] Step 4: Declare the inbound event in definition.go
- [ ] Step 5: Generate the boilerplate
- [ ] Step 6: Implement the sink in service.go
- [ ] Step 7: Test the inbound event sink
- [ ] Step 8: HousekeepingCLAUDE.md FileRead the local CLAUDE.md file in the microservice's directory. It contains microservice-specific instructions that should take precedence over global instructions.
Locate the define.OutboundEvent var in the api package of the microservice that is the source of the event. Note its package import path (e.g. github.com/company/project/eventsource/eventsourceapi) and its In/Out structs - the handler's signature is the source event's signature.
func OnMyEvent(ctx context.Context, input1 string, input2 ThirdPartyStruct) (output1 map[string]MyStruct, err error)Take the event's description from the source's OutboundEvent godoc. Use it for the godoc on this define.InboundEvent var.
definition.goAppend the define.InboundEvent var to myserviceapi/definition.go, referencing the source's OutboundEvent var. Add the import for the source api package.
import (
"github.com/microbus-io/fabric/define"
"github.com/company/project/eventsource/eventsourceapi"
)
/*
OnMyEvent is triggered when X.
*/
var OnMyEvent = define.InboundEvent{ // MARKER: OnMyEvent
Source: eventsourceapi.OnMyEvent,
}OnAUpdated, OnBUpdated) so the handler methods differSource is the typed reference to the source's OutboundEvent var, so a renamed or removed source event becomes a compile error hereLoadBalancing: define.None to process the event on every replica of this service (broadcast, e.g. cache invalidation), or LoadBalancing: "my-queue" for a named queue; omit for the default queue (one replica processes each delivery)RequiredClaims: "roles.user" to process the event only when its carried actor satisfies the expression; omit to accept allTimeBudget: 30 * time.Second to cap the handler's duration; add the "time" import if usedFrom the microservice's directory, run the generator. It regenerates intermediate.go (the hook wiring and ToDo entry), mock.go, mock_test.go, and manifest.yaml from the updated definition.go. It also scaffolds a placeholder handler in service.go and a placeholder test in service_test.go for any new feature that lacks one, each ready for you to fill in.
go run github.com/microbus-io/fabric/cmd/genservice .Then verify the microservice compiles with go vet ./... from the project root.
service.goThe previous step generated a placeholder sink handler func (svc *Service) OnMyEvent(...) in service.go, with its signature (the source event's signature, complex types referenced through the source api package) and godoc projected from definition.go, tagged // MARKER: OnMyEvent and holding a // TODO body. Fill in that body; leave the generated signature and godoc as they are. Add imports for any packages the body references that are not already present.
Skip this step if instructed to be "quick" or to skip tests.
The boilerplate generator created a placeholder test function TestMyService_OnMyEvent in service_test.go, tagged with a // MARKER: OnMyEvent comment and a HINT block. Add one or more test cases at the bottom of that function, following the pattern shown in its HINT comment. Do not remove the HINT comment.
If the feature or microservice cannot or should not be tested - for example, it starts a daemon or requires a
resource unavailable in the test environment - do not delete the generated test. The generator keys on the test
function's name and would scaffold it again on the next regeneration. Instead, replace the entire body of the
test with a t.Skip("reason") explaining why.
Follow the housekeeping skill.
© microbus-io, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in .claude/skills/microbus/add-inbound-event of microbus-io/fabric.
Open the folder on GitHubat commit fb98098
Add Inbound 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Add Inbound Event this skillmicrobus-io/fabric | 172 | — | ~1.4k | Automated safety check: Pass | Apache-2.0 | |
| Node Backend Development Guidelinesdiet103/claude-code-infrastructure-showcase | 10k | 2 repos | ~2k | Automated safety check: Pass | MIT | |
| Nodejs Backend Patternsever-works/ever-works | 162 | 18 repos | ~4k | Automated safety check: Pass | AGPL-3.0 | |
| AWS Serverless Edazxkane/aws-skills | 367 | 4 repos | ~3.2k | Automated safety check: Pass | MIT | |
| Golang Proantoniopaya22/go-rest-template | 172 | 3 repos | ~1.2k | Automated safety check: Pass | MIT | |
| Dr Jskilljdubois/dr-jskill | 342 | — | ~4.6k | Automated safety check: Notes | Apache-2.0 |
diet103/claude-code-infrastructure-showcase
Sets layered architecture and coding rules for Node.js, Express and TypeScript microservices, covering routes, controllers, services, repositories, Prisma, Sentry and Zod.
ever-works/ever-works
Build production-ready Node.js backend services with Express/Fastify, implementing middleware patterns, error handling, authentication, database integration, and API design best practices.
zxkane/aws-skills
AWS serverless and event-driven architecture expert based on Well-Architected Framework.
antoniopaya22/go-rest-template
Implements concurrent Go patterns using goroutines and channels, designs and builds microservices with gRPC or REST, optimizes Go application performance with pprof, and enforces idiomatic Go with…
jdubois/dr-jskill
Creates Java + Spring Boot projects: Web applications, full-stack apps with Vue.js or Angular or React or vanilla JS, PostgreSQL, REST APIs, and Docker.
getsentry/sentry
Generate hybrid cloud tests for the Sentry codebase. An agent skill from getsentry/sentry.
microbus-io/fabric
TRIGGER when user asks to add or modify a configuration property or setting, or to make a value configurable.
microbus-io/fabric
TRIGGER when user asks to add, create, or modify an API endpoint, function, or RPC, or a route that accepts typed arguments and returns typed results.
microbus-io/fabric
TRIGGER when user asks to add or modify a metric, counter, gauge, or histogram, or to track/measure an operation.
microbus-io/fabric
TRIGGER when user asks to fire, emit, or publish an event that other microservices can subscribe to.
microbus-io/fabric
TRIGGER when user asks to add a Python-backed function endpoint to an existing Python-backed microservice.
microbus-io/fabric
TRIGGER when user asks to create a microservice that calls Python, runs ML inference, or uses Python libraries (PyTorch, pandas, sentence-transformers, numpy) for its core compute.
Categories
TRIGGER when user asks to listen for, subscribe to, or handle an event emitted by another microservice. Add Inbound Event is an agent skill from microbus-io/fabric. TRIGGER when user asks to listen for, subscribe to, or handle an event emitted by another microservice.
Add Inbound Event fits situations like: user asks to listen for; handle an event emitted by another microservice.
Run `npx skills add microbus-io/fabric --skill add-inbound-event -a claude-code`. Or copy the skill folder (.claude/skills/microbus/add-inbound-event in microbus-io/fabric) into .claude/skills/add-inbound-event in your project. Claude Code loads it when a task matches its description.
Run `npx skills add microbus-io/fabric --skill add-inbound-event -a codex`. Or copy the skill folder (.claude/skills/microbus/add-inbound-event in microbus-io/fabric) into .agents/skills/add-inbound-event in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add microbus-io/fabric --skill add-inbound-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-inbound-event, .gemini/skills/add-inbound-event, .github/skills/add-inbound-event and .opencode/skills/add-inbound-event in your project.
Going by SKILL.md and its folder, Add Inbound Event needs the command-line tools its instructions call (go).
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.
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.
Add Inbound Event is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.4k tokens (SKILL.md is roughly 5.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Add Inbound Event: Node Backend Development Guidelines (diet103/claude-code-infrastructure-showcase, 10k stars), Nodejs Backend Patterns (ever-works/ever-works, 162 stars), AWS Serverless Eda (zxkane/aws-skills, 367 stars) and Golang Pro (antoniopaya22/go-rest-template, 172 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
microbus-io (a GitHub organization) maintains it in microbus-io/fabric, which has 172 GitHub stars. The repository holds 32 skills in this directory. The repository was last updated on September 28, 2026.
Source: microbus-io/fabric on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.
