[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M757PCEECH5X62ZWYCV79D90":3,"skill-same:01M757PCEECH5X62ZWYCV79D90":49},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M757PCEECH5X62ZWYCV79D90","auto-remediation-fixes",null,"Essential auto-remediation fixes for staging server guardian — timeout patterns, provider drift fixes, and operational hygiene for cron job errors and agent inbox remediation.","lukemcqueen\u002Fsteadfaste-fleet","lukemcqueen","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F405240?v=4","01M757MHPAGRXTJAT46SKZP98R","Luke McQueen","01M757MHPZ573KP8DT9GB8SBQ7",4,"MIT","https:\u002F\u002Fgithub.com\u002Flukemcqueen\u002Fsteadfaste-fleet\u002Fblob\u002Fmain\u002Fskills\u002F.archive\u002Fauto-remediation-fixes\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: auto-remediation-fixes\ndescription: \"Essential auto-remediation fixes for staging server guardian — timeout patterns, provider drift fixes, and operational hygiene for cron job errors and agent inbox remediation.\"\nversion: 1.0.0\ncategory: devops\n---\n\n# Auto-Remediation Fixes — Orchestrator Patterns\n\n## General Principles\n\n### Conservative Editing of Monitoring Lists\n\nWhen modifying a cron quality watchdog's `MONITORED_CRONS` list (or any monitoring inventory):\n\n1. **Only remove entries that don't exist.** An existing cron, even if it's a `no_agent` script rather than an LLM-driven cron, still produces output worth monitoring. The watchdog checks apply to all output, not just LLM-generated text.\n2. **Add new entries rather than shuffling.** If the list is missing crons that should be monitored, add them. Rearranging is cosmetic and risks accidentally removing a valid entry.\n3. **Verify each entry exists.** Check `cronjob(action='list')` or `read_file('~\u002F.hermes\u002Fcron\u002Fjobs.json')` before deciding an entry is stale.\n\n## Timeout Patterns\n\n### Cron Timeout Fires\n\nWhen a cron times out (\"timed out after Ns\"):\n\n1. Check the cron's actual runtime — `cronjob action='list'` shows `last_duration`.\n2. If the script legitimately needs more time, raise the timeout — do not \"optimize\" a script that is correctly slow.\n3. If the script hangs (waiting on network, lock, or stdin), fix the hang — raising the timeout just delays the failure.\n\n### Provider Timeout Drift\n\nWhen an API provider (OpenRouter, DeepSeek, Ollama) starts timing out:\n\n1. Verify the provider's own status page (health-external-verification).\n2. Check `OLLAMA_KEEP_ALIVE` — a 0 value unloads the model and the cold-load exceeds the `_embed()` timeout (see loop-governance lesson).\n3. Add retry-with-backoff at the call site rather than raising timeouts globally.\n\n## Provider Drift Fixes\n\n### Model\u002FConfig Drift After Update\n\nWhen an update cycle silently changes provider config:\n\n1. **Diff the deployed config vs repo source** — `config-drift-diagnostics` compares 3 locations.\n2. **Fix the repo source first**, then deploy — never patch the deployed copy directly (fleet-preflight rule).\n3. **Verify the running service actually reloaded** — file-on-disk ≠ change-live (Principle 15).\n\n### Cron Prompts Referencing Missing Skills\n\nWhen a cron prompt references a skill that doesn't exist or was renamed:\n\n1. Find the real skill name — `skills_list()`.\n2. Update the cron's skill attachment — `cronjob action='update' skills=[...]`.\n3. Update the installer source in `install-crons.sh` so the fix survives redeploys.\n\n## Operational Hygiene\n\n### Remediation Must Be Idempotent\n\nEvery fix applied by the guardian must be safe to re-run on an already-fixed system:\n\n```bash\n# ✅ Idempotent: check-then-act\nif ! grep -q \"setting\" config; then\n  echo \"setting\" >> config\nfi\n\n# ❌ Non-idempotent: appends every time\necho \"setting\" >> config\n```\n\n### Escalate After Repeated Failure\n\nA remediation that fires 3+ times for the same root cause is a failed fix, not a healthy loop:\n\n1. First occurrence: remediate, log outcome.\n2. Second occurrence: remediate + check the fixer's own logic (wrong pattern?).\n3. Third occurrence: **escalate** — stop auto-fixing, report to the orchestrator with the failure history.\n\n### Unattended Destructive Actions Default to No-Op\n\nIn unattended\u002Fcron mode, destructive operations (prunes, deletions, resets) default to **inaction** when ambiguous. Disk pressure can be remediated; deleted data cannot.\n\n## Related\n- `auto-remediation-ecosystem` — full-pipeline deployment + monitoring\n- `auto-remediation-setup` — setup and verification\n- `cron-quality-gate` — the watchdog that monitors cron output\n- `sensor-false-positive-remediation` — handling false sensor positives\n- `fix-without-asking` — when to auto-fix vs escalate\n","# Auto-Remediation Fixes — Orchestrator Patterns\n\n## General Principles\n\n### Conservative Editing of Monitoring Lists\n\nWhen modifying a cron quality watchdog's `MONITORED_CRONS` list (or any monitoring inventory):\n\n1. **Only remove entries that don't exist.** An existing cron, even if it's a `no_agent` script rather than an LLM-driven cron, still produces output worth monitoring. The watchdog checks apply to all output, not just LLM-generated text.\n2. **Add new entries rather than shuffling.** If the list is missing crons that should be monitored, add them. Rearranging is cosmetic and risks accidentally removing a valid entry.\n3. **Verify each entry exists.** Check `cronjob(action='list')` or `read_file('~\u002F.hermes\u002Fcron\u002Fjobs.json')` before deciding an entry is stale.\n\n## Timeout Patterns\n\n### Cron Timeout Fires\n\nWhen a cron times out (\"timed out after Ns\"):\n\n1. Check the cron's actual runtime — `cronjob action='list'` shows `last_duration`.\n2. If the script legitimately needs more time, raise the timeout — do not \"optimize\" a script that is correctly slow.\n3. If the script hangs (waiting on network, lock, or stdin), fix the hang — raising the timeout just delays the failure.\n\n### Provider Timeout Drift\n\nWhen an API provider (OpenRouter, DeepSeek, Ollama) starts timing out:\n\n1. Verify the provider's own status page (health-external-verification).\n2. Check `OLLAMA_KEEP_ALIVE` — a 0 value unloads the model and the cold-load exceeds the `_embed()` timeout (see loop-governance lesson).\n3. Add retry-with-backoff at the call site rather than raising timeouts globally.\n\n## Provider Drift Fixes\n\n### Model\u002FConfig Drift After Update\n\nWhen an update cycle silently changes provider config:\n\n1. **Diff the deployed config vs repo source** — `config-drift-diagnostics` compares 3 locations.\n2. **Fix the repo source first**, then deploy — never patch the deployed copy directly (fleet-preflight rule).\n3. **Verify the running service actually reloaded** — file-on-disk ≠ change-live (Principle 15).\n\n### Cron Prompts Referencing Missing Skills\n\nWhen a cron prompt references a skill that doesn't exist or was renamed:\n\n1. Find the real skill name — `skills_list()`.\n2. Update the cron's skill attachment — `cronjob action='update' skills=[...]`.\n3. Update the installer source in `install-crons.sh` so the fix survives redeploys.\n\n## Operational Hygiene\n\n### Remediation Must Be Idempotent\n\nEvery fix applied by the guardian must be safe to re-run on an already-fixed system:\n\n```bash\n# ✅ Idempotent: check-then-act\nif ! grep -q \"setting\" config; then\n  echo \"setting\" >> config\nfi\n\n# ❌ Non-idempotent: appends every time\necho \"setting\" >> config\n```\n\n### Escalate After Repeated Failure\n\nA remediation that fires 3+ times for the same root cause is a failed fix, not a healthy loop:\n\n1. First occurrence: remediate, log outcome.\n2. Second occurrence: remediate + check the fixer's own logic (wrong pattern?).\n3. Third occurrence: **escalate** — stop auto-fixing, report to the orchestrator with the failure history.\n\n### Unattended Destructive Actions Default to No-Op\n\nIn unattended\u002Fcron mode, destructive operations (prunes, deletions, resets) default to **inaction** when ambiguous. Disk pressure can be remediated; deleted data cannot.\n\n## Related\n- `auto-remediation-ecosystem` — full-pipeline deployment + monitoring\n- `auto-remediation-setup` — setup and verification\n- `cron-quality-gate` — the watchdog that monitors cron output\n- `sensor-false-positive-remediation` — handling false sensor positives\n- `fix-without-asking` — when to auto-fix vs escalate\n",{"name":5,"version":24,"category":25,"description":7},"1.0.0","devops","main","162463c5db5a1e06f4c54abddce6ee13c3d7612b","skills\u002F.archive\u002Fauto-remediation-fixes",1,"https:\u002F\u002Fgithub.com\u002Flukemcqueen\u002Fsteadfaste-fleet","steadfaste.com","https:\u002F\u002Fgithub.com\u002Flukemcqueen","AI Architect | Building Hermes Cortex: governed multi-agent AI for autonomous software engineering | Enterprise Tech Consultant","2026-11-14 22:33:34",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add lukemcqueen\u002Fsteadfaste-fleet --skill auto-remediation-fixes",{"tool":41,"command":42},"bunx","bunx skills add lukemcqueen\u002Fsteadfaste-fleet --skill auto-remediation-fixes",{"tool":44,"command":45},"pnpm","pnpm dlx skills add lukemcqueen\u002Fsteadfaste-fleet --skill auto-remediation-fixes","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flukemcqueen\u002Fsteadfaste-fleet\u002Fblob\u002Fmain\u002Fskills\u002F.archive\u002Fauto-remediation-fixes\u002FSKILL.md",true,[],[50,58,65,72,79,86],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":57},"01M7DXY4G8NSVB59K8B6S2AQNP","macbook-linux-maintenance","Legacy MacBook Linux fixes: GPU wedge, reboot hang, thermal.","https:\u002F\u002Fgithub.com\u002Flukemcqueen\u002Fsteadfaste-fleet\u002Fblob\u002Fmain\u002Fskills\u002Fdevops\u002Fmacbook-linux-maintenance\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":57},"01M7DXXYJCXFJ3TGB84ZQ8KFE6","governance-regression-triage","Triage a host's governance issues: what changed.","https:\u002F\u002Fgithub.com\u002Flukemcqueen\u002Fsteadfaste-fleet\u002Fblob\u002Fmain\u002Fskills\u002Fdevops\u002Fgovernance-regression-triage\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":57},"01M7DXXSAP1G8FDRJAMXQGBBMK","enforcement-immutability","Use when enforcement files lose their immutable flag.","https:\u002F\u002Fgithub.com\u002Flukemcqueen\u002Fsteadfaste-fleet\u002Fblob\u002Fmain\u002Fskills\u002Fdevops\u002Fenforcement-immutability\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":57},"01M78SSDQVRYX64Y16X32TC0NS","steadfaste-fleet-repo-deploy","Use when committing to the steadfaste-fleet repo.","https:\u002F\u002Fgithub.com\u002Flukemcqueen\u002Fsteadfaste-fleet\u002Fblob\u002Fmain\u002Fskills\u002Fdevops\u002Fsteadfaste-fleet-repo-deploy\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":57},"01M78SS928F3R2RJAYVW4E30CE","steadfaste-fleet-maintenance","Maintain an installed Steadfaste Fleet instance — update both the upstream Hermes Agent and the fleet repo layer, merge diverged histories, sync skills safely, and troubleshoot common issues. Covers the dual-update workflow (hermes update + fleet-update.sh), encrypted brain data backup, mycortex import, and recovery techniques.","https:\u002F\u002Fgithub.com\u002Flukemcqueen\u002Fsteadfaste-fleet\u002Fblob\u002Fmain\u002Fskills\u002Fdevops\u002Fsteadfaste-fleet-maintenance\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":57},"01M78SP1CHW0T0BWE5ZT6JBPX8","fleet-preflight","DEPRECATED alias — merged into survey-before-action (2026-08-20). Load survey-before-action instead; its \"Repo-Specific Pre-Flight\" section covers git search, Hermes boundary, and deployment verification.","https:\u002F\u002Fgithub.com\u002Flukemcqueen\u002Fsteadfaste-fleet\u002Fblob\u002Fmain\u002Fskills\u002Fdevops\u002Ffleet-preflight\u002FSKILL.md",[],[]]