Support ops
Product Bug vs How-To Split
Classify support cases by evidence of expected versus observed behavior.
Configure this skill
The page and the file follow your answers.
CRM
Email
Chat
Documents
Calendar
Project tools
6 of 6 systems connected
KeepDirectMissing
Your assistantSKILL.md
Download ↓
When to use it
Classify support cases by evidence of expected versus observed behavior.
What it covers
Inputs
Tickets, product version, approved documentation.
Result
Case classifications, supporting evidence and diagnostic questions.
What it uses
SlackProject toolsCalendarEmailDocumentsKeep memoryRead only
For developers
Retrieval instructions
Resolve people, accounts and projects by stable identifiers. Use only the sources this task needs. Cite the source and date for each finding. Keep source systems unchanged.
Data sources
Slack, Linear, Google Workspace, Keep memory.
Procedure
- Resolve inputs for Product Bug vs How-To Split: time_window, account, ticket_id, severity. Default time window: open incidents and SLA risk window (override if caller provides time_window). Ask only for missing.
- keep_memory_read for open tasks, decisions, and handoffs relevant to Product Bug vs How-To Split (filter out unrelated day-plan noise).
- Run keep_search with these skill-specific intents (keep meaning; adjust wording to corpus):