immich-sdcard-sync-prune
Skill1 starsChanged 9 days agoNo licenceView on GitHub
This skill should be used when building or debugging a macOS launchd automation that uploads a camera SD card's contents to Immich on insert (via @immich/cli), or when building a workflow to prune Immich assets that were deleted from their source card/folder after import. Covers the Immich CLI's non-obvious API key permission requirements (album.create vs albumAsset.create, the "Found 0 new files" scoped-key bug), launchd's StartOnMount trigger and its missing-Homebrew-PATH gotcha, parsing `immich upload -j` JSON output, the Immich bulk-delete (trash vs permanent) endpoint, and — critically — why a delete/prune workflow across multiple source cards feeding one album must scope its diff by a per-source manifest rather than diffing the whole album, or a second card mounted alone will make every surviving photo from the first card look deletable. Trigger phrases include "sd card to immich", "immich cli upload", "@immich/cli permissions", "albumAsset.create", "Found 0 new files and 0 duplicates", "launchd StartOnMount", "immich upload -j json output", "immich bulk delete trash", "DELETE /api/assets force", "prune immich assets deleted from card", "multiple sd cards same immich album".
- Installs packages
In this repository81 other files it gives its agents.
- agent-command-approval-gateSkill
- agent-delivery-canarySkill
- agents-sdkSkill
- agent-vault-credential-brokerSkill
- anthropic-admin-cost-apiSkill
- artifact-font-embeddingSkill
- backblaze-b2-rclone-backupSkill
- better-documentsSkill
- caddy-cloudflare-wildcard-proxySkill
- cdp-layout-verificationSkill
- claritySkill
- claude-code-headless-tool-restrictionSkill
- claude-code-remote-control-hostSkill
- cloudflare-cron-telegram-alertSkill
- cloudflare-email-serviceSkill
- cloudflare-one-migrationsSkill
- cloudflare-oneSkill
- cloudflare-pages-gotchasSkill
- cloudflare-r2-rclone-backupSkill
- cloudflare-r2-restic-backupSkill
- cloudflareSkill
- cloudflare-workers-cron-emailSkill
- cloudflare-worker-tailscale-shieldSkill
- credential-rotation-protocolSkill
- cross-agent-filesystem-exchangeSkill
- debian-kernel-reboot-checkSkill
- docker-vpn-killswitch-lxcSkill
- durable-objectsSkill
- filament-panel-themingSkill
- forced-outage-drillSkill
- forgejo-deploymentSkill
- grafana-api-token-provisioningSkill
- grafana-prometheus-alertingSkill
- hermes-agent-deploymentSkill
- home-assistantSkill
- homelab-terminal-report-deliverySkill
- image-crop-focal-pointSkill
- infisical-secrets-managerSkill
- jellyfin-media-permissionsSkill
- jellyfin-proxmox-deploymentSkill
- laravel-filament-proxmox-lxcSkill
- n8n-workflow-api-authoringSkill
- ollama-macos-headlessSkill
- paperless-ngx-bare-metalSkill
- pause-handoff-emailSkill
- photo-site-album-ingestSkill
- pihole-dot-upstream-failoverSkill
- pihole-lists-doh-workerSkill
- pihole-local-dns-recordsSkill
- postmarkSkill
- proxmox-ansible-provisioningSkill
- proxmox-docker-compose-vmSkill
- proxmox-guest-egress-firewallSkill
- proxmox-node-systemd-serviceSkill
- proxmox-no-subscription-nagSkill
- proxmox-pbs-backup-jobSkill
- proxmox-terraform-provisioningSkill
- proxmox-vm-crash-diagnosisSkill
- proxmox-vm-igpu-passthroughSkill
- proxmox-vzdump-notificationsSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

