Data Ownership and Distributed Transactions (SAHP Chapter 9)

After a monolithic database is broken apart, the pieces have to work together again. This skill helps an agent decide which service owns each table, resolve tables that several services write, recognize when a business request has become a distributed transaction, and pick an eventual consistency pattern with its error handling. Every choice here trades consistency, performance, coupling and change cost against each other; present the trade-off, recommend, and record it as an ADR.

What does this entry provide?

Data Ownership and Distributed Transactions (SAHP Chapter 9) is an agent skill entry in ChatHome Skills, sourced from GitHub Skill Search and scored 53/100. # Data Ownership and Distributed Transactions (SAHP Chapter 9) ## Purpose After a monolithic database is broken apart, the pieces have to work together again. T. As an agent skill, it packages a reusable instruction set that AI coding agents such as Codex and Claude Code can load to perform this task without hand-written glue code. ChatHome Skills discovered this entry through its daily ingest of official registries and GitHub discovery queries, and re-verifies repository facts, freshness signals, and install metadata on every run. The quality score weighs official-registry presence, a working install command, license clarity, GitHub star trajectory, and repository freshness — the full formula is on the Sources page. The install command above is ready to copy. Review the last-pushed date and repository status before adding Data Ownership and Distributed Transactions (SAHP Chapter 9) to a production agent workflow; the snapshot facts below are point-in-time values from the most recent ingest.

Snapshot facts

Source: GitHub Skill Search
Quality: 53/100
Install method: codex
Repo: sauloleite/booksasskills
Repo updated: Nov 3, 2026

Install command

codex skill install sauloleite/booksasskills

Install method: codex

Review the upstream source before running this command.

GitHub project

Quality

Repo stars

Repo updated

Unknown

How is this score calculated?

Weighted across six dimensions, scored 0-100.
Provenance (25): listed in an official or curated registry.
Installability (25): a runnable install command beats a declared transport, which beats a source checkout.
Maintenance (20): recency of the last push; archived entries score zero here.
Adoption (20): repository stars on a log curve.

Security signals

Scan coverage: Install metadata and the indexed document body.

Automated signals from install metadata and a bounded skill body — not a full code security audit and not a recursive source or dependency review.

Discovery note

# Data Ownership and Distributed Transactions (SAHP Chapter 9) ## Purpose After a monolithic database is broken apart, the pieces have to work together again. This skill helps an a

Report an issue with this listing