Menú
Interactive setup wizard for `config/hq.yaml`. Use when the user says "setup", "configure", "set up env", or when `config/hq.yaml` is missing.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Google Calendar via `hq cal` — agenda, free slots, time checks, and session proposals. Use for meetings, appointments, availability, scheduling. Trigger on "calendar", "meeting", "free", "schedule".
Build a dossier on a task issue — gather context from Gmail, Drive, and the wiki, and post it as one sourced comment. Use when asked to "collect for
Google Drive search via `hq drive` (read-only). Use to find work documents, spreadsheets, or slides and pull short excerpts. Trigger on "drive", "document", "doc", "spreadsheet".
Gmail via `hq mail` — search, read, label, and draft (never send). Use for anything involving email. Trigger on "email", "inbox", "reply", "message from".
GTD tasks on the Forgejo repo via `hq task`. Use for adding, listing, and updating tasks (defer/complete are `hq task update` status changes), and for task context/dossiers. Trigger on "task", "todo", "inbox", "what's on my plate".
Email triage — turn unread mail into Inbox task cards and draft replies. Use when asked to "triage", "process email/inbox", or during a triage job.
| name | setup |
| description | Interactive setup wizard for `config/hq.yaml`. Use when the user says "setup", "configure", "set up env", or when `config/hq.yaml` is missing. |
You are a thin wrapper around the built-in hq setup command. It does the real work
(writes config, detects UID/GID/TZ, checks reachability, and on Tier 2 bootstraps
Forgejo). Your job is to ask the human the questions it needs and run it for them.
config/hq.yaml is the gitignored, host-local config every hq command reads. The
tracked template is config/hq.example.yaml. There is no separate project.yaml and no
GitHub anymore — the backend is Forgejo, and forgejo_url is personal, so it lives in
hq.yaml too.
Interactive: ./bin/hq setup (prompts on stdin, prints the compose/ollama commands to
run afterwards). Ask the human for the values it needs and pass them as flags when you
already know them:
--tier {1,2,3}--username, --repo (Forgejo owner/name slug), --timezone (must contain /)--forgejo-url (base URL of the Forgejo instance)--bind-ip, --domain, --admin-user, --admin-password, and either
--forgejo-token (reuse an existing token) or --token-name (mint one).hq setup never overwrites an existing config/hq.yaml/.env unless you pass --force
— confirm with the user before forcing.
config/hq.yaml (e.g. per-account gws
config_dir and mail_url_index under google.accounts, working-hour blocks)../bin/hq doctor — it checks binaries, config keys, token validity, Forgejo/ollama
reachability, and container/cron freshness, and prints a FIX line per failure. Walk the
user through anything red../bin/hq install <mail|cal|drive|discord|core|all>.Bind-mount the config: docker run -v /path/to/config/hq.yaml:/hq/config/hq.yaml:ro ….
Each host keeps its own hq.yaml (accounts and runners differ per host).