Explore skills
Search every indexed skill by name, description, repository or instructions, then narrow the results.
Showing 32881–32910 of 33516 skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| clarityjackson2w/claude-code-skillsDraft, rewrite, or review reader-facing prose so it is specific, useful, and recognizably the author's without inventing facts or performing humanness. Use for essays, articles, newsletters, documentation, talks, launch copy, and other important prose that feels generic, hollow, or AI-shaped. Supports co-write, rewrite, review, and lint modes. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| claude-code-headless-tool-restrictionjackson2w/claude-code-skillsThis skill should be used when building an unattended/headless `claude -p` invocation (cron job, systemd timer, CI step, webhook handler) that needs a real security boundary restricting which tools the agent can use — not just permission-prompt convenience. Trigger phrases include "headless claude code", "unattended claude -p", "restrict claude code tools", "claude code allowedTools", "claude code disallowedTools", "safe automated claude invocation". | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| claude-code-remote-control-hostjackson2w/claude-code-skills | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| cloudflarejackson2w/claude-code-skillsDiscover and choose Cloudflare products for apps, APIs, AI agents, storage, networking, and security. Use for architecture and product selection, including when the user describes a need without naming a Cloudflare product; then find the relevant skill or documentation. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| cloudflare-cron-telegram-alertjackson2w/claude-code-skillsThis skill should be used when scaffolding a Cloudflare Worker that runs on a cron trigger, checks something external (a URL, an API, a heartbeat), and sends a Telegram alert only on failure — e.g. an uptime monitor, a health check, a dead-man's-switch. Trigger phrases include "cron trigger uptime monitor", "Telegram alert Worker", "cloudflare cron health check", "scheduled Worker Telegram", "uptime monitor Cloudflare Worker", "dead man's switch worker". | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| cloudflare-email-servicejackson2w/claude-code-skillsImplement or troubleshoot Cloudflare Email Sending and Email Routing integrations and their delivery configuration. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| cloudflare-onejackson2w/claude-code-skillsDesign, configure, troubleshoot, or review Cloudflare One Zero Trust and SASE deployments. Use cloudflare-one-migrations for migration planning from other vendors. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| cloudflare-one-migrationsjackson2w/claude-code-skillsAssess and plan migrations from existing VPN, SWG, or SASE platforms to Cloudflare One, including policy mapping, parity gaps, and rollout. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| cloudflare-pages-gotchasjackson2w/claude-code-skillsThis skill should be used when working on a Cloudflare Pages project with Pages Functions — debugging on-the-fly image resizing that won't work, a wrangler.toml with named [env.*] blocks where bindings mysteriously go missing in one environment, a crypto.subtle PBKDF2 call that throws in production but works locally, or a _redirects rule that silently never fires on a path a Function also handles. Trigger phrases include "pages images binding", "env.IMAGES", "wrangler.toml env production", "bindings missing in production", "PBKDF2 iterations error", "NotSupportedError iteration counts", "_redirects not working", "redirect skipped by functions", "pages function precedence". | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| cloudflare-r2-rclone-backupjackson2w/claude-code-skills | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| cloudflare-r2-restic-backupjackson2w/claude-code-skillsThis skill should be used when setting up a nightly/periodic encrypted backup of a directory (an app's state/data dir, a database dump, an agent's working directory) to a Cloudflare R2 bucket via restic, or when debugging an existing restic-to-R2 systemd timer job. Distinct from the `cloudflare-r2-rclone-backup` skill — that one covers plain `rclone sync` (mirrors a tree as-is, no encryption/dedup/snapshots); this one covers `restic` (client-side encrypted, deduplicated, snapshotted, with retention/pruning) — pick restic whenever the source is app state you'd want point-in-time recovery of, not just an already-static archive worth mirroring. Trigger phrases include "restic backup to R2", "restic R2 repository", "nightly restic backup", "restic systemd timer", "restic keep-daily keep-weekly prune", "restic init repository", "restic check integrity", "restic restore verify", "restic unable to open cache", "R2 access key for restic", "AWS_ACCESS_KEY_ID restic env", "credential assert guard rail ansible", "restic backup credential not yet populated". | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| cloudflare-worker-tailscale-shieldjackson2w/claude-code-skillsThis skill should be used when building a Cloudflare Worker that sits in front of a homelab service reachable only via Tailscale Funnel — validating auth/rate-limiting at Cloudflare's edge before forwarding inward, with a Cloudflare Queue for retry-on-failure. Also covers a specific `wrangler secret put` misuse that leaks the secret value as the secret's *name*. Trigger phrases include "cloudflare worker in front of tailscale", "webhook shield worker", "worker forward to tailscale funnel", "workers can't reach tailnet", "wrangler secret put wrong name", "queue retry backoff worker", "workers_dev false no public url". | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| cloudflare-workers-cron-emailjackson2w/claude-code-skillsThis skill should be used when the user asks to debug a Cloudflare Workers Cron Trigger that "isn't firing" or "not running" (or fires on the wrong day), set up or troubleshoot the send_email binding or Email Routing destination addresses for Workers, size a Worker against Cloudflare's per-invocation subrequest limits, test a scheduled() handler locally against real R2/KV/email bindings, verify an R2 delete/rename actually took effect, or rename/reorganize keys in an R2 bucket. Trigger phrases include "cron trigger not firing", "scheduled worker not running", "cron ran on the wrong day", "wrangler cron", "cron trigger debug", "send_email binding", "Workers email binding", "Email Routing destination address", "workers subrequest limit", "test-scheduled --remote", "r2 object rename", "r2 delete not working", "r2 move objects". | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| credential-rotation-protocoljackson2w/claude-code-skillsThis skill should be used whenever a live credential (API key, bot token, access token, etc.) needs to be rotated, changed, OR REMOVED ENTIRELY — whether because it leaked, is being proactively refreshed, is being replaced as part of an incident response, or auth is simply being turned off on a service. Disabling/removing a password is the same category of change as rotating it and needs the same consumer inventory — arguably more so, since there's no new value to hand out, only broken consumers to discover the hard way if you skip the check. Also load it whenever verifying that a credential file/rotation is correct, since that's exactly the step that causes leaks if done wrong. Trigger phrases include "rotate this credential", "the key leaked", "update this token everywhere", "credential rotation", "verify the new key works", "did the secret change", "disable the password", "turn off auth", "remove the login requirement", "no longer needs a password". | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| cross-agent-filesystem-exchangejackson2w/claude-code-skills | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| debian-kernel-reboot-checkjackson2w/claude-code-skillsThis skill should be used when checking whether a Debian-based host (Proxmox host, LXC, VM, bare metal, or VPS) needs a reboot to pick up a kernel update, when "apt update" reports no upgradable packages but a reboot is suspected to be pending anyway, when planning a safe reboot of a host running live services, or when auditing an entire fleet of mixed LXC/VM/bare-metal hosts for pending kernel upgrades. Trigger phrases include "kernel upgrade", "check for pending reboot", "reboot-required", "unattended-upgrades installed a new kernel", "does this host need a reboot", "safe reboot checklist", "fleet kernel sweep", "uname -r doesn't match installed kernel", "proxmox-kernel not applied", "LXC kernel version", "does the container share the host kernel". | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| docker-vpn-killswitch-lxcjackson2w/claude-code-skillsRoute only some Docker containers (downloaders such as yt-dlp, MeTube, Pinchflat) out through a commercial WireGuard VPN (ProtonVPN, Mullvad, etc.) from inside an unprivileged Proxmox LXC, with a two-layer kill switch so they can never fall back to the ISP: WireGuard `Table = off`, a dedicated Docker bridge with a fixed name, source-based ip rules into a routing table whose only permanent route is `unreachable`, and an nftables forward-hook drop in its own table. The rest of the LXC (Tailscale, Jellyfin, SMB, apt) stays on the LAN. Covers sanitising the provider's .conf, unit ordering, DNS, Tailscale's ip rules, and the two drills that prove each layer works alone. Trigger phrases include "VPN kill switch", "route docker through wireguard", "containers only through the VPN", "ProtonVPN for the downloaders", "no ISP fallback", "Table = off", "policy routing for a docker network", "split tunnel docker", "gluetun alternative", "wg-quick in an LXC". | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| durable-objectsjackson2w/claude-code-skillsBuild, debug, or review Cloudflare Durable Objects code for persistent state and coordination. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| filament-panel-themingjackson2w/claude-code-skills | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| forced-outage-drilljackson2w/claude-code-skillsSimulate a dependency outage on a live host (upstream DNS, an API endpoint, a backup target, a peer) to prove a watcher, failover or alert actually works, without paging anyone and without the drill passing for the wrong reason. Covers proving the block bites (nft counters plus a control) before trusting any result, why container egress needs a forward-hook chain, cache and stale-answer layers that hide the outage, a systemd-run dead-man revert, testing a new watcher against a throwaway instance on a spare port with stubbed alerting, and the drill sequence: baseline, failure surfaces, failover, recovery, cleanup. Trigger phrases include "failover drill", "simulate an outage", "force a failover", "test the watcher", "blackhole the upstream", "nft drop for a test", "dead-man revert", "does the alert actually fire", "drill without paging", "stub telegram", "prove the failover works". | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| forgejo-deploymentjackson2w/claude-code-skillsThis skill should be used when installing or debugging a self-hosted Forgejo (Gitea fork) git server as a native binary + systemd service — not Docker. Covers the three required secrets (SECRET_KEY/INTERNAL_TOKEN/JWT_SECRET) and the permission-denied crash-loop from a locked-down config file, unattended install without exposing the web setup wizard, why Forgejo's built-in git-SSH server needs firewall-level scoping instead of an app-level bind address, a non-obvious API scope requirement for repo deletion, and Vultr Block Storage's region-locking. Trigger phrases include "forgejo install", "forgejo systemd", "forgejo app.ini", "JWT_SECRET failed loading", "save oauth2.JWT_SECRET failed", "forgejo not supposed to be run as root", "forgejo admin user create", "forgejo random-password", "forgejo generate secret", "forgejo INSTALL_LOCK", "forgejo git-ssh port", "forgejo delete repo API 403", "write:user scope forgejo", "vultr block storage wrong region", "no active instances available in this region", "vultr NVMe block storage not available". | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| grafana-api-token-provisioningjackson2w/claude-code-skillsThis skill should be used when provisioning a scoped Grafana API credential for an automation/script (a monitoring sweep, a health-check script, a report generator), when deciding what Grafana role a service account needs, when checking real alert-rule health/evaluation state via the API rather than the UI, or when a Grafana RBAC fixed role like `fixed:alerting.rules:reader` doesn't seem to be assignable. Trigger phrases include "grafana service account", "grafana api token", "grafana read-only token", "grafana alert rule health api", "api/prometheus/grafana/api/v1/rules", "fixed:alerting.rules:reader not available", "grafana RBAC OSS vs enterprise", "grafana viewer role least privilege". | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| grafana-prometheus-alertingjackson2w/claude-code-skillsThis skill should be used when a Prometheus + Grafana stack has metrics being scraped but no real alerting configured, when adding a new Grafana alert rule via provisioning-as-code (not the UI), when checking whether Prometheus alert rules actually exist versus assuming a monitoring stack alerts on its own, when detecting individual systemd service failures across a fleet without building a custom OnFailure-to-webhook mechanism, or when a Grafana alert rule needs testing end-to-end before trusting it. Also use it when a disk/filesystem alert rule is green over something that is actually filling up, when a mounted volume has no `node_filesystem_*` series at all, or when a scrape target goes DOWN after a host changes address. Trigger phrases include "prometheus has no alert rules", "grafana provisioning alert rules", "node_systemd_unit_state", "grafana rules.yaml", "alert on systemd unit failure", "grafana noDataState", "test grafana alert rule firing", "prometheus /api/v1/rules empty", "node_exporter systemd collector", "node_exporter not showing /mnt", "no metrics for mounted volume", "mount-points-exclude", "collector.filesystem.mount-points-exclude", "datastore has no disk metrics", "alert green but disk full", "filesystem collector skipping mount", "disk space rule never fires", "scrape target DOWN after IP change", "pin scrape target to hostname not IP". | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| hermes-agent-deploymentjackson2w/claude-code-skillsThis skill should be used when deploying or debugging a self-hosted Hermes Agent (Nous Research's self-hosted personal-assistant gateway bridging Telegram/WhatsApp/Slack/Discord to an LLM with tool/skill/cron access — Will calls his instance "Chuka") — including install via the `hermes` CLI, the `hermes-gateway.service` systemd unit, native `hermes cron` scheduled jobs, the `hermes skills` system (SKILL.md drop-in files distinct from Claude Code's own skills), Debian 13 install gotchas (python3.13-venv, broken IPv6/gai.conf), fleet-readonly SSH access design, or UID-scoped egress firewalling. For credential protection via Agent Vault specifically, see the separate `agent-vault-credential-broker` skill — this skill covers Hermes's own deployment, not the broker. Trigger phrases include "hermes agent", "hermes gateway", "hermes cli", "hermes cron create", "hermes skills list", "hermes-gateway.service", "hermes mcp install", "ensurepip is not available", "HERMES_HOME", "hermes gateway install --system", "chuka", "hermes_cli.main gateway run", "LunaRoute glm-5.3-flash", "hermes fleet access", "hermes-remote", "hermes_egress table", "hermes gateway setup selector drops to done", "hermes setup tools", "hermes homeassistant setup not prompting", "aiohttp trust_env proxy bypass", "hermes update reverted patch", "uv pip install no pip module hermes venv", "hermes memory provider", "hindsight plugin", "memory.provider hindsight", "lazy_deps exact pin", "Feature memory.hindsight unavailable", "local_external". | Stars: 1 | Updated | Claude CodeCodex | Unverified | 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 |