Skip to content
Back to skills

Cardano Cli Transactions

ASecurity

Build, sign, and submit standard (non-script) transactions with cardano-cli, including change, fees, and TTL/validity.

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 27, 2026
tools

Works with

  • cli

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned September 27, 2026

npx -y skills add David-Li0406/meta-skill-evloving --skill cardano-cli-transactions --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Cardano Cli Transactions?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Cardano Cli Transactions
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/david-li0406-cardano-cli-transactions/badge)](https://www.skillsdirectory.com/skills/david-li0406-cardano-cli-transactions)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: cardano-cli-transactions
description: "Build, sign, and submit standard (non-script) transactions with cardano-cli, including change, fees, and TTL/validity."
---

# cardano-cli-transactions

## When to use
- Use when you need to send ADA or native assets, manage UTxOs, or do offline/online signing workflows.

## Operating rules (must follow)
- Confirm the user's network (mainnet vs preprod/preview) and **magic** before generating commands.
- Print commands in **copy/paste blocks**. Keep secrets out of logs.
- For any `cardano-cli` command: verify syntax with `cardano-cli --help` (and era help) and adjust if needed.
- Use fresh protocol parameters from the target network when calculating fees or script execution units.

## Workflow
1) Gather inputs
   - Sender address + signing key path
   - Recipient address
   - Amount (lovelace) and optional asset bundle
   - Target network flags

2) Query UTxOs and choose inputs
   - Prefer consolidating inputs intentionally (avoid accidental dust).
   - Calculate change output.

3) Fetch protocol parameters
   - Dump pparams to file (fresh from network).

4) Build tx body
   - Use `transaction build` (online) when possible.
   - Use `build-raw` only for offline/cold-key workflows.

5) Sign + submit
   - Create witness set (or full signed tx) and submit.
   - Verify by querying UTxO for recipient and checking tx hash.

6) Produce a reproducible “tx bundle” folder
   - tx.raw / tx.body, pparams.json, witnesses, and a command log.


## Safety / key handling
- Never expose signing keys.
- Confirm the destination address (checksum mindset).
- On mainnet: recommend a small test transfer first.


## References used by this skill
- `shared/PRINCIPLES.md` (repo)

Files in this skill

  • SKILL.md1.7 KB
  • reference/tx-send-ada.md902 B

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…