ollama-macos-headless
Skill1 starsChanged 9 days agoNo licenceView on GitHub
This 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".
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
- immich-sdcard-sync-pruneSkill
- infisical-secrets-managerSkill
- jellyfin-media-permissionsSkill
- jellyfin-proxmox-deploymentSkill
- laravel-filament-proxmox-lxcSkill
- n8n-workflow-api-authoringSkill
- 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
3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
3
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.

