How do I install the Photos skill?

Run npx skillmds@latest add caglarbaranbora/photos 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 Photos 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 Photos?

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 Photos free to use?

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

Who published Photos?

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

Photos by caglarbaranbora — Agent Skill

Name: Photos
Author: caglarbaranbora

Photos

Route Photos and PhotoKit implementation tasks to the correct Knowledge Contracts -- picking assets with no authorization, requesting library access and its usage-description keys, the limited library, fetching assets, requesting images, and writing to the library. Use when presenting PhotosPicker or PHPickerViewController, configuring PHPickerConfiguration/selectionLimit/PHPickerFilter, reading PHPickerResult.itemProvider or assetIdentifier or PhotosPickerItem, calling PHPhotoLibrary.requestAuthorization(for:) or authorizationStatus(for:), declaring NSPhotoLibraryUsageDescription/NSPhotoLibraryAddUsageDescription, handling PHAuthorizationStatus.limited or presentLimitedLibraryPicker(from:), fetching with PHFetchOptions/PHFetchResult, requesting images through PHImageManager/PHCachingImageManager, or saving with performChanges and PHAssetCreationRequest. v1 is library access, reading, and saving only -- no photo editing (PHContentEditingInput/Output), no PHLivePhotoView, no AVAsset export, and no camera captu

File contents

Photos — Foundations Skill

Purpose

Route Photos and PhotoKit implementation tasks to the minimum required Photos Knowledge Contracts. v1 scope is reaching the user's photo library: selecting assets with no permission at all, requesting access when selection is not enough, behaving correctly under limited access, reading assets and their images, and writing new ones — not editing photos, not playing Live Photos or video, and not capturing from the camera.

Routing

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

Presenting PhotosPicker or PHPickerViewController; setting selectionLimit/maxSelectionCount or a PHPickerFilter; reading PHPickerResult.itemProvider/assetIdentifier or a PhotosPickerItem -> picker-and-selection-results.md
Calling PHPhotoLibrary.requestAuthorization(for:handler:)/authorizationStatus(for:); choosing PHAccessLevel.addOnly vs .readWrite; declaring NSPhotoLibraryUsageDescription/NSPhotoLibraryAddUsageDescription; branching on PHAuthorizationStatus -> authorization-and-access-levels.md
Handling PHAuthorizationStatus.limited; calling presentLimitedLibraryPicker(from:); setting PHPhotoLibraryPreventAutomaticLimitedAccessAlert -> limited-library.md
Building a PHFetchOptions query; holding or refreshing a PHFetchResult; fetching a PHAssetCollection's members; reading where a photo was taken from PHAsset.location -> asset-fetching.md
Calling PHImageManager.requestImage(...); setting PHImageRequestOptions' isSynchronous/deliveryMode/isNetworkAccessAllowed; priming a PHCachingImageManager -> image-requests.md
Running performChanges(_:completionHandler:); creating with PHAssetChangeRequest/PHAssetCreationRequest; capturing placeholderForCreatedAsset -> saving-to-the-library.md

Never load more than the contracts relevant to the specific question. For how a usage-description string should be worded, route to skill.app-store-review-guidelines.submission. For whether to show a pre-permission screen and what it says, route to skill.human-interface-guidelines.foundations. For declaring photo data in PrivacyInfo.xcprivacy, route to skill.privacy.foundations.

Stop Conditions

Stop and report if the requested topic has no matching Knowledge Contract in knowledge/photos/ — do not guess or fall back to general knowledge. Photo and video editing (PHContentEditingInput, PHContentEditingOutput, adjustment data, Photo Editing extensions), PHLivePhotoView, AVAsset export from a PHAsset, and PHAssetResource-level resource copying are out of scope entirely (see docs/architecture/domain-map.md). Capturing a new photo from the camera is AVFoundation's and has no Skill yet — report that rather than answering.

A photo's recorded capture place is this domain's, not core-location's, even though PHAsset.location is typed as a CLLocation: asset-fetching.md Rule 5 owns it, including the authorization question. Route to core-location only when the task needs the device's current or ongoing location, which is a different subject.

SwiftUI interop with this domain is split deliberately, and the split is this Skill's: PhotosPicker is SwiftUI-native, so picker-and-selection-results.md Rule 2 forbids wrapping the picker, while presentLimitedLibraryPicker(from:) takes a UIViewController and has no SwiftUI counterpart, so limited-library.md Rule 5 requires a bridge. How any such wrapper is written belongs to uikit-interaction and is not restated here.

---name: photosdescription: Route Photos and PhotoKit implementation tasks to the correct Knowledge Contracts -- picking assets with no authorization, requesting library access and its usage-description keys, the limited library, fetching assets, requesting images, and writing to the library. Use when presenting PhotosPicker or PHPickerViewController, configuring PHPickerConfiguration/selectionLimit/PHPickerFilter, reading PHPickerResult.itemProvider or assetIdentifier or PhotosPickerItem, calling PHPhotoLibrary.requestAuthorization(for:) or authorizationStatus(for:), declaring NSPhotoLibraryUsageDescription/NSPhotoLibraryAddUsageDescription, handling PHAuthorizationStatus.limited or presentLimitedLibraryPicker(from:), fetching with PHFetchOptions/PHFetchResult, requesting images through PHImageManager/PHCachingImageManager, or saving with performChanges and PHAssetCreationRequest. v1 is library access, reading, and saving only -- no photo editing (PHContentEditingInput/Output), no PHLivePhotoView, no AVAsset export, and no camera captu---# Photos — Foundations Skill## PurposeRoute Photos and PhotoKit implementation tasks to the minimum requiredPhotos Knowledge Contracts. v1 scope is reaching the user's photolibrary: selecting assets with no permission at all, requesting accesswhen selection is not enough, behaving correctly under limited access,reading assets and their images, and writing new ones — not editingphotos, not playing Live Photos or video, and not capturing from thecamera.## RoutingLoad only the contracts relevant to the task. All paths relative toknowledge/photos/.- Presenting `PhotosPicker` or `PHPickerViewController`; setting `selectionLimit`/`maxSelectionCount` or a `PHPickerFilter`; reading `PHPickerResult.itemProvider`/`assetIdentifier` or a `PhotosPickerItem` -> picker-and-selection-results.md- Calling `PHPhotoLibrary.requestAuthorization(for:handler:)`/`authorizationStatus(for:)`; choosing `PHAccessLevel.addOnly` vs `.readWrite`; declaring `NSPhotoLibraryUsageDescription`/`NSPhotoLibraryAddUsageDescription`; branching on `PHAuthorizationStatus` -> authorization-and-access-levels.md- Handling `PHAuthorizationStatus.limited`; calling `presentLimitedLibraryPicker(from:)`; setting `PHPhotoLibraryPreventAutomaticLimitedAccessAlert` -> limited-library.md- Building a `PHFetchOptions` query; holding or refreshing a `PHFetchResult`; fetching a `PHAssetCollection`'s members; reading where a photo was taken from `PHAsset.location` -> asset-fetching.md- Calling `PHImageManager.requestImage(...)`; setting `PHImageRequestOptions`' `isSynchronous`/`deliveryMode`/`isNetworkAccessAllowed`; priming a `PHCachingImageManager` -> image-requests.md- Running `performChanges(_:completionHandler:)`; creating with `PHAssetChangeRequest`/`PHAssetCreationRequest`; capturing `placeholderForCreatedAsset` -> saving-to-the-library.mdNever load more than the contracts relevant to the specific question.For how a usage-description string should be *worded*, route to`skill.app-store-review-guidelines.submission`. For whether to show apre-permission screen and what it says, route to`skill.human-interface-guidelines.foundations`. For declaring photo datain `PrivacyInfo.xcprivacy`, route to `skill.privacy.foundations`.## Stop ConditionsStop and report if the requested topic has no matching KnowledgeContract in knowledge/photos/ — do not guess or fall back to generalknowledge. Photo and video editing (`PHContentEditingInput`,`PHContentEditingOutput`, adjustment data, Photo Editing extensions),`PHLivePhotoView`, `AVAsset` export from a `PHAsset`, and`PHAssetResource`-level resource copying are out of scope entirely (seedocs/architecture/domain-map.md). Capturing a new photo from the camerais AVFoundation's and has no Skill yet — report that rather thananswering.A photo's recorded capture place is this domain's, not `core-location`'s,even though `PHAsset.location` is typed as a `CLLocation`:asset-fetching.md Rule 5 owns it, including the authorization question.Route to `core-location` only when the task needs the *device's* currentor ongoing location, which is a different subject.SwiftUI interop with this domain is split deliberately, and the split isthis Skill's: `PhotosPicker` is SwiftUI-native, sopicker-and-selection-results.md Rule 2 *forbids* wrapping the picker,while `presentLimitedLibraryPicker(from:)` takes a `UIViewController`and has no SwiftUI counterpart, so limited-library.md Rule 5 *requires*a bridge. How any such wrapper is written belongs to `uikit-interaction`and is not restated here.

Frequently asked questions