link-cli

Installs and authenticates Link CLI for agent payments and financial insights.

750|105|Updated Apr 23, 2026
One-click install
npx skills add https://github.com/stripe/link-cli --skill link-cli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: link-cli
Source: https://github.com/stripe/link-cli/tree/main/skills/link-cli
Command: npx skills add https://github.com/stripe/link-cli --skill link-cli

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @stripe/link-cli.

What problem does it solve?

Setting up Link CLI requires choosing the right OAuth scopes and source actions for your use case, then completing a multi-step approval flow. This Skill guides agents through installation, authentication status checks, scope selection, and user approval so Link access is configured correctly the first time.

Core Features & Use Cases

  • Use-case detection: Determines whether the user needs agent payments, financial insights, or both, and recommends a default when intent is unclear.
  • Authentication management: Runs auth status first, then uses auth login or auth upgrade to request the correct scopes (userinfo:read, payment_methods.agentic) and source actions without dropping existing access.
  • Approval flow handling: Presents verification URLs, polls for approval via _next commands, and hands off to the create-payment-credential or financial-insights skills once authenticated.
  • Use Case: A user asks their agent to start making purchases with Link. The Skill checks auth status, initiates login with the payment scopes, walks the user through approval in the Link app, and then hands off to the payment credential skill.

Quick Start

Use the link-cli skill to set up and authenticate Link CLI so I can make agent payments and view financial insights.

Frequently Asked Questions about link-cli

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up Link CLI for agent payments?

Install Link CLI with npm install -g @stripe/link-cli, then run link-cli auth status to check for an active session. If none exists, run auth login with the scopes userinfo:read and payment_methods.agentic, present the verification URL to the user, and poll until approval completes.

How do I authenticate Link CLI for financial insights?

Run auth login or auth upgrade with the userinfo:read scope plus one --source-actions flag per needed insight, such as read_link_transactions, read_balances, read_external_transactions, or read_source_details. Complete the approval flow before querying any financial data.

What is the difference between auth login and auth upgrade in Link CLI?

Use auth login when there is no active session, and auth upgrade when a session exists but needs broader scopes or source actions. Upgrade merges new permissions with existing grants and keeps the current session valid until the new approval completes.

Can I use Link CLI without installing it globally?

Yes, replace every link-cli command with npx @stripe/link-cli@latest to run it without a global install. All commands, flags, and authentication flows work identically through npx.

Why does Link CLI authentication stop at a verification URL?

Authentication is a multi-step approval flow requiring the user to approve access in their Link app. Present the verification_url clearly, then run the returned _next.command to poll for approval, or add --interval 5 --timeout 300 for inline polling.