How do I install the Passkit skill?

Run npx skillmds@latest add caglarbaranbora/passkit in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Passkit safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Passkit?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Passkit free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Passkit?

caglarbaranbora (@caglarbaranbora) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Passkit by caglarbaranbora — Agent Skill

Name: Passkit
Author: caglarbaranbora

Passkit

Route PassKit implementation tasks to the correct Knowledge Contracts -- pass library querying/adding, .pkpass/pass.json content and required fields, the add-to-Wallet UI flow, pass updates and the app-vs-server push boundary, and Apple Pay payment requests plus authorization/result handling. Use when calling PKPassLibrary.isPassLibraryAvailable()/containsPass(_:)/passes()/passes(of:)/addPasses(_:withCompletionHandler:), authoring pass.json (formatVersion/passTypeIdentifier/serialNumber/teamIdentifier/organizationName/description, boardingPass/coupon/eventTicket/storeCard/generic, PassFields, barcodes, locations/relevantDates), inspecting a pass with PKPass(data:), presenting AddPassToWalletButton/PKAddPassesViewController/PKAddPassButton, wiring webServiceURL/authenticationToken, or building/presenting Apple Pay with PKPaymentRequest, PKPaymentAuthorizationController/PKPaymentAuthorizationViewController, PayWithApplePayButton/PKPaymentButton, PKPaymentAuthorizationControllerDelegate, PKPayment/PKPaymentToken

File contents

PassKit — Foundations Skill

Purpose

Route PassKit implementation tasks to the minimum required PassKit Knowledge Contracts. v1 scope is app-side Wallet-pass querying/adding, .pkpass/pass.json structure, the add-to-Wallet UI flow, the app-vs-server pass-update boundary, and building/presenting Apple Pay -- not server-side pass signing or certificate management, not NFC/secure-element passes, not pass personalization, and not Apple Pay's server-side merchant validation or token decryption.

Routing

Load only the contracts relevant to the task. All paths relative to knowledge/passkit/.

Calling PKPassLibrary.isPassLibraryAvailable()/containsPass(_:)/passes()/passes(of:); adding held passes with addPasses(_:withCompletionHandler:); or asking why there's no EventKit-style permission gate -> pass-library-and-authorization.md
Authoring or validating pass.json (formatVersion/passTypeIdentifier/serialNumber/teamIdentifier/organizationName/description, the boardingPass/coupon/eventTicket/storeCard/generic style keys, PassFields groups, barcodes, locations/relevantDates); or inspecting a pass with PKPass(data:) -> pass-content-and-required-fields.md
Presenting AddPassToWalletButton (SwiftUI) or PKAddPassesViewController/PKAddPassButton (UIKit); checking canAddPasses(); or the delegate/dismissal pattern -> adding-passes-ui.md
Wiring webServiceURL/authenticationToken; or understanding the device-registration/push/update-fetch protocol and why the app registers for no PassKit push type -> pass-updates-and-push-registration.md
Building PKPaymentRequest; checking canMakePayments()/canMakePayments(usingNetworks:); or choosing PayWithApplePayButton/PKPaymentButton and PKPaymentAuthorizationController/PKPaymentAuthorizationViewController -> apple-pay-payment-request.md
Implementing PKPaymentAuthorizationControllerDelegate; handling PKPayment/PKPaymentToken in didAuthorizePayment(_:handler:); returning PKPaymentAuthorizationResult; or dismissing via paymentAuthorizationControllerDidFinish(_:) -> apple-pay-authorization-and-result-handling.md

Never load more than the contracts relevant to the specific question.

Stop Conditions

Stop and report if the requested topic has no matching Knowledge Contract in knowledge/passkit/ — do not guess or fall back to general knowledge. Server-side pass signing, certificate management, and the Pass Type ID/Apple Developer portal setup process are out of scope entirely -- not app-side Swift code, not planned as a contract here. PKAddSecureElementPassViewController and NFC/secure-element-backed passes (transit cards, car keys, driver's-license-in-Wallet) are out of scope entirely -- a distinct, more specialized subsystem, not yet built. PKPassPersonalization (the transit-pass personalization flow) is out of scope entirely -- niche, not yet built. Apple Pay server-side merchant validation, payment-token decryption, and payment-processor integration are out of scope entirely -- report that this boundary exists and is server-side rather than routing to a contract here or fabricating a client-side decryption API.

---name: passkitdescription: Route PassKit implementation tasks to the correct Knowledge Contracts -- pass library querying/adding, .pkpass/pass.json content and required fields, the add-to-Wallet UI flow, pass updates and the app-vs-server push boundary, and Apple Pay payment requests plus authorization/result handling. Use when calling PKPassLibrary.isPassLibraryAvailable()/containsPass(_:)/passes()/passes(of:)/addPasses(_:withCompletionHandler:), authoring pass.json (formatVersion/passTypeIdentifier/serialNumber/teamIdentifier/organizationName/description, boardingPass/coupon/eventTicket/storeCard/generic, PassFields, barcodes, locations/relevantDates), inspecting a pass with PKPass(data:), presenting AddPassToWalletButton/PKAddPassesViewController/PKAddPassButton, wiring webServiceURL/authenticationToken, or building/presenting Apple Pay with PKPaymentRequest, PKPaymentAuthorizationController/PKPaymentAuthorizationViewController, PayWithApplePayButton/PKPaymentButton, PKPaymentAuthorizationControllerDelegate, PKPayment/PKPaymentToken---# PassKit — Foundations Skill## PurposeRoute PassKit implementation tasks to the minimum required PassKitKnowledge Contracts. v1 scope is app-side Wallet-pass querying/adding,`.pkpass`/`pass.json` structure, the add-to-Wallet UI flow, theapp-vs-server pass-update boundary, and building/presenting Apple Pay --not server-side pass signing or certificate management, notNFC/secure-element passes, not pass personalization, and not Apple Pay'sserver-side merchant validation or token decryption.## RoutingLoad only the contracts relevant to the task. All paths relative toknowledge/passkit/.- Calling `PKPassLibrary.isPassLibraryAvailable()`/`containsPass(_:)`/`passes()`/`passes(of:)`; adding held passes with `addPasses(_:withCompletionHandler:)`; or asking why there's no EventKit-style permission gate -> pass-library-and-authorization.md- Authoring or validating `pass.json` (`formatVersion`/`passTypeIdentifier`/`serialNumber`/`teamIdentifier`/`organizationName`/`description`, the `boardingPass`/`coupon`/`eventTicket`/`storeCard`/`generic` style keys, `PassFields` groups, `barcodes`, `locations`/`relevantDates`); or inspecting a pass with `PKPass(data:)` -> pass-content-and-required-fields.md- Presenting `AddPassToWalletButton` (SwiftUI) or `PKAddPassesViewController`/`PKAddPassButton` (UIKit); checking `canAddPasses()`; or the delegate/dismissal pattern -> adding-passes-ui.md- Wiring `webServiceURL`/`authenticationToken`; or understanding the device-registration/push/update-fetch protocol and why the app registers for no PassKit push type -> pass-updates-and-push-registration.md- Building `PKPaymentRequest`; checking `canMakePayments()`/`canMakePayments(usingNetworks:)`; or choosing `PayWithApplePayButton`/`PKPaymentButton` and `PKPaymentAuthorizationController`/`PKPaymentAuthorizationViewController` -> apple-pay-payment-request.md- Implementing `PKPaymentAuthorizationControllerDelegate`; handling `PKPayment`/`PKPaymentToken` in `didAuthorizePayment(_:handler:)`; returning `PKPaymentAuthorizationResult`; or dismissing via `paymentAuthorizationControllerDidFinish(_:)` -> apple-pay-authorization-and-result-handling.mdNever load more than the contracts relevant to the specific question.## Stop ConditionsStop and report if the requested topic has no matching KnowledgeContract in knowledge/passkit/ — do not guess or fall back to generalknowledge. Server-side pass signing, certificate management, and thePass Type ID/Apple Developer portal setup process are out of scopeentirely -- not app-side Swift code, not planned as a contract here.`PKAddSecureElementPassViewController` and NFC/secure-element-backedpasses (transit cards, car keys, driver's-license-in-Wallet) are out ofscope entirely -- a distinct, more specialized subsystem, not yet built.`PKPassPersonalization` (the transit-pass personalization flow) is outof scope entirely -- niche, not yet built. Apple Pay server-side merchantvalidation, payment-token decryption, and payment-processor integrationare out of scope entirely -- report that this boundary exists and isserver-side rather than routing to a contract here or fabricating aclient-side decryption API.

Frequently asked questions