Build database-backed Perspective pages with fewer SQL guesses.
This skill teaches the agent to discover real queries and schemas, preview bounded data, and connect SQL output to Perspective tables, charts, labels, and filters.
Why it was made
- Prioritizes parameterized Named Queries over pasted one-off SQL.
- Uses historian bindings or documented history APIs before reaching for raw historian table SQL.
- Uses capped previews and safe defaults before a Perspective binding depends on a query.
- Connects query shape to UI state, zero-row states, labels, filters, and validation.
Common use cases
- Downtime, quality, work order, production, and maintenance dashboards.
- Perspective tables and charts backed by Named Queries.
- Tag Historian, Named Query, and Postgres-style reporting patterns.
- Reviewing query parameters and return shapes before UI binding.
Proof style
Validate the artifact, not the promise.
The skill does not treat a SQL string as done until preview shape, parameters, and Perspective binding behavior are checked. Historian raw SQL is treated as advanced evidence work, not the default first move.
Evidence
Named Query workflow proof
The graphic is AI-generated for the site. The checks below come from a sanitized read-only runner pass that proved the API-assisted SQL workflow can inventory Named Queries, read one allowed query contract, inspect database context, and run a capped preview without publishing local query text or row data.
- health confirmed namedQueriesList, namedQueryRead, namedQueryPreview, and databaseConnectionsList are supported runner actions.
- namedQueriesList returned a capped inventory and identified a read-only, bounded, no-parameter preview candidate.
- namedQueryRead inspected the selected query contract, type, parameter count, SQL hash, and preview eligibility without exposing SQL text.
- databaseConnectionsList returned redacted connection/status context before preview work.
- namedQueryPreview ran with a five-row cap and returned a two-column result shape for binding validation.
Example prompt
Using the runner, discover a bounded Named Query and build a Perspective table binding with filters.This is the kind of short instruction the skill is designed to make useful. The value is in the checks and Ignition-specific defaults the AI uses after reading the skill.
Expected output
- Uses health, database discovery, namedQueriesList, namedQueryRead, and namedQueryPreview.
- Drafts parameter maps, return shape notes, and read-only preview limits.
- Validates page bindings with viewRead, pageValidate, browser rows, and zero-row behavior.
Related workflows
Skills that pair with this one
Ignition SQL query builder without API
SQL Builder Without API
Work from exports without pretending it was live-tested.
Ignition Web Dev API builder
Web Dev API Builder
Let the AI inspect, apply, and validate on a Gateway.
Ignition HMI SCADA styling
HMI/SCADA Styling
Make generated screens readable for operators.
Lifetime membership
Want access to this skill?
The one-time membership unlocks this skill, the full Ignition AI Toolkit, the Web Dev runner materials, setup docs, versioned downloads, and future Ignition 8.3 skills as they ship.
No subscription. Lifetime members keep portal access to the current toolkit and future skill releases, including planned Ignition 8.3-focused skills as they are added.