limits-quiet-hours

Honor the quiet hours the user set for themselves — the hours where AI tools are off-limits so "one more prompt" stops costing sleep. Enforced as refused tool calls where hooks exist, advisory everywhere else, with a deliberate logged override path. Use when the user asks about their quiet hours, asks why tool calls are paused, wants to override quiet hours, or asks "am I inside my quiet hours".

Ir a la instalación

Repositorio: bradfrost/skills
Última actividad en el origen: 28 de agosto de 2026 a las 15:20
Idioma detectado de SKILL.md: inglés
Estrellas: 6
Forks: 0

Opciones de instalación

De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.

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.

Un comando directo omite el prompt de revisión. Revisa el origen antes de ejecutarlo.

npx skills add https://github.com/bradfrost/skills --skill limits-quiet-hours

El comando permanece en una sola línea. Desplázate horizontalmente para revisarlo antes de copiarlo.

¿Prefieres una copia local? Descarga los archivos que SkillsMP tiene disponibles ahora.

Revisa los archivos de origen

Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.

Explorador de archivos

2 archivos

SKILL.md

Instrucciones de origen · Vista previa de solo lectura

Volver a la búsqueda Volver a la instalación

limits-setup

The AI limits interview — run by /setup-brad-frost-skills, or directly any time. A short guided interview that establishes your personal limits for AI usage — quiet hours, a sessions-per-day ceiling, how sessions end — then wires them into whatever your tools can actually enforce and tells you plainly where enforcement stops. Use when the user says "set my limits", "set up my AI limits", "limits setup", "help me stop using AI at 2am", when /setup-brad-frost-skills routes here, or when the limits skills are installed but no config exists yet at ~/.config/ai-limits/.

2026-08-30

setup-brad-frost-skills

START HERE after installing Brad Frost's skills — run this once to get everything set up. Finds which of the skills you installed, runs the setup each one needs (the limits interview), and tells you how to use the ones that need no setup. Use when the user says "setup brad frost skills", runs /setup-brad-frost-skills, has just installed this collection, or asks how to get started with these skills.

2026-08-30

limits-endings

End every AI session definitively — the task that started the session is the task that ends it, loose ends get filed rather than dangled, and every substantive response closes with a compact Signal Flags block instead of a trailing "want me to also…?" hook. Use always, in every session where this skill is installed; also when the user says "wrap this up", "land it", "close out", or asks about session endings.

2026-08-28

Ver todos los de este repositorio

Limits: quiet hours

The person using this skill declared hours where AI tools are off-limits — typically the hours where late-night prompting was costing them sleep. Your job is to honor the window, honor the override when it's made deliberately, and never lecture in either direction.

Pairs with limits-setup, which writes the config this skill reads and installs its hook.

How it works

QUIET_START / QUIET_END in ~/.config/ai-limits/config define the window (wrapping midnight is fine: 22:00–07:00).

Where PreToolUse-style hooks exist (Claude Code today), quiet-hours.sh refuses tool calls inside the window with a terse message. The model can still talk; it can't work. That's the strongest lever the platform offers — no surface can gate the model's text.

The override is a deliberate typed act via the CLI: ~/.config/ai-limits/bin/ai-limits override quiet-hours --reason "why" — which asks the person to type, exactly: I'M AWARE I'M INCREASING MY AI USAGE It's then honored for 8 hours, logged once, and counted in the weekly report. Honored means honored: no follow-up commentary from you.

Your conduct (binding)

Inside quiet hours, don't be the workaround. If tool calls are refused, don't route around the hook. Name the override path once and leave the choice with them.

Never moralize — not about working late, not about overriding. The logged count is the instrument; judgment isn't yours to add.

Automation stays quiet. If the config says AUTOMATION_IN_QUIET=run-silent, scheduled work may proceed but must not notify, message, or otherwise pull the person back to the keyboard. If you are the automation, hold your report until the window ends.

Name the gap when asked. On surfaces without hooks, quiet hours are advisory — you honor them by declining to start new work and saying why, but nothing enforces that. See the enforcement matrix in limits-setup.

Files

Path

What

hooks/quiet-hours.sh (in this skill)

the PreToolUse gate; limits-setup installs it

~/.config/ai-limits/config

QUIET_START, QUIET_END

~/.config/ai-limits/state/override-quiet-hours

the active override (8h, by file age)

~/.config/ai-limits/state/overrides.log

every override: timestamp, reason