스킬 use-link-identity
📦

use-link-identity

콘텐츠 리비전 r1 안전 ⚙️ 외부 명령어🌐 네트워크 접근📁 파일 시스템 접근

Present Link Attestations and Identity Claims

Services can require agent attestations or signed identity claims before accepting a request. This skill guides Link CLI workflows for obtaining proofs and presenting authorized claims.

지원: Claude Codex Code(CC)
Maintain this Skill? Claim it 🥉 78 브론즈

내 에이전트로 설치

이 요청을 에이전트에 복사하세요. 공식 Skill 페이지와 매니페스트가 포함되어 있습니다.

에이전트 요청
Review the Skillstore skill "use-link-identity" from https://skillstore.io/skills/stripe-use-link-identity.md and its manifest at https://skillstore.io/api/skills/stripe-use-link-identity/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

에이전트는 계속해서 계획을 표시하고 보안 정책에서 요구하는 확인을 요청해야 합니다.

에이전트가 읽기 쉬운 리소스

AI 에이전트, 크롤러, 스크립트가 전체 페이지 대신 정리된 컨텍스트만 필요할 때 이 링크를 사용하세요.

테스트해 보기

"use-link-identity" 사용 중입니다. Explain how to respond when the attestation pool is empty.

예상 결과:

  • Request a new batch before attempting to pop a token.
  • Use the returned authorization value unchanged for the intended endpoint.
  • Keep token values out of transcripts and logs.

"use-link-identity" 사용 중입니다. Explain the checks before presenting my email claim.

예상 결과:

  • Confirm that a usable credential includes the email claim.
  • Validate the intended service audience and current nonce.
  • Select only the authorized email claim and keep the credential and holder key local.
  • Report success only after the service accepts the request.

보안 감사

안전
v1 • 2026. 10. 17. 버전별 보고서 열기

All 40 static findings are false positives in this documentation-only skill. Markdown formatting, expected identity storage, example URLs, and explicit secret-protection guidance explain the detections. No evidence found of prompt injection, unauthorized disclosure, or malicious execution in the reviewed file.

1
스캔된 파일
109
분석된 줄 수
0
검토 항목
0
오탐 무시됨
가장 최근에 완료된 정적·의미론적 감사에서 확인된 보안 발견 사항이 감지되지 않았습니다. 이는 스킬에 부작용이 없음을 증명하지 않습니다.
감사자: codex
이 보고서 공유 및 인용

버전이 지정된 평가 보고서, 중립 배지, 임베드 카드 및 인용을 공유하세요. Skillstore는 근거를 보고하지만 이 Skill의 안전 여부를 판단하지 않습니다.

버전별 보고서 열기
보안 평가

보고서 링크 복사

https://skillstore.io/skills/stripe-use-link-identity/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown 배지

[![Skillstore security assessment](https://skillstore.io/badges/skills/stripe-use-link-identity/security.svg)](https://skillstore.io/skills/stripe-use-link-identity?utm_source=security_passport_badge)

HTML 배지

<a href="https://skillstore.io/skills/stripe-use-link-identity?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/stripe-use-link-identity/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

임베드 카드

<iframe src="https://skillstore.io/embed/skills/stripe-use-link-identity.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
학술 인용 (APA · BibTeX · CFF)

APA 인용

stripe. (2026). use-link-identity security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/stripe-use-link-identity/audits/1

BibTeX 인용

@techreport{stripe-stripe-use-link-identity-2026, author = {stripe}, title = {use-link-identity security audit report (audit version 1)}, institution = {Skillstore}, year = {2026}, number = {1}, url = {https://skillstore.io/skills/stripe-use-link-identity/audits/1}, note = {Author version unspecified} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "use-link-identity security audit report (audit version 1)" version: "unspecified" type: report authors: - name: "stripe" date-released: "2026-10-17" url: "https://skillstore.io/skills/stripe-use-link-identity/audits/1" identifiers: - type: other value: "skillstore:stripe-use-link-identity:audit:1" description: "Skillstore immutable audit report identifier"

Skillstore 점수

이 점수의 이유 증거 신뢰도: 중간
55
아키텍처
85
유지보수성
87
콘텐츠
65
커뮤니티
91
사양 준수

만들 수 있는 것

Respond to an attestation challenge

Inspect the local pool, obtain an AAT when needed, and pass its authorization value to the intended endpoint.

Present an authorized email claim

Use a verified audience and nonce to present only the email claim requested by the service and authorized by the user.

Coordinate attestation allocation

Export an attestation batch and plan token ownership, concurrency, and cleanup outside the internal CLI pool.

이 프롬프트를 사용해 보세요

Inspect identity readiness
Check Link CLI version and local identity inventory. Report availability and errors without exposing tokens, private keys, or claim values.
Handle an attestation request
Handle the PrivateToken challenge for [endpoint]. Check inventory and refill only if needed. Send the exact authorization value without logging it.
Present selected claims
Present only my authorized email claim to [endpoint]. Validate its audience and nonce, use safe process arguments, and report only the acceptance status.
Plan multi-agent token handling
Plan an exported AAT batch for [worker count] workers. Address permissions, allocation, concurrency, cleanup, identity isolation, and retries. Do not request tokens yet.

모범 사례

  • Parse CLI JSON programmatically and keep proofs, private keys, and claim values out of transcripts and logs.
  • Validate the destination, audience, and nonce before presenting only claims authorized by the user.
  • Use separate home directories for different users and restrictive permissions for proof handoff files.

피하기

  • Manually reconstructing tokens or presentations, or including them in logs.
  • Using global browser headers or forwarding identity proofs across origins.
  • Assuming an authentication change switches cached identity, or disclosing raw credentials instead of selected claims.

자주 묻는 질문

What is the difference between an AAT and a presentation?
An AAT proves Link issuance without user claims. A presentation discloses selected claims and proves holder-key possession for an audience and nonce.
Which Link CLI version is required?
Use Link Agent Wallet v0.27.0 or later. Identity commands are in beta and do not require a preview flag.
Can I use these commands through Link MCP tools?
No. The documented identity commands are available through the CLI, not its MCP tools.
Which operations require Link authentication?
Only request operations require Link authentication. List, pop, and present use local files.
Does logging in as another user switch cached identity?
No. Cached identity belongs to the home directory. Use separate home directories for different users.
Can I reuse attestations and presentations?
Keep an AAT for retries within an existing interaction, subject to service rules. Use fresh challenges after nonce consumption or expiry.

개발자 세부 정보

작성자

stripe

라이선스

Complete terms at https://github.com/stripe/link-cli/blob/main/LICENSE

Skillstore 리비전

r1

버전 안내

작성자가 버전을 선언하지 않았습니다.

참조

8b0f5f59e50ec6f1de06321c2ecc77427561d561

유지보수 최신성

2026. 10. 17.

사용량

0 다운로드 · 0 조회

파일 구조

📄 SKILL.md

stripe의 다른 스킬

전체 보기
전체 보기