financial-insights

The saved excerpt is a snapshot from when this skill was listed. The external source remains the complete and most current version.

---
version: 0.15.1
name: financial-insights
description: |
  Reads a user's Link financial data — transactions, balances, and wallet sources — so agents can answer questions about spending and available source capabilities. Use when the user says "check my balance", "how much did I spend", "show my transactions", "what accounts are connected", "summarize my spending", "recent purchases", or asks about their financial activity, account balances, or linked sources.
allowed-tools:
 - Bash(link-cli:*)
 - Bash(npx --yes @stripe/link-cli:*)
 - Bash(npx @stripe/link-cli:*)
 - Bash(npm install -g @stripe/link-cli:*)
license: Complete terms in LICENSE
metadata:
  author: stripe
  url: link.com/agents
  openclaw:
    emoji: "📊"
    homepage: https://link.com/agents
    requires:
      bins:
        - link-cli
    install:
      - kind: node
        package: "@stripe/link-cli"
        bins: [link-cli]
user-invocable: true
---

# Financial insights

Use this skill to answer questions about a user’s Link-connected financial data, including:

- Recent transactions
- Spending patterns
- Account balances
- Linked wallet sources
- Basic summaries derived from the user’s financial data

All commands are read-only. They do not move money, initiate payments, modify accounts, or expose payment credentials.

## Safety and privacy

Do not retrieve financial data until the user is authenticated with the required source actions.

Only retrieve the data needed to answer the user’s request. Do not run every list command by default.

Do not expose sensitive identifiers, access tokens, credentials, or payment instrument details. Summarize financial information at the level needed to answer the user’s question.

If the user asks for an action that would move money, reference `skills/create-payment-credential/SKILL.md` instead.

## Authentication

Before retrieving financial data, check whether the user is authenticated and whether the current session has the required source actions.

```bash
link-cli auth status --format json
```

When present, inspect `authorization_details` in the response for entries with `type: "source"` and the required actions. The field may be absent when the token endpoint did not return authorization details or when authentication comes from `LINK_ACCESS_TOKEN`; in that case, run only the minimum data command needed and handle a permission error as described below.

If the user is not authenticated, start a login that requests only the source actions needed for the requested data. If the user is already authenticated but one or more required source actions are missing, use `auth upgrade` instead of `auth login`. `auth upgrade` preserves the current session while the user approves the additional access and replaces it only after approval succeeds.

Use the minimum required source actions:

- Transactions processed through Link: `read_link_transactions`
- Transactions imported from bank connections: `read_external_transactions`
- Account balances: `read_balances`
- Data source details and descriptions: `read_source_details`

If the user asks a question that requires multiple data types, request all relevant actions together.

Example for a new login that needs all financial data types:

```bash
link-cli auth login \
  --client-name "<your-agent-name>" \
  --source-actions read_link_transactions \
  --source-actions read_balances \
  --source-actions read_external_transactions \
  --source-actions read_source_details \
  --format json
```

Example for adding balance access to an existing session:

```bash
link-cli auth upgrade \
  --client-name "<your-agent-name>" \
  --source-actions read_balances \
  --format json
```

Replace `<your-agent-name>` with a clear name for the agent or application. Present the returned `verification_url` to the user, then follow the response's `_next` instruction or poll with:

```bash
link-cli auth status --interval 5 --max-attempts 60 --format json
```

Do not proceed until authentication or the acc