haiggoh
UserRun Claude Code on local Apple-Silicon MLX models (rapid-mlx/vllm-mlx) as an additive overlay — private config stays local.
Categories
Indexed Skills (7)
compose-the-payload
Use WHEN assembling the MATERIAL for a stateless dispatch — file contents, large corpora, or structured data — so the source never enters the orchestrator context. Do NOT use for writing the instructions about that material, verifying output, guarding runtime, or isolating work.
guard-shared-runtime
Use BEFORE modifying the local execution environment (installing packages, upgrading dependencies, changing config) or when the local inference server behaves unexpectedly. Triggered by dependency changes, reinstall checks, or server wedges. Do NOT use for verifying output, isolating work, or composing payloads.
isolate-parallel-work
Use BEFORE dispatching work that touches files or requires exclusive access to a server/port. Triggered by the need to run multiple agents concurrently or to prevent clobbering. Do NOT use for verifying output, guarding runtime, or composing payloads.
local-agents
Use when the user wants to offload Claude Code work to a LOCAL MLX model to save cost — PRIMARILY dispatching a delegatable sub-task from their normal cloud session (Opus/Sonnet), and secondarily running a full local session. Triggers: "dispatch this to a local model", "offload this locally to save cost", "run this on qwen locally", "start a local session / local mode", "run the local model tournament", or working offline. Explains how to drive the local-agents overlay: dispatch focused prompts (main use), launch a full local session (niche), and run the diagnostic harnesses. Do NOT use for ordinary cloud work that isn't being offloaded.
offload-to-local
Use when PLANNING or decomposing ANY multi-step task, and whenever your plan involves reading, searching, summarizing, transforming, drafting, extracting, or editing across files — regardless of whether cost is mentioned. Also when you're about to do delegatable/bulk/mechanical work on a paid cloud model, or you notice you're about to burn cloud tokens on work a smaller model could do. It routes delegatable work to a free local model — by DEFAULT to the broad `operator` role, escalating to a specialist role only when needed — instead of spending cloud tokens. Explicit triggers: starting a multi-step plan (especially under a budget constraint / Credit Efficient Mode), "save cost/tokens", "do this locally", "offload this", "use the local model for this". Do NOT use it to offload frontier-reasoning, architecture, security-critical, or final-review work.
verify-delegated-work
Use AFTER a delegate (local model, cloud subagent, or external tool) returns output that modifies state, generates code, or asserts facts. Triggered by the need to validate correctness before trusting the result. Do NOT use for planning, briefing, or runtime checks. Covers ground-truth comparison, mutation testing of generated tests, and the retry ceiling.
brief-the-delegate
Use WHEN writing the instruction/prompt for a stateless dispatch. Triggered by the need to disambiguate task boundaries, ordering, or output format. Do NOT use for verifying output, guarding runtime, or composing payloads.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.