Detect plugin regressions and roll back before they wreck a deadline
Third-party plugins can cause crashes, failed launches, or dramatic slowdowns after updates. This recipe adds change control to your plugin folder — tracking versions, logging failures, and enabling fast rollback when an update breaks your setup.
Create a skill called "Plugin Stability Gate". Inputs: - plugin_paths - backups_path - notify_on_change (true) Behavior: - Watch plugin_paths for changes and record an inventory snapshot. - If I report crashes/slowdowns, ask what changed recently and guide me through isolating the offending plugin with a rollback plan.
This skill takes periodic snapshots of your plugin inventory (name, version, path, last
modified) and watches for changes. When you report instability, it helps you isolate the
offending plugin through a structured test and provides rollback steps.
Diagnose missing conversions and "flying blind" measurement fast
Use this when the numbers don't match: ad platforms over/under-report, GA4 looks off, CRM revenue doesn't reconcile, or privacy changes (ATT/cookie loss/consent) have degraded tracking. It produces a root-cause shortlist, a "what to trust" guidance note, and a prioritized fix plan.
Diagnose CrashLoopBackOff and friends without the kubectl marathon
Give it a namespace or pod name and it runs the full kubectl diagnostic sequence for you — events, logs, describe, resource usage — then explains what's actually wrong in plain English. No more chaining five commands to find out you're missing an environment variable.
A playbook for "stops at the same frame" and "freeze mid-render" failures
Renders freeze at a consistent percentage or frame — often caused by a bad clip, a heavy effect, a Fusion comp issue, or "stop render on error" settings. This recipe classifies the failure pattern and gives you a structured triage plan instead of blind re-exports.
Fix a common Premiere playback-lag issue caused by audio input device settings
Severe playback lag and stutter in Premiere Pro that looks like a codec performance problem but is actually caused by audio hardware input settings. This recipe provides a quick decision tree to test and fix the issue — often resolved in under a minute by switching the default input to "No Input."