Explore skills
Search every indexed skill by name, description, repository or instructions, then narrow the results.
Showing 34591–34620 of 35202 skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| home-assistantjackson2w/claude-code-skillsThis skill should be used when configuring, troubleshooting, or extending a Home Assistant OS (HAOS) instance — installing add-ons/apps, editing configuration.yaml, setting up Tailscale/remote access, or troubleshooting onboarding, the Supervisor, or backups, or building automations/scripts/helpers/template switches/webhooks through HA's REST and websocket APIs. Trigger phrases include "Home Assistant add-on", "Home Assistant apps", "configuration.yaml", "HAOS", "Home Assistant Tailscale", "Supervisor", "HACS", "home assistant api", "create automation via api", "/api/config/automation/config", "input_boolean/create", "timer/create", "home assistant websocket", "template switch config flow", "webhook local_only", "ios shortcut webhook", "template value should be a string", "pause for 1 hour then revert". | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| homelab-terminal-report-deliveryjackson2w/claude-code-skillsThis skill should be used when building or modifying a homelab automation that needs to deliver a status report via email + Telegram + (optionally) a GitHub-hosted markdown archive — the shared report system (resilience-ledger-styled HTML as of 2026-08-17, previously Kanagawa-Wave-terminal-styled) already used by the weekly housekeeping sweep, the nightly backup summary, and the R2/B2 offsite sync emails. Also covers choosing between a minimal-link Telegram ping and a rich bulleted Telegram-as-primary-channel with conditional email (added 2026-08-20 to cut Postmark's 100/month free-tier quota). Trigger phrases include "homelab status report", "ledger styled email", "kanagawa wave email", "render-terminal-report", "homelab-report-lib", "consolidate emails into a digest", "add a new homelab report automation", "resilience-ledger design system", "claude_code_prompts schema", "push report to obsidian-vault", "deploy report script to a host other than ansible-ctrl", "raw ISO timestamp in email/telegram", "human readable local time in report", "send_rich_telegram_report", "postmark quota", "postmark free tier limit", "telegram primary channel", "bulleted telegram summary", "only email on warn or fail". | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| image-crop-focal-pointjackson2w/claude-code-skillsThis skill should be used when the user asks to "fix this crop", "the photo is cut off", "set a focal point", "the preview is offset", "recrop this image", "the thumbnail cuts off the head", or any task requiring picking a normalized (x, y) focal point or CSS background-position so a specific subject stays in frame when an image is cropped to a different aspect ratio than its source. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| immich-sdcard-sync-prunejackson2w/claude-code-skillsThis 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". | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| infisical-secrets-managerjackson2w/claude-code-skillsThis skill should be used when migrating a credential off a plaintext .env file onto self-hosted Infisical (the fleet secrets-management platform — distinct from Agent Vault, its separate MITM-proxy product), when provisioning a new host's Infisical machine identity, when debugging an `infisical-wrapper.sh`/`infisical-get.sh` fetch failure, or when auditing which fleet credentials still live in plaintext. Trigger phrases include "infisical secrets get empty", "secret not found exit 0", "*not found* infisical", "infisical secrets manager", "infisical-wrapper.sh", "infisical-get.sh", "infisical machine identity", "infisical login universal-auth", "homelab-fleet project", "migrate credential to infisical", "retire .env file", "Injecting N Infisical secrets", "infisical secrets get", "lookup('pipe', '/root/bin/infisical-get.sh", "deployed-copy vs git-tracked-source". | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| jellyfin-media-permissionsjackson2w/claude-code-skillsThis skill should be used when Jellyfin shows "Playback failed due to a fatal player error" for a newly-added title, when a library item has empty/stub metadata (title from the folder name only, no overview/poster/runtime), or when media was ingested via an rsync pipeline from macOS. Trigger phrases include "fatal player error", "jellyfin playback failed", "jellyfin permission denied", "jellyfin metadata empty", "openrsync chown", "rsync macOS uid gid Linux permissions". | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| jellyfin-proxmox-deploymentjackson2w/claude-code-skillsThis skill should be used when deploying (or redeploying) Jellyfin on a Proxmox host as an unprivileged LXC with Intel QuickSync hardware transcoding passthrough — including the VM-vs-LXC decision for a shared iGPU, the manual device-passthrough steps Terraform can't do declaratively, the media-volume backup-exclusion pattern, and the Tailscale-Serve-only exposure model. Trigger phrases include "deploy jellyfin", "reinstall jellyfin", "jellyfin quicksync passthrough", "jellyfin proxmox LXC", "renderD128 jellyfin", "jellyfin hardware transcoding setup", "redeploy jellyfin from scratch". | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| laravel-filament-proxmox-lxcjackson2w/claude-code-skillsThis skill should be used when deploying a Laravel + Filament v3 app (an admin panel, internal dashboard, or CMDB) as a native systemd service inside an unprivileged Proxmox LXC, instead of Docker — dedicated PHP-FPM pool, Caddy loopback front, Pest testing, Laravel Boost, Laravel Nightwatch APM, and adding a read-only Sanctum token API for an external consumer. Also covers a Filament panel behind Tailscale Serve generating mixed-content http:// asset URLs on an https:// page (including a plain asset() call not honoring URL::forceScheme), Eloquent's belongsToMany pivot-table naming surprising an agent building the schema by hand, php-fpm socket permission errors from a restrictive service-user home directory, Boost's guideline generation silently doing nothing under --no-interaction, Sanctum's abilities/ability middleware aliases not existing on a bootstrap/app.php (no Kernel.php) app, and an unauthenticated api/* request 500ing instead of 401ing when no Accept header is sent. For theming/skinning an already-deployed panel (custom colors, self-hosted fonts, brand name), see the sibling `filament-panel-theming` skill instead. Trigger phrases include "laravel filament proxmox", "filament admin panel native install", "php-fpm dedicated pool ansible", "laravel behind tailscale serve mixed content", "APP_URL forceScheme https", "asset() secure true mixed content", "eloquent belongsToMany pivot table wrong name", "credential_service vs service_credential", "laravel nightwatch systemd agent", "boost:install no agents selected", "pest --init not pest:install", "php-fpm socket permission denied caddy", "sanctum personal access token read only", "Target class [abilities] does not exist", "sanctum middleware alias missing", "Route [login] not defined api", "unauthenticated api request 500", "redirectGuestsTo bootstrap/app.php", "FilamentUser canAccessPanel api-only user", "APP_DEBUG true production laravel". | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| macos-pre-erase-auditjackson2w/claude-code-skillsThis skill should be used before a Mac is erased, traded in, sold or handed down, to check over SSH what would be lost — whether iCloud Drive (incl. Desktop & Documents), iCloud Photos, Messages in iCloud, Notes and Voice Memos are fully synced, and what lives only locally (Trash, Downloads, app data, keys, credentials). Also covers the fleet cleanup after. Trigger phrases include "trade in my mac", "erase my mac", "before I wipe", "anything I should back up", "sell my mac mini", "is everything in icloud", "photos not uploaded", "decommission a mac". | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| n8n-workflow-api-authoringjackson2w/claude-code-skillsThis skill should be used when authoring an n8n workflow as JSON to import via n8n's REST API (rather than hand-clicking in the editor), when an n8n HTTP Request node's attached credential seems to be silently ignored, when an n8n Code node throws "Module 'X' is disallowed", when a `{{ }}` expression field throws a bare "invalid syntax", when downstream Code node fields go missing/undefined after an HTTP Request node, when importing/updating an n8n workflow via `POST`/`PUT /api/v1/workflows` hits errors like "active is read-only", "PATCH method not allowed", or a referenced error-workflow name not resolving, when a Wait-node-delayed check using `$getWorkflowStaticData` gives a stale/wrong answer, or when decoding n8n's SQLite `execution_data` for debugging without an API key. Trigger phrases include "n8n workflow JSON", "n8n REST API import", "n8n credential not working", "n8n expression invalid syntax", "n8n Module crypto is disallowed", "n8n HTTP Request neverError", "n8n workflow active read-only", "POST /api/v1/workflows", "getWorkflowStaticData stale", "n8n Wait node static data", "n8n execution_data flatted decode". | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| ollama-macos-headlessjackson2w/claude-code-skillsThis skill should be used when running Ollama headless on a Mac as an always-on service, when Ollama returns HTTP 403 to requests arriving through a reverse proxy or Tailscale Serve, when deciding whether to enable macOS auto-login for a headless box, when choosing a model size for an 8GB Apple Silicon machine, or when a Caddy reverse proxy returns HTTP 200 with an empty body. Trigger phrases include "ollama headless mac", "ollama 403 proxy", "ollama Host header", "OLLAMA_ORIGINS not working", "brew services doesn't start until login", "LaunchDaemon vs LaunchAgent", "mac mini always on service", "ollama tailscale serve", "8GB unified memory model size", "caddy 200 empty body", "caddy site matcher Host". | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| paperless-ngx-bare-metaljackson2w/claude-code-skillsThis skill should be used when installing, upgrading, or troubleshooting a Paperless-ngx deployment via its bare-metal (non-Docker) release tarball rather than Docker Compose — especially inside a Proxmox LXC. Trigger phrases include "paperless-ngx bare metal", "paperless-ngx without docker", "pip install requirements.txt paperless", "granian paperless", "PAPERLESS_BIND_ADDR", "mysqlclient pkg-config error", "liblept", "paperless-ngx tarball structure", "paperless systemd service", "paperless-webserver.service". | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| pause-handoff-emailjackson2w/claude-code-skillsThis skill should be used whenever a working session pauses rather than completes — when Will says "good pause point", "let's pause here", "I'll pick this up later", "that's enough for today", "wrapping up", "done for now", or hands work back while something is still mid-flight. It defines the pause-handoff email sent to Will covering unverified claims, owed work, phrases to resume each thread, and steps only he can run. Also applies when he asks to "email me the flags", "send me what's outstanding", "what do I need to do", or "how do I pick this up later". | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| photo-site-album-ingestjackson2w/claude-code-skills | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| pihole-dot-upstream-failoverjackson2w/claude-code-skillsThis skill should be used when adding DNS-over-TLS (DoT) as a Pi-hole upstream resolver, when evaluating cloudflared for DoT/DoH proxying, when a "no fallback DNS" or "DNS failures should surface" constraint needs to coexist with wanting resilience against a recursive resolver (e.g. Unbound) going down, when pihole-FTL --config dns.upstreams rejects an unquoted value as invalid JSON, or when designing an alerted (not silent) failover watcher for infrastructure that must not silently mask its own failures. Trigger phrases include "cloudflared proxy-dns", "cloudflared DoT deprecated", "pihole DNS over TLS", "stubby DoT", "pihole-FTL --config dns.upstreams", "dns.upstreams invalid JSON", "Unbound fallback resolver", "no fallback DNS constraint", "alerted failover watcher", "silent fallback DNS", "pihole upstream failover", "Quad9", "Unbound forward-zone DoT", "forward-tls-upstream", "switch Unbound from recursive to forwarding", "tls-cert-bundle certificate verify failed", "unbound reload vs restart", "serve-expired hides an upstream outage", "FTLCONF_dns_upstreams read-only", "docker Pi-hole upstream". | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| pihole-lists-doh-workerjackson2w/claude-code-skillsThis skill should be used when giving phones or tablets Pi-hole-style ad-blocking away from home without depending on a VPN/Tailscale tunnel. It covers serving Pi-hole's own lists as DNS-over-HTTPS from a Cloudflare Worker, iOS/iPadOS DNS-settings profiles (.mobileconfig) with SSID OnDemand rules, and the Worker's upstream (Cloudflare's security resolver over DoH since 2026-11-03; Quad9 DoT before). Built 2026-11-02 for Will (repo jackson2w/roaming-dns-worker, homelab-ansible roaming-dns.yml). Trigger phrases include "ad blocking on the go", "roaming DNS", "DoH Worker", "DNS over HTTPS cloudflare worker", "pihole lists cloudflare", "mobileconfig DNS profile", "com.apple.dnsSettings.managed", "OnDemandRules SSIDMatch", "iOS DNS profile not working", "Use Tailscale DNS settings", "Quad9 DoH 505", "HTTP Version Not Supported quad9", "cloudflare:sockets DoT", "error code 1010", "security.cloudflare-dns.com", "connect to 1.1.1.1 from worker", "Stream was cancelled", "Python-urllib 403 workers.dev", "Workers Builds name mismatch", "npm install-scripts approve workerd", "roaming-dns-canary", "roaming-dns-sync". | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| pihole-local-dns-recordsjackson2w/claude-code-skillsThis skill should be used when configuring Pi-hole so devices show by friendly name instead of raw IP in the dashboard/Top Clients/Query Log, when the "List of configured clients" (Group Management > Clients) Comment field doesn't seem to change any display elsewhere, when identifying an unlabeled/mystery device on the network without router access, when a dashboard label doesn't update even though the dns.hosts record looks correct, or when managing dns.hosts declaratively via Ansible. Trigger phrases include "pi-hole map traffic to devices", "pi-hole client names in dashboard", "pi-hole Local DNS Records", "dns.hosts pihole.toml", "pihole-FTL --config dns.hosts", "client comment not showing in dashboard", "pihole network table discover devices", "identify unknown device on network", "what is this IP/MAC", "dns-sd companion-link", "mdns bonjour identify device", "private wifi address randomized mac", "dashboard name not updating", "pihole query log lag", "dns.hosts restarts FTL", "maxDBdays not trimming". | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| postmarkjackson2w/claude-code-skillsThis skill should be used when the user asks to "send email via Postmark", "set up Postmark", "configure an SMTP relay with Postmark", "check Postmark delivery status", "use my Postmark account", or needs transactional email sending/delivery verification through Postmark's SMTP relay or HTTP API — including from non-Workers systems like Proxmox, cron jobs, or backend services that support a generic SMTP smarthost. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| proxmox-ansible-provisioningjackson2w/claude-code-skillsThis skill should be used when creating a new Proxmox LXC (pct create) or VM, writing or debugging Ansible playbooks that target Proxmox/Debian hosts (including Debian 13/trixie), or troubleshooting a Proxmox+Ansible workflow — a "storage 'local-lvm' does not exist" error, a "Systemd 257 detected" nesting warning, Ansible failing with a locale error inside a fresh LXC, an Ansible lineinfile task that keeps reporting changed on every run, writing multi-line config/YAML files to a remote host over SSH, an "apt-key or gpg binary is required" error from Ansible's apt_repository module, a Proxmox-family product (PVE/PBS/PMG) apt install failing with a 401 against enterprise.proxmox.com, Tailscale/anything needing `/dev/net/tun` stuck crash-looping inside an unprivileged LXC, any host device (GPU render node, USB dongle) bind-mounted into an unprivileged LXC showing up owned by `nobody:nogroup`, or an LXC's own dashboard/monitoring reporting a suspiciously high load average that doesn't match its actual workload. Trigger phrases include "pct create", "pvesm status", "local-lvm", "local-zfs", "unprivileged LXC", "nesting=1", "Ansible could not initialize the preferred locale", "lineinfile idempotency", "ansible-playbook --check failing", "pct exec", "apt-key deprecated", "apt_repository module failed", "enterprise repo 401 unauthorized", "pbs-enterprise.sources", "/dev/net/tun does not exist", "tailscaled activating auto-restart", "TUN passthrough LXC", "device passthrough nobody nogroup", "renderD128 permission denied LXC", "GPU passthrough unprivileged LXC", "chmod 666 dev dri", "loadavg LXC host contamination", "/proc/loadavg not namespaced", "LXC excessive load false alarm", "Jinja Syntax error Missing end of comment tag", "ansible template array length bash", "${#array[@]} jinja", "ansible --start-at-task check diff", "template drifted from live script". | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| proxmox-docker-compose-vmjackson2w/claude-code-skillsThis skill should be used when deploying an application that only ships via Docker Compose (no native/bare-metal install path — e.g. Immich, and similar multi-container stacks with a custom database extension baked into a maintained image) inside a Proxmox VM, managing its Docker Compose file and secrets as code via Ansible, debugging a Compose service that's unexpectedly reachable on the plain LAN IP instead of only over Tailscale Serve, wiring up a hardware-acceleration `extends:` stanza (hwaccel.yml, OpenVINO/VAAPI image tags) that ships commented-out in the upstream Compose file, or exposing one feature of an otherwise tailnet-only app (e.g. Immich share links) to people outside the tailnet via a purpose-built proxy sidecar + narrow Funnel rather than punching a hole in the app's own API. Also covers verifying an async first-run job (ML indexing, search embedding, etc.) actually processed something rather than just checking container health, and a shared Ansible `file` loop silently drifting a sensitive directory's mode. Trigger phrases include "tailscale serve nftables allowlist not working", "restrict tailnet peers serve", "docker compose in a proxmox vm", "immich docker deployment", "no bare-metal install path", "docker compose ports binds 0.0.0.0", "docker-proxy 0.0.0.0", "ansible deploy docker-compose.yml", "verify smart search indexed", "async job queued but not verified", "second disk for docker volumes proxmox", "hwaccel.yml extends", "immich openvino image tag", "docker compose hardware acceleration", "share immich link outside tailnet", "immich public proxy", "expose one path publicly without exposing the app", "funnel to a proxy not the app". | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| proxmox-guest-egress-firewalljackson2w/claude-code-skillsThis skill should be used when restricting a single Proxmox guest's outbound traffic with the Proxmox VE firewall — especially the first time the datacenter (cluster) firewall is enabled on a host where it has never been on. Covers the safe enable order (off files for the host and for any guest whose NIC already has firewall=1, ACCEPT defaults), a per-VM egress allowlist (DNS, NTP, HTTPS, Tailscale, RFC1918 drop), what breaks under it (apt over HTTP, NTP to the internet, direct tailnet paths), and positive/negative verification. Trigger phrases include "proxmox firewall egress", "restrict outbound for one vm", "pve firewall enable cluster", "cluster.fw", "vmid.fw", "policy_out DROP", "firewall=1 nic", "proxmox firewall lock out", "egress allowlist proxmox", "agentic service outbound restriction". | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| proxmox-no-subscription-nagjackson2w/claude-code-skillsThis skill should be used when a user on a no-subscription (free) Proxmox VE or Proxmox Backup Server install wants to suppress the "No valid subscription" login popup, or asks whether that popup indicates a real problem. Trigger phrases include "no valid subscription popup", "proxmox subscription nag", "remove subscription popup", "proxmox no-nag patch", "checked_command proxmoxlib.js". | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| proxmox-node-systemd-servicejackson2w/claude-code-skillsThis skill should be used when deploying a Node.js application (Next.js, n8n, or any pnpm/npm-based app) as a native systemd service inside an unprivileged Proxmox LXC, instead of Docker — installing Node via NodeSource, running a dedicated non-root service user, building with pnpm, and exposing it only over Tailscale Serve. Also covers debugging an Ansible playbook for this pattern that never reports `changed=0` on a repeat run, a "detected dubious ownership in repository" git error, a service that's unexpectedly reachable on the plain LAN IP instead of only over Tailscale, or an app that fails to write scratch/upload files under `/tmp` despite the service showing active. Trigger phrases include "run Node app as systemd service", "NodeSource install Ansible", "pnpm build systemd", "next start binds 0.0.0.0", "HOSTNAME env var not working Next.js", "ansible git dubious ownership", "git module changed every run", "recursive chown always changed ansible", "Docker-in-LXC alternative for Node app", "ProtectSystem strict /tmp ENOENT", "PrivateTmp systemd Node app", "npm install -g version bump not applying", "creates guard blocks upgrade", "bumping n8n_version does nothing", "ansible pinned npm package upgrade". | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| proxmox-pbs-backup-jobjackson2w/claude-code-skillsThis skill should be used when adding a new host (LXC or VM) to an existing Proxmox Backup Server nightly backup schedule, creating a vzdump job via `pvesh`, debugging a backup job that succeeds but the prune step fails with a permission error, excluding one specific mount point (e.g. a bulky media/data volume) from an LXC's backup while still backing up its rootfs, setting up PBS-to-PBS replication via a Remote + Sync Job (a second physical PBS instance holding a pulled copy of another datastore), a PBS API token that returns `{}` from `/access/permissions` despite a correct-looking ACL grant, `apt update` failing with `401 Unauthorized` against `enterprise.proxmox.com` on a no-subscription PBS install, or restore-testing a PBS datastore/replica by restoring to a throwaway VMID/CTID. Trigger phrases include "add backup job pvesh", "vzdump schedule new host", "pbs prune permission denied", "Datastore.Modify Datastore.Prune missing", "backup job finished with errors", "proxmox-backup-client prune permission check failed", "exclude mount point from backup", "mp0 backup=0", "vzdump exclude volume", "pbs remote sync job", "proxmox-backup-manager sync-job create", "pbs replica second instance", "pbs api token permissions empty", "access/permissions returns empty object", "pbs enterprise repo 401 unauthorized", "pbs-enterprise.sources", "restore test throwaway ctid", "pct restore verify backup", "querying namespaces failed permission check", "pbs sync job remove-vanished". | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| proxmox-terraform-provisioningjackson2w/claude-code-skills | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| proxmox-vm-crash-diagnosisjackson2w/claude-code-skills | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| proxmox-vm-igpu-passthroughjackson2w/claude-code-skillsThis skill should be used when passing an Intel iGPU (or other PCI device) through to a Proxmox VM via vfio-pci for hardware acceleration (transcoding, OpenVINO/ML inference, etc.) — as opposed to an LXC's simple device bind-mount. Covers checking IOMMU group isolation, host-side vfio-pci binding, the Terraform hostpci block, and guest-kernel-side gotchas (missing GPU drivers in cloud kernels, grub picking the wrong kernel, missing firmware). Trigger phrases include "vfio-pci passthrough", "IOMMU group", "pass GPU to proxmox VM", "hostpci vfio", "vainfo can't connect", "i915 declaring it wedged", "GuC firmware fetch failed", "cloud kernel missing i915", "grub boots wrong kernel same version", "intel_gpu_top", "OpenVINO GPU device", "linux-image-cloud-amd64 no gpu driver". | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| proxmox-vzdump-notificationsjackson2w/claude-code-skillsThis skill should be used when customizing Proxmox VE's notification templates (vzdump backup emails, replication, package-updates, test notifications) at /etc/pve/notification-templates/default/*.hbs, when a Handlebars template edit produces mangled output (missing spaces, unexpected blank lines), or when a notification needs to be tested without waiting for or triggering a real backup/replication job. Trigger phrases include "vzdump notification template", "customize backup email", "pve notification hbs", "notification-templates/default", "PVE::Notify", "guest-table hbs", "Handlebars trim eating space", "test proxmox notification without running backup", "human-bytes duration helper". | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| proxmox-zfs-root-mirrorjackson2w/claude-code-skillsThis skill should be used when a Proxmox host's root pool (`rpool`) is a single ZFS disk with no redundancy and needs to become a mirror, or when an existing 2-drive ZFS root mirror needs to be grown to use more of each drive's capacity — all live, without reinstalling Proxmox or restoring guests from backup. Trigger phrases include "add redundancy to rpool", "mirror the boot drive", "zfs root mirror no reinstall", "grow zfs root partition live", "zpool attach boot disk", "expand rpool without downtime", "convert single disk zfs to mirror", "replace boot drive keep guests running". | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| resilience-ledger-email-stylingjackson2w/claude-code-skillsThis skill should be used when sending or styling any transactional/notification email for Will (dfw, Olu, WordPress, or any future homelab automation) and it should carry the resilience-ledger design system look, when a new HTML email needs light+dark mode that actually works, or when debugging an email where dark mode text is invisible/low-contrast. Also load this before touching render-ledger-email.py, ledger-email-style.php, render-terminal-report.py's HTML output, or render-correspondence-email.py (Claude Code's own prose emails to Will, markdown-in/HTML-out, entities distinguished by shape not colour). Trigger phrases include "ledger styled email", "resilience ledger design system email", "make this email look like the other ones", "dark mode email text invisible", "email dark mode not working", "wp_mail styled", "render-ledger-email.py", "status pill email", "callout box email html". | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |