caddy-mute

Solid

Mute a Caddy hint class for a window. Defaults to 4h auto-expiry. Classes — memory, context, body, routing, all.

AI & Automation 11 stars 3 forks Updated today MIT

Install

View on GitHub

Quality Score: 85/100

Stars 20%
36
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# /caddy-mute Suppress a Caddy hint class for a bounded window. State lives in `memory/CADDY_MUTES.json`. `daemons/caddy.sh` reads it on every UserPromptSubmit and skips matching class hints when active. ## Classes - `memory` — `[CADDY:memory]` MEMDB, DIGEST hints - `context` — `[CADDY:context]` CTX, CAPSULE hints - `body` — `[CADDY:body]` BODY-CHECK hint - `routing` — `[CADDY:routing]` ROUTE, /orient, STYLE, DICT hints - `all` — nuclear; mutes every class ## Usage ``` /caddy-mute --class memory # 4h default /caddy-mute --class memory --hours 1 # 1h /caddy-mute --class memory --forever # explicit permanent (rare) /caddy-mute --class all # nuclear /caddy-mute --class memory --reason "design session, hint fatigue" ``` If no `--hours` and no `--forever`: default 4 hours. ## Implementation Compute `muted_until` and Edit `memory/CADDY_MUTES.json`: ```json { "memory": { "muted_until": "2026-05-03T18:00:00Z", "reason": "design session, hint fatigue", "default_duration_hours": 4 } } ``` For `--forever`: set `muted_until` to `9999-12-31T23:59:59Z`. Surface to the operator when setting forever ("muted memory class indefinitely — confirm?") so it doesn't drift into permanent silence by accident. For `--class all`: write a single `all` block; caddy.sh `class_muted` checks `all` in addition to the requested class. ## Inverse To unmute early, Edit `memory/CADDY_MUTES.json` and remove the class entry, or set `muted_until` t...

Details

Author
wrg32786
Repository
wrg32786/aigent-os
Created
1 months ago
Last Updated
today
Language
JavaScript
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

memory-write

Captures a durable fact to project memory through the kit's safe write path (Poison_Guard secret/injection screening + home-path sanitization + dedup + conflict detection) — preferring the cmk MCP tools (mk_remember / mk_forget / mk_trust) when connected, falling back to the cmk CLI. Use when the user says "remember this", "note this", "save this", "from now on", "going forward", "I prefer", "I don't like", "we decided", "we agreed", or otherwise states a durable preference, decision, or environment fact worth carrying across sessions. Also covers correcting a saved fact ("update memory: X is now Y"), removing one ("forget about X"), and adjusting how much a saved fact is trusted ("trust this", "that's important — keep it", "that's not important / I'm not sure about that / low priority"). Skip throwaway chatter and facts that only matter to the current task.

4 Updated today
LH8PPL
AI & Automation Listed

bettermemory

Verification-grade memory between sessions. Use bettermemory's MCP tools (memory_search, memory_show, memory_write, memory_verify, memory_record_use, etc.) instead of writing to files when the user asks you to "remember" something or references shared context from a past session. Default is to NOT call memory_search; only retrieve when the user references context you don't have ("my project", "the script we wrote") or a request is ambiguous in a way stored preferences could resolve. Every hit carries a staleness_verdict (calendar + path-drift + commit-drift); when it isn't "fresh", spot-check a claim before relying and call memory_verify to attest. Every use should record a claim_excerpt so retrievals stay auditable.

0 Updated today
0Mattias
AI & Automation Listed

ccc-memory

Two-tier persistent memory for Claude Code sessions. Layer 1 is CLAUDE.md (always-loaded context). Layer 2 is a memory/ directory with dated notes, decisions, and…

6 Updated today
KevinZai