# Explain Config

> Explain a pREST configuration file in plain language. Use when the user pastes prest.toml or asks what their pREST setup does.

- Skill: `prest/explain-config` (Agent Skill)
- Install (CLI): `npx skillmds@latest add prest/explain-config`
- Raw SKILL.md: https://api.skillmd.com/api/skills/prest/explain-config/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: prest (https://skillmd.com/u/prest)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/prest/explain-config

---


# Explain pREST config

## When to use

- User pastes `prest.toml`, env dump, or Compose config
- User asks what a setting means or whether something is safe
- User wants a migration-oriented summary (v1 → v2)

## Instructions

1. Read the provided config carefully. Ask for missing related files only if needed (`.env`, `queries/`, Compose).
2. Summarize in this order:

   - **Runtime** — HTTP host/port, debug mode
   - **Database** — single vs multi (`pg.single`, `[[databases]]` aliases), SSL, connection source (TOML vs `DATABASE_URL`)
   - **Queries** — `queries.location` and notable SQL routes if present
   - **Auth** — JWT (`jwt.default`, keys/JWKS), `/auth` table login
   - **Authorization** — `access.restrict`, table permissions, user-level rules
   - **Exposure** — `/databases|/schemas|/tables` listing controls
   - **Cache / other** — only if present

3. Call out risks and suggested improvements (secrets in plaintext, public write, debug enabled).
4. Do not invent fields that are not in the file; say when something is using defaults.
5. Prefer accurate docs language; link https://docs.prestd.com/get-started/configuring-prest when recommending changes.

## Output format

- Short overview (what this deployment is for)
- Sectioned explanation
- Risks & improvements (bullets)
- Optional next steps (skills: `review-security`, `generate-sql-route`, `setup-mcp`)