IsmaelMartinez

Use when the user asks for a portfolio briefing, debrief, status update, morning standup, end-of-day summary, or "what did I do today" across their repo-butler-managed repos.

Use when the user wants to act on governance findings, open remediation PRs, fix standards gaps, or apply tier-uplift / policy-drift / stale-Dependabot fixes across the portfolio. Routes findings by their executor hint — dispatching the cloud workflow for templatable gaps and drafting local PRs for findings that need tailored content.

Use this skill to offload non-reasoning text work to locally-installed models (Ollama or MLX) via `delegate.sh`, keeping content on-device and freeing the main-agent context window. Saves API tokens too, though context protection and privacy are the headline values, not cost. MUST use whenever the user asks to summarise a log/diff/file/PR/issue, draft a commit message/changelog/release note, triage or classify many items, extract structured fields from free text, skim many files for a one-liner, or rewrite or reformat prose. MUST also use when the user explicitly asks to delegate, names a local backend or model (Ollama, MLX, "a local model"), wants content kept on-device or offline for privacy, or wants to save API tokens. Bare "run it locally" usually means running the app, server, or tests on the user's own machine, not delegating to a local model, so treat "locally" as a delegation signal only when paired with an explicit delegate verb, a named local model, or a keep-it-private reason. MUST also use after

Delegate complex, multi-step codebase exploration to local Ollama models. Best for analysis, review, and understanding tasks that require reasoning across multiple files.