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.
In this repository9 other files it gives its agents.
- account-reconciliationSkill
- create-transferSkill
- customer-overviewSkill
- making-paymentsSkill
- managing-users-and-accountsSkill
- new-account-setupSkill
- payment-operationsSkill
- return-resolutionSkill
- transaction-reportingSkill
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
- Distinctive: line 12
If you have the transfer UID directly:
- Distinctive: line 18
If you need to find it first:
- Very specific: line 55
Look for events whose transaction_uid matches any of the transactions found in Step 2.
- Very specific: line 64
Look for returns where original_transaction_uid matches a transaction from Step 2.
- Distinctive: line 65
If a return is found:
- Distinctive: line 71
If the transfer is part of a batch or grouped operation:
- Very specific: line 77
Look for a combined transfer whose transfer_uids includes the transfer UID from Step 1.
≈ “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.
Files
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-transfersNote from the transfer response:
status— current state of the transfertransaction_uids— list of associated transaction UIDssource_synthetic_account_uidanddestination_synthetic_account_uidinitiating_customer_uidanddestination_customer_uidusd_transfer_amountach,wire, orinstant_paymentblock — 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,failedtransaction_typeamountandcurrencybalance_after— running balance on the synthetic account after this entrycustodial_account_uid— the underlying custodial account
Step 3 — Check Transaction Events
Transaction events capture lifecycle state changes (initiated, settled, failed, returned, etc.):
list-transaction-eventsLook 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-returnsLook for returns where original_transaction_uid matches a transaction from Step 2.
If a return is found:
- Note
return_reason,amount,status, andprocessed_at - See the
return-resolutionskill for next steps
Step 5 — Check the Combined Transfer View (Optional)
If the transfer is part of a batch or grouped operation:
list-combined-transfersLook 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:
- Transfer status and type (Wire / ACH / Instant Payment)
- Amount and direction (source → destination account)
- Status of each transaction and whether all are settled
- Any transaction events indicating failures or state changes
- Whether any returns exist and their reasons
- The combined transfer status if applicable
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
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.

