pubfi-dsl-client

Construct schema-compliant PubFi DSL requests for OpenSearch and Postgres.

Updated Feb 3, 2026
One-click install
npx skills add https://github.com/helixbox/pubfi-skills --skill pubfi-dsl-client
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pubfi-dsl-client
Source: https://github.com/helixbox/pubfi-skills/tree/main/skills/pubfi-dsl-client
Command: npx skills add https://github.com/helixbox/pubfi-skills --skill pubfi-dsl-client

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Enables developers to construct safe, structured PubFi DSL requests for OpenSearch and Postgres, avoiding server-side natural language compilation and ensuring auditable query shapes.

Core Features & Use Cases

  • Generate deterministic DSL queries from user intents
  • Enforce schema-compliant fields and UTC timestamps
  • Validate and route requests to the proper DSL endpoints

Quick Start

Configure API_BASE to your environment and map a user intent into the DSL schema to generate a structured query.

Frequently Asked Questions about pubfi-dsl-client

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build structured queries for OpenSearch and Postgres without writing raw SQL or DSL?

You can generate deterministic PubFi DSL requests from user intents to ensure safe, structured queries against the schema, avoiding server-side natural language compilation and raw SQL injection risks.

What is the best way to validate fields and timestamps before sending a PubFi DSL query?

Validating PubFi DSL queries involves enforcing schema-compliant fields and UTC timestamps, applying end-exclusive windows, and verifying shapes against the DSL schema before routing requests.

How do I map user intents into a deterministic DSL query schema?

To map user intents, configure your API base environment, apply the user intent against the retrieved DSL schema fields, and generate a structured query using the POST /v1/dsl/query endpoint.

Does the PubFi DSL client require specific endpoints for schema retrieval and querying?

Yes, the PubFi DSL client requires the GET /v1/dsl/schema endpoint to fetch the schema and the POST /v1/dsl/query endpoint to execute the structured query requests.

Why should I use structured PubFi DSL queries instead of server-side natural language compilation?

Structured PubFi DSL queries provide deterministic query shapes, enforce schema-driven fields and auditable usage, and bypass the unpredictability of server-side natural language compilation.

What are the limitations of using PubFi DSL queries for OpenSearch and Postgres?

PubFi DSL queries are limited by the fetched DSL schema, strictly enforcing schema-compliant fields, UTC timestamps, and end-exclusive windows, which prevents arbitrary or non-compliant query construction.