Try it
Add the skill to a bot, then ask your Chief of Staff:
“Use the Go Error Handling skill on this: [describe the job, or paste your notes].”
This decouples your domain from the persistence library. If you later swap pgx for the standard database/sql, callers do not change. The tradeoff is that the original pgx error information is lost below the sentinel -- log it before wrapping if the original error carries useful diagnostic data (e.g., a pgx PgError with a Code field).
What it covers
- Error Handling Analysis: UserService Three-Layer Stack