support-triage

Generate a weekly support triage brief by feeding an aggregated categorical inbox export into the skill, which computes category mix, detects spikes against a 4-week baseline, and routes trends to owning skills. Save the output brief to context/admin-ops/support/briefs with a dated filename.

Support trend analysis remains read-only on the weekly export and omits individual tickets and user data entirely. It processes only aggregated categorical data to enforce privacy rules while producing a concise weekly trend brief.

Yes, you can detect support ticket spikes by comparing the current week's aggregated export against a 4-week baseline. The analysis flags time-sensitive items and surfaces significant volume shifts across support categories.

Yes, the weekly triage brief routes detected trends to owning skills based on rules defined in support-categories.md. This routing orchestration ensures recurring patterns are directed to the correct teams for remediation.

The weekly support export must be an aggregated categorical export from the support inbox. The trend analysis operates on this aggregated data to compute category mix and detect spikes without inspecting individual tickets.

Your support triage brief omits individual ticket details to enforce strict privacy rules defined in memory and companion skills. The brief focuses exclusively on aggregated trend analysis and category mix rather than user-level data.