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

investigate-transfer

Skill2 starsChanged 7 months agoApache-2.0View on GitHub

Investigates a Newline banking transfer end-to-end by drilling through the transfer, its transactions, transaction events, any returns, and the combined transfer view. Use when asked to debug, trace, audit, or check the status of a transfer.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    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:

    If you have the transfer UID directly:

    line 12
  2. Distinctive:

    If you need to find it first:

    line 18
  3. Very specific:

    Look for events whose transaction_uid matches any of the transactions found in Step 2.

    line 55
  4. Very specific:

    Look for returns where original_transaction_uid matches a transaction from Step 2.

    line 64
  5. Distinctive:

    If a return is found:

    line 65
  6. Distinctive:

    If the transfer is part of a batch or grouped operation:

    line 71
  7. Very specific:

    Look for a combined transfer whose transfer_uids includes the transfer UID from Step 1.

    line 77

≈ “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

Investigate Transfer

Full drill-down workflow for understanding the state and history of a transfer.

Step 1 — Get the Transfer

If you have the transfer UID directly:

get-newline-transfer  uid=<transfer_uid>

If you need to find it first:

list-newline-transfers

Note from the transfer response:

  • status — current state of the transfer
  • transaction_uids — list of associated transaction UIDs
  • source_synthetic_account_uid and destination_synthetic_account_uid
  • initiating_customer_uid and destination_customer_uid
  • usd_transfer_amount
  • ach, wire, or instant_payment block — identifies the transfer type

Step 2 — Inspect Each Transaction

For every UID in transaction_uids, fetch the full transaction:

get-transaction  uid=<transaction_uid>

Note for each transaction:

  • status — e.g. settled, pending, failed
  • transaction_type
  • amount and currency
  • balance_after — running balance on the synthetic account after this entry
  • custodial_account_uid — the underlying custodial account

Step 3 — Check Transaction Events

Transaction events capture lifecycle state changes (initiated, settled, failed, returned, etc.):

list-transaction-events

Look for events whose transaction_uid matches any of the transactions found in Step 2. Pay attention to event_type and status for any failure or return indicators.

Step 4 — Check for Returns

list-returns

Look for returns where original_transaction_uid matches a transaction from Step 2. If a return is found:

  • Note return_reason, amount, status, and processed_at
  • See the return-resolution skill for next steps

Step 5 — Check the Combined Transfer View (Optional)

If the transfer is part of a batch or grouped operation:

list-combined-transfers

Look for a combined transfer whose transfer_uids includes the transfer UID from Step 1. The combined transfer shows total_amount and overall status across all constituent transfers.

Step 6 — Summarise Findings

Report back:

  1. Transfer status and type (Wire / ACH / Instant Payment)
  2. Amount and direction (source → destination account)
  3. Status of each transaction and whether all are settled
  4. Any transaction events indicating failures or state changes
  5. Whether any returns exist and their reasons
  6. The combined transfer status if applicable

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.