support-technician-setup: Skill for Claude Code

Discovering Support Tools

Overview

The runtime support agent must diagnose an end user's actual situation, not guess. It does that by calling read-only tools that fetch and check the user's live state. The user-owned state may live behind more than one read surface — SQL tables, a read API, a non-SQL store, or a pure read-only accessor — so this skill works for whatever connection types the operator enabled (default: SQL only; see "Connection types" below). It reads a product's backend and proposes, for human review:

1. a tool catalog — named, fixed, parameterized read tools scoped to the authenticated end user, each tagged with its connection_type;
2. per-type read-only access artifacts — for SQL, the migration SQL (a restricted read-only role, a table/column allowlist, and row-level-security policies); for any other enabled type, that type's equivalent read-only access spec (endpoint allowlist + read-scoped token for an API, read-only rules/credential for a non-SQL store, an allowlist of pure read accessors for custom);
3. one per-tool source spec (the SQL query, HTTP request, non-SQL query, or named accessor the tool runs).

Core principle: the agent reads the world only through these named tools. It never gets a raw connection, never composes its own query/request/execution, never sees another user's data, and never performs a change.

Connection types — confirm what the agent reads through

Before designing anything, confirm the enabled connection types with the operator (this is decision 6 in setting-up-support-agent; the set lives in the config's connections list). State back which are enabled. Default = SQL only, in which case every output below is identical to the SQL-only behavior. The four supported types:

• sql (default) — a relational database. Tools are parameterized SQL; enforcement is a read-only role + column grants + RLS / mandatory owner filter.
• http_api — a read API the product already exposes. Tools are single, enumerated GET/HEAD requests against allowlisted endpoints.
• nosql — a non-relational store (document/key-value/etc.). Tools are scoped reads with a mandatory owner filter, over a read-only credential.
• custom — a pure, side-effect-free read accessor the product provides (a function that computes a verdict from data it reads). Tools name an allowlisted accessor; the model never supplies code.