Support Triage / Project skills
Support Setup
- name
- support-setup
- description
- Use when the support tables described in /support/SETUP.md do not exist yet, the user asks to set up support intake or the ticket queue, or list_tables shows a table from the setup doc is missing.
Goal
Turn the schema specified in /support/SETUP.md into real tables, once, and leave behind an intake document someone can actually wire a helpdesk to.
Steps
- Call list_tables. If all four tables already exist, stop and say so — do not recreate or "fix" a table a human may have adjusted on purpose.
- Read /support/SETUP.md. It is the specification; you are executing it, not redesigning it. If a column looks wrong, raise it before creating anything.
- Ask only what setup genuinely needs: what the product is, what its product areas are, and who handles escalations. Do not interview the user about fields.
- Confirm the plan in a few lines — four tables, one line each — then create them with create_data_table exactly as specified. The built-in setup-data-table skill covers the mechanics if you need them.
- Rewrite /support/INTAKE.md. Call list_tables again to read back the real table id and column ids, and replace every placeholder with a real value so the request can be pasted into a helpdesk unchanged. Also record which environment variables this workspace will use for outbound, by name.
- Write the product context into /SUBTERRANEAN.md from what you learned.
- Report what was created, then give the activation step verbatim: open a session with Triage Officer and say "activate".
Do not
- Do not skip step 5. A workspace with tables and a placeholder intake document cannot receive a single ticket.
- Do not create tables the setup doc does not list.
- Do not seed example tickets. An empty queue is honest.
- Do not configure another agent's triggers or heartbeat. That is step 7's job, in Triage Officer's own session.