Skip to content
TrustedSkillsbeta
Back to all skills

Transaction Correctness

Checked
tursodatabase·vlatest·database·MIT

This skill verifies transactions for accuracy by comparing data against a database, ensuring data integrity and preventing errors.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add tursodatabase/turso --skill transaction-correctness -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

tursodatabase

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned tursodatabase/turso at 64b8ef5742.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
64b8ef5742
Manifest
.claude/skills/transaction-correctness/SKILL.md
Scanned
1 file, 87 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The transaction-correctness skill ensures that database transactions are handled accurately and consistently, preventing data corruption or inconsistencies during operations like inserts, updates, or deletes. It enforces ACID (Atomicity, Consistency, Isolation, Durability) properties to maintain reliable data integrity.

When to use it

  • When performing financial transactions where accuracy is critical
  • During multi-step database operations that require atomic execution
  • In applications handling user accounts or inventory systems where partial updates could cause errors

Key capabilities

  • Enforces ACID compliance for database transactions
  • Prevents race conditions and data inconsistencies
  • Ensures all operations within a transaction are completed successfully or rolled back entirely

Example prompts

  • "Verify that the payment processing transaction is correct and consistent."
  • "Ensure that the inventory update operation follows ACID principles."
  • "Check if the user account creation process maintains data integrity during multi-step transactions."

Tips & gotchas

  • Ensure your database system supports ACID compliance before using this skill.
  • Be mindful of performance trade-offs, as enforcing strict transaction correctness can increase overhead.