use-link-identity Skill (Stripe) for Claude: What It Does and How to Install It
Makes Claude use Link CLI to get an agent attestation token or present signed claims such as email to a service.
- Installs
- 10.9K
- on skills.sh
- Stars
- 889
- on GitHub
- Updated
- Oct 2026
- last repo commit
use-link-identity makes Claude use the Link CLI's identity commands when a service asks for a Link Agent Attestation Token (AAT) or signed user claims such as email. It fetches or lists attestations, requests an identity credential, and presents only the claims the service asked for, then hands the exact proof to an HTTP client or browser automation. SKILL.md marks these commands as beta.
It needs Link Agent Wallet v0.27.0 or later. Only the request commands need Link sign-in; list, pop and present work on local files in your home directory. SKILL.md points to the create-payment-credential skill for authentication, so install the set.
Good for
- Agent builders whose agents must prove they came through Link
- Developers answering a service's attestation or identity challenge
- Teams that want to share only selected claims, such as email
Install use-link-identity
Claude Code
- 1
Copy this prompt.
Install the use-link-identity skill in Claude Code. Run this command: npm i -g @stripe/link-cli Then check that it loaded and tell me how to use it.
- 2
Paste it into Claude Code. It shows the change and asks before running it.
Requires Node.js.
Pick one route. All routes need the link-cli tool (version 0.27.0 or later for identity commands) installed first. The skills CLI route installs the repo's 3 skills: create-payment-credential, financial-insights and use-link-identity. The plugin route installs the link plugin: those 3 skills and an MCP server entry that runs link-cli --mcp. This skill's identity commands run through the CLI, not the MCP tools.
From the project README. Source.
What's in the skill
When it loads
Use Link CLI's identity commands when a service requests a Link Agent Attestation Token (AAT) or signed user claims such as email. Covers acquiring and managing attestations, obtaining identity credentials, and presenting selected claims to a verifier through an HTTP client or browser automation.
Sections in SKILL.md
- Setup and handling
- Attestations
- Credentials and presentations
- Send and recover
Key facts
- License
- MIT
- Installs on skills.sh
- 10,941 (Nov 2, 2026)
- Last repo commit
- Oct 30, 2026
- What it includes
- 1 file: SKILL.md
What it includes
Show attestation inventory from local files
Check errors and attestations; only entries with storage 'pool' can be popped.
Files ·
identity attestations listRefill the pool with 1 to 100 tokens
Needs Link sign-in. Appends to ~/.link-cli/identity/attestations/pool.json, or use --output-file for a batch outside the pool.
Write ·
identity attestations requestTake one token and return the Authorization value
Removes the token locally and returns a header value that starts with PrivateToken. Use it verbatim.
Write ·
identity attestations popCheck credentials, expiry and claim names
Reads local files; look at errors, expired, expires_at and claim_names.
Files ·
identity credentials listGet a signed credential bound to a holder key
Needs Link sign-in. Replaces ~/.link-cli/identity/credentials/current.json and creates or reuses holder-key.jwk.
Write ·
identity credentials requestSign selected claims for an audience and nonce
Requires --aud, --nonce and at least one --claim. Returns a presentation for the Identity-Presentation header.
Write ·
identity credentials presentRules for headers, retries and common errors
Set headers only for the intended endpoint, avoid redirects that forward proofs, and report success only after the service accepts the request.
Read ·
Send and recover
From the official docs
Permissions
Medium risk
What it can do
- Read your data
- Create and change things
- Delete things
- Read-only mode
Watch out for
It discloses signed claims such as email
credentials present signs the claims you select for an audience and nonce. Check that the audience belongs to the intended service and share only the claims the task needs. github.com
Link sign-in can include payment access
By default the README says login requests userinfo:read and payment_methods.agentic scopes plus financial-insights actions. Use the README's flags to leave out access you do not need. github.com
Keys and proofs sit on disk
The holder key and credential are stored under your home directory. SKILL.md advises restrictive permissions for handoff files and keeping proofs out of logs. github.com
The plugin route adds an MCP server entry
The link plugin's .mcp.json runs link-cli --mcp, and the plugin carries all 3 Link skills including payment credentials. Use the skills-only route if you only want identity. github.com
Security advisories
No published security advisories as of Nov 2, 2026.
Technical details
| Turning on read-only | No read-only mode. The list commands only read local files. |
|---|---|
| Talks to | api.link.com (shown as the issuer in SKILL.md's example output). The service you present a proof to |
| Sign-in and keys | README: link-cli auth login signs you in to Link. Identity files live in ~/.link-cli/identity and are cached per home directory, so use separate home directories for different users. |
| Scopes |
|
Questions
What does the use-link-identity skill do?
It makes Claude use Link CLI's identity commands when a service asks for a Link attestation token or signed user claims. An attestation proves Link issued the token without disclosing user claims. A presentation discloses the selected claims.
How do I install use-link-identity?
Use the install box at the top of this page. Install the link-cli tool first, then the skills or the plugin. Identity commands need Link Agent Wallet v0.27.0 or later.
Do I need a Link account?
For the request commands, yes. SKILL.md says only request needs Link authentication, while list, pop and present use local files. The README says Link CLI is for US and Canadian Link accounts for now.
Is this the skill for payments?
No. Payments are handled by the create-payment-credential skill in the same repo. This skill points to it for authentication guidance. Link sign-in by default asks for payment and financial-insights access too, and the README shows how to leave those out.
Does it work through the MCP server?
No. SKILL.md says identity commands are available through the CLI, not its MCP tools. The plugin route also adds an MCP server entry, which this skill does not use.
Does it work in Codex or the Claude app?
The README gives no Codex or Claude app install steps. The repo has a Codex plugin manifest, but SKILL.md needs the link-cli tool on your machine, so use a client that can run commands.
Which claims can it share?
Only claims listed in your credential's claim_names. SKILL.md's example presents email, and it says to repeat --claim only for extra claims the task authorizes and not to disclose the raw credential.
Is it safe?
Installing it copies one SKILL.md. Using it makes Claude run link-cli in your shell and handle tokens and signed claims. SKILL.md says to keep proofs, private keys and claim values out of transcripts and logs, and to send them only to the intended endpoint. Check the audience and nonce before presenting.
Information
updated Nov 2, 2026
- Repository
- stripe/link-cli
- Folder
skills/use-link-identity
Sources
Docs, issue trackers and discussions this page is built from.
Show all 6Hide
- use-link-identity SKILL.md · github.com
- stripe/link-cli README · github.com
- link-cli marketplace.json · github.com
- link plugin.json · github.com
- link plugin .mcp.json · github.com
- create-payment-credential SKILL.md · github.com