agentleFS
newline53newline53/newline-mcp-server/skills/create-transfer/SKILL.md

create-transfer

Skill2 starsChanged 7 months agoApache-2.0View on GitHub

Creates a Newline banking transfer between two synthetic accounts. Handles all three transfer types: Wire, ACH, and Instant Payment. Use this skill when asked to send money, initiate a transfer, move funds, or create any Wire/ACH/Instant Payment between accounts.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 3 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    All three types share a common set of required fields, plus type-specific fields.

    line 9
  2. Distinctive:

    If you don't already have the customer UID, find it first:

    line 13
  3. Distinctive:

    If you only have one side, also check the destination customer's accounts:

    line 33
  4. Very specific:

    Call create-newline-transfer with all required fields:

    line 66
  5. Very specific:

    Only one of wire, ach, or instant_payment should be provided per transfer.

    line 87
  6. Very specific:

    Use a unique external_uid per request to prevent duplicate transfers.

    line 89

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Create Transfer

Guide for creating a Wire, ACH, or Instant Payment transfer via the Newline Banking API. All three types share a common set of required fields, plus type-specific fields.

Step 1 — Identify the Initiating Customer

If you don't already have the customer UID, find it first:

list-customers  (filter by name, email, or external_uid as needed)

Note the customer's uid — this becomes initiating_customer_uid.

Step 2 — Identify Source and Destination Accounts

Retrieve the synthetic accounts involved in the transfer:

get-synthetic-accounts

Note the uid of each account:

  • source_synthetic_account_uid — the account funds leave from
  • destination_synthetic_account_uid — the account funds arrive at

If you only have one side, also check the destination customer's accounts:

list-customers  (find destination customer)
get-synthetic-accounts

Step 3 — Choose Transfer Type and Gather Type-Specific Fields

Wire Transfer

Requires a wire object with:

  • wire_instructions — free-text wire routing instructions

ACH Transfer

Requires an ach object with:

  • sec_code — Standard Entry Class code (e.g. PPD, CCD, WEB)
  • service_processing — STANDARD or SAME_DAY
  • originator_name — name of the originating entity
  • company_id — ACH company identifier
  • prenote — true to send a prenote, false for a live entry
  • entry_description — up to 10-character description (e.g. PAYROLL)
  • effective_entry_date — desired settlement date (YYYY-MM-DD)
  • id_number — individual identification number

Instant Payment Transfer

Requires an instant_payment object with:

  • memo — payment memo / message to recipient
  • instant_payment_transmitter — object containing:
    • name, transmitter_identifier
    • street_number (integer), street1, street2, city, state, postal_code, country

Step 4 — Create the Transfer

Call create-newline-transfer with all required fields:

create-newline-transfer
  external_uid              — your own unique identifier for idempotency
  initiating_customer_uid   — from Step 1
  initiator_type            — "customer" in most cases
  source_synthetic_account_uid       — from Step 2
  destination_synthetic_account_uid  — from Step 2
  usd_transfer_amount       — amount as a string (e.g. "100.00")
  wire | ach | instant_payment       — exactly one, from Step 3

Step 5 — Confirm

The response includes the new transfer's uid and initial status. Share the transfer UID and status with the user. If the status is not yet settled, advise that it will update asynchronously.

Notes

  • Only one of wire, ach, or instant_payment should be provided per transfer.
  • usd_transfer_amount is a string, not a number (e.g. "250.00").
  • Use a unique external_uid per request to prevent duplicate transfers.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.