Backend Transactional Outbox

Use when the user asks about the transactional outbox, when a database write and a Kafka publish get out of sync, dual writes, reliable event publishing, Debezium outbox or a message relay. Produces outbox table, relay and consumer dedupe. Not for event schema design (use backend-event-driven).

45 stars 6 forksSoftware Development

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add j4flmao/agent-skills --skill backend-transactional-outbox
Manual install
git clone --depth 1 https://github.com/j4flmao/agent-skills.git /tmp/agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/agent-skills/skills/backend/universal/transactional-outbox ~/.claude/skills/backend-transactional-outbox

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Backend Transactional Outbox

## Purpose
Guarantee reliable event publication by writing events to an outbox table within the same database transaction as the business operation, then publishing them via a separate message relay process.

## Agent Protocol

### Trigger
Exact user phrases: "outbox", "transactional outbox", "outbox pattern", "reliable event publishing", "dual write", "CDC outbox", "message relay", "publish events", "exactly-once publish", "debezium outbox".

### Input Context
- Database technology (PostgreSQL, MySQL, SQL Server, etc.).
- Message broker (Kafka, RabbitMQ, SQS, etc.).
- Whether dual-write (DB + broker) is a current problem.
- Current event publishing mechanism.

### Output Artifact
Outbox implementation design as text. No file unless requested.

### Response Format
```
Outbox table: {table schema}
Write strategy: {same transaction|CDC}
Relay: {polling|CDC|transaction log}
Delivery: {at-least-once|exactly-once}
Consumer dedup: {key and storage}
```

### Completion Criteria
- [ ] Outbox table created in the same database as business data.
- [ ] Business operation and outbox insert are in the same DB transaction.
- [ ] Message relay process is separate from the application.
- [ ] Outbox records are deleted or marked processed after successful publish.
- [ ] Relay handles failures with retry and backoff.
- [ ] Consumers are idempotent (handle duplicate deliveries).
- [ ] Monitoring in place for outbox backlog.

### Max Response Length
Read the full skill on GitHub

Details

Skill name
backend-transactional-outbox
Path
skills/backend/universal/transactional-outbox/SKILL.md
License
MIT
Repo updated
17 November 2026

FAQ

What does the Backend Transactional Outbox skill do?

Use when the user asks about the transactional outbox, when a database write and a Kafka publish get out of sync, dual writes, reliable event publishing, Debezium outbox or a message relay. Produces outbox table, relay and consumer dedupe. Not for event schema design (use backend-event-driven).

How do I install the Backend Transactional Outbox skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add j4flmao/agent-skills --skill backend-transactional-outbox. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Backend Transactional Outbox popular?

It lives in j4flmao/agent-skills, which has 45 GitHub stars and 6 forks.

Related skills

Agent Observability

45

j4flmao/agent-skills

Use when the user asks about agent observability, tracing agent reasoning, debugging an agent loop, OpenTelemetry GenAI spans for LLM calls, LLM cost tracking per agent, agent audit logs or hallucination/eval monitoring in production. Produces instrumentation config, trace schema, dashboards, alerts and cost attribution. Not for generic service tracing without LLMs (use devops-opentelemetry).

DevOps & Cloud

AI Agent Architectures

45

j4flmao/agent-skills

Use when the user asks to build an AI agent, design an agent that calls tools and keeps memory, write an agent system prompt or pick an agent framework (Claude Agent SDK, OpenAI Agents SDK, LangGraph). Produces an architecture brief covering loop, tools, memory, guardrails and evals, routing depth to child skills. Not for workflow patterns (use ai-agentic-workflows).

AI, LLMs & Agents

AI Agent Core Loop

45

j4flmao/agent-skills

Use when the user asks about the agent loop, ReAct vs plan-and-solve, re-planning, Reflexion, an agent stuck in a loop, max iterations or termination conditions. Produces a loop spec or patch with state, success predicate, caps and no-progress detection. Not for overall agent design (use ai-agent-architectures) or tool schemas (use tool-calling-principles).

AI, LLMs & Agents

Backend Web Real Time

45

j4flmao/agent-skills

Use when the user asks about WebRTC, building a video call feature, SFU vs MCU, signaling servers, TURN/STUN, LiveKit or mediasoup, simulcast or live streaming latency. Produces real-time media architecture and signaling code. Not for chat-style WebSocket messaging (use backend-websocket-patterns).

Software Development

Backend Structured Logging

45

j4flmao/agent-skills

Use when the user asks about structured logging, JSON logs, Pino, Winston, Serilog, structlog, correlation IDs, log levels, log sampling or PII redaction in logs. Produces a logging setup with a field schema. Not for tracing pipelines (use observability) or audit trails (use backend-audit-logging).

Software Development

Backend Webhooks

45

j4flmao/agent-skills

Use when the user asks about webhooks, receiving Stripe or GitHub webhooks safely, verifying webhook signatures (HMAC), sending outgoing webhooks, retries or replay protection. Produces webhook receiver and delivery code. Not for payment flows themselves (use ecommerce-payment-processing).

Software Development

Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.