Check whether upgrading a package / runtime / model version is safe. Looks up the user-driven regression catalogue (8+ entries from real field reports) AND runs provider-side regression detection (catches Anthropic-April-23-style silent reasoning-effort downgrades). Returns a recommended upgrade path with mitigations. Use before any significant package upgrade, model-version bump, or runtime change.
This listing is imported from SkillsMP metadata and should be treated as untrusted until upstream source review is completed.
Install skill "should-i-upgrade" with this command: npx skills add temurkhan13/skillsmp-temurkhan13-temurkhan13-should-i-upgrade
This source entry does not include full markdown content beyond metadata.
This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.
Related by shared tags or category signals.
One-page operator cheatsheet for the Aufgaard plugin. The "what to check, when, why" reference. Auto-loaded so day-to-day routing is fast. Use as the lightweight summary when the user wants a quick recap of capabilities.
Show recent silent-failure detections from cron / scheduled jobs. Catches the textbook patterns — exit-0 with empty stdout, length anomalies (output dramatically shorter than baseline), retry storms, action-budget leaks. Use when the user asks "is anything silently broken", "did Friday's cron actually run", "are my scheduled jobs working", or after a downstream consumer reports stale data.
Show current production AI cost overview — totals, top spenders by agent, per-provider breakdown, anomaly detection, and time-to-429 rate-limit prediction. Use when the user asks "what's my AI bill", "which agent is burning tokens", "am I about to hit the rate limit", or wants a cost dashboard. Cross-provider — works for Anthropic, OpenAI, Gemini, Bedrock, Ollama.
Scan Python source files for swallowed-exception patterns that silently turn errors into fake successes. Catches bare `except` blocks that pass / return None / return mock objects, log-and-fake-success handlers, and mock-substitution-on-error. AST-based — not just regex. Use before any deploy of new agent code, on the working directory after a bug fix, or routinely on production-path Python files.