onmax/skills

file-a-pr

Files one concise GitHub pull request from a completed change. Use when the user explicitly asks to file, open, create, or update a PR from the current branch.

airtable-flow

Advances Quiver Airtable tasks from intake or selection to a review-ready pull request. Use when Maxi asks to report new Airtable work or select, claim, investigate, implement, or finish a task.

fleet

Converges Linux agent machines into shared coding nodes and balances bounded agent work across them. Use when bootstrapping or reconciling a VPS, direct SSH, T3 Connect, Codex and GitHub auth profiles, shared workspaces, scheduled jobs, machine cleanup, or…

html-communication

Use when the user asks to communicate through an HTML document, or if they mention "HTML" with no additional context.

portal-preview-login

Authenticates Browser to a Quiver Portal pull-request preview and opens the requested route. Use when a `pr<number>-demo.preview.quiver.dk` preview displays the Portal login page.

postplan-read

Use when the user provides a postplan.dev URL to read.

code-review

Reviews a diff against repository standards, the requested behavior, and structural code quality. Use when the user asks to review a branch, PR, commit range, or work in progress, including strict review.

vitehub-projects

Routes ViteHub projects and consumers to their local project roots and GitHub coordinates when available. Use when the user mentions ViteHub itself, a ViteHub template or app, Formula 100, or a Quiver Agent, Airtable, Babysitter, Chat, Portal, Review, or Wiki…

agent-writing

Writes or revises prompts and SKILL.md files as compact agent instructions. Use only when the user explicitly asks to write, improve, or consolidate a prompt or skill.

animation

Designs, finds, implements, audits, and reviews interface animation with Emil Kowalski's interaction principles. Use when the user explicitly asks for animation, motion, transitions, easing, spring behavior, or animation polish.

cleanup

Audits and safely cleans Git worktrees, branches, build artifacts, caches, Docker data, or disk usage. Use only when the user explicitly asks to clean worktrees, reclaim disk space, or remove stale development state.

codebase-design

Designs or improves codebase boundaries, deep modules, domain models, ownership, and test seams. Use for architecture, module interfaces, domain concepts, structural simplification, or codebase deepening.

delegate

Delegate one conversation-grounded pull request to a separate Codex task.

diagnosing-bugs

Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.

evidence-research

Researches one decision using auditable internal or external evidence. Use when current sources, repository history, precedent, or competing claims could materially change a technical or product decision.

grill-with-docs

Interviews the user until a product, technical, or workflow direction is explicit, then optionally writes the requested durable artifact. Use when the user asks to be grilled, challenged, or interviewed about an underspecified direction.

handoff

Writes a compact continuation handoff that preserves exact repository state, proof, ownership, decisions, and the next action. Use when work must continue in another task, agent, or session.

library-craft

Reviews reusable package craft: third-party dependencies, exports, layout, naming, tests, docs, compatibility, and release shape. Use for npm packages, SDKs, framework utilities, reusable modules, or public APIs.

pull-request

Reviews and converges one existing GitHub pull request: contribution fit, code quality, CI, feedback, conflicts, and merge readiness. Use only when the user explicitly asks to inspect, review, refine, fix, or finish an existing PR.

ui

Routes UI design, implementation, and visual QA to the smallest useful local or external context. Use for layout, hierarchy, controls, responsiveness, visual polish, interaction craft, or Apple-platform UI.

validate-direction

Challenges a proposed technical or product direction before it hardens into an API, workflow, architecture, plan, or durable artifact. Use when competing boundaries or ownership choices could materially change the next action.

vitehub-drop

Uploads scoped local files to permanent public URLs and renders scoped source code as temporary Ray.so images. Use when an agent needs a public image or document URL for GitHub content, or a shareable PNG or SVG code image.

writing-documentation

Writes and rewrites developer documentation around the reader's goal, with concrete technical English and verified examples. Use for tutorials, guides, concepts, references, and troubleshooting pages.

engineering-writing

Turns verified engineering context into concise issue reports, implementation requests, and pull request bodies. Use when engineers need an actionable artifact that preserves the reasoning and evidence behind a problem, request, or completed change.

cli-craft

Builds and evolves command-line interfaces around an explicit CLI contract, including arguments, automation-safe output, exit behavior, interaction, mutation boundaries, and executable proof. Use when creating a CLI, adding or changing commands and flags, or…

people-skills

Drafts human-centered messages and recommends interpersonal next actions using practical relationship principles. Use when the user asks for emails, DMs, apologies, conflict repair, influence, persuasion, feedback, favors, boundaries, or advice for a personal…