skojaku

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".

Interactive setup wizard for `config/hq.yaml`. Use when the user says "setup", "configure", "set up env", or when `config/hq.yaml` is missing.

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.

Rules for the personal wiki under wiki/ (inbox, pieces, hubs, literature). Use when reading, creating, editing, or promoting notes; when assigning tags or linking notes to hubs. For searching, use `hq wiki find`.

Hierarchical review of scientific documents (papers, grant proposals) without editing them. Layer 1 spawns naive skim and adversarial critics that file findings as GitHub issues; Layer 2 triages each finding simplification-first (cut before patch). Runs coarse to fine — document skeleton, sections, paragraphs — locking user decisions between stages, then a sentence-level style check. Use for any review or critique request on paper or proposal prose. For writing, rewriting, or wording edits, use the scientific-writing skill instead.

Draft and revise multi-page scientific documents (papers, grant proposals) in the user's style. Structures documents for busy readers who skim — skeleton-first drafting loop, claim-carrying headings — and enforces the user's sentence-level voice (terse first-person description over persuasive, blog-like phrasing). Use whenever writing, rewriting, or editing paper or proposal prose, even for a single sentence. For a review or critique request without editing, use the scientific-review skill instead.

Set up an orchestrated lead-agent + subagent loop for any iterative multi-step task. Use this skill whenever the user wants to process a collection of items one at a time (papers, files, tickets, data points), build up accumulated results across iterations, or run a multi-phase pipeline with a controlling agent and worker subagents. Also trigger on "ralph loop", "lead agent loop", "orchestration loop", "subagent delegation", processing a list of things automatically, or iterating over a batch of inputs. Trigger even when the user just describes the task without naming the pattern—if it sounds like "do X for each Y and accumulate results", this skill applies.

Explains a paper comprehensively and concisely.

Write a literature review by iterating over papers one at a time, accumulating summaries and themes across iterations.

Check and install required dependencies for this repository.

Test-drive a skill by spawning one sub-agent per incomplete task in PRD.md. Each sub-agent executes the skill for the task's Test Case and judges output against its Evaluation Criteria.

Write a literature review by iterating over papers one at a time, accumulating summaries and themes across iterations.

Manage a computational research project across its whole lifecycle — starting a fresh project, exploring new ideas, and promoting validated results into the reproducible master workflow. Use whenever the user starts a new project, kicks off a new experiment / study / investigation ("let's test whether...", "new idea to look at...", "spin up a study on..."), records what an experiment found, or wants results moved into the paper's master workflow — even if they don't say "experiment" but are clearly starting or advancing research. It owns the project template, each experiment's dated folder under exps/, its NOTE.md, its GitHub issue, and the master workflow. Do NOT trigger for narrow edits inside an already-scaffolded experiment — a Snakemake rule, NOTE.md typo, script tweak, conda env, paper text, or gh lookup.

Snakemake style guide and conventions for building reproducible data pipelines. Covers project layout, naming, rules, paramspace, dual-mode scripts, and utility functions.

Build marimo walkthrough notebooks with narrative story arcs, consistent visualization style, and branded CSS. Use when creating or editing marimo notebooks that present research findings as a story. Use together with marimo-pair for cell editing.