Tech on DataAgentX

The 2W1H of the Semantic Layer for Agents: Why It's Needed, What It Is, and How to Build It

Fri, 23 Oct 2026 00:00:00 +0000

Does connecting to a database and generating SQL guarantee that an Agent will answer business questions correctly?

When asked the same question, “What was last quarter’s revenue?”, different tools yield different answers: a BI tool might include taxes and shipping costs; a Notebook might fail to deduct discounts and returns; finance may recognize revenue based on shipment dates, while the Agent is still guessing how tables relate.

Before Adjusting a Fee Rate, Identify Which Transactions Will Be Affected

Thu, 22 Oct 2026 00:00:00 +0000

If a payment fee rate is reduced from 14 basis points to 1 basis point, how much can a merchant save in a month?

While this appears to be a multiplication problem, the actual challenge lies before the multiplication: determining which transactions are affected. This analysis recalculates two “hard” problems from DABstep, with a focus on defining the scope and performing independent verification.

Hotel Data in Practice: Why Brand Rankings Change

Tue, 20 Oct 2026 00:00:00 +0000

Why doesn’t a brand with an average 5-star rating always rank first on the hotel brand leaderboard?

This walkthrough follows the complete pipeline using public benchmark questions: Data → Question → Solution → Validation. The focus is not merely on calculating the answer, but on understanding how qualification thresholds and denominator selection alter conclusions.

Data and Questions

The dataset is InfiAgent-DABench, which evaluates the ability to truly execute analysis and deliver results starting from CSV files, natural language questions, and constraints. This fixed question set contains 257 questions referencing 52 CSV files; here, we use only hotel_data.csv, comprising 1,057 rows and 9 columns, covering 7 cities and 103 non-null brands, with each row representing a hotel record.

Turning 15 Skills into an Agent You Can Verify

Sat, 17 Oct 2026 00:00:00 +0000

Does installing 15 Skills give you a reliable Data Agent?

One essential step remains: turning “what it can do” into “how to prove it has done the job well.”

This article introduces no new official Skill. It presents an approach to product development synthesized from the source material discussed in the previous 9 installments. The task protocols, acceptance chain, and failure checklist below are editorial frameworks, rather than a unified specification defined by the source.

What Is Published Is a Snapshot, Not a Real-Time System

Fri, 16 Oct 2026 00:00:00 +0000

Does publishing analysis results as a URL mean the team now has a real-time data system?

No. The original documentation for Publish Artifact to Sites clarifies this boundary first and foremost: what is published is a snapshot; it does not automatically add live data source connections.

This boundary dictates all subsequent design decisions: how access permissions are configured, how versions are managed, and what must be communicated during handoff.

Dashboards and Reports Share Evidence, but Serve Different Jobs

Thu, 15 Oct 2026 00:00:00 +0000

When a dashboard starts resembling a long article, or a report becomes a wall of metrics, the underlying problem often precedes visual design. Does the reader need to keep monitoring a situation, or understand a particular judgment?

Data Analytics Skills addresses these needs with two Skills: Build Dashboard and Build Report. They share a foundation of trustworthy evidence, but their purposes, structures, and acceptance criteria differ.

Reproducible Calculations Make Charts Credible

Wed, 14 Oct 2026 00:00:00 +0000

The same chart changes when someone else reruns the analysis. The same data tells a different story when the axis changes. Details like these often undermine a Data Agent’s credibility.

Data Analytics Skills divides this work between two Skills: Jupyter Notebooks makes the calculations reproducible, while Visualize Data keeps their presentation from misleading readers. The first explains where a number comes from; the second establishes what a chart can support.

Data Quality and Validation: Two Gates, Two Risks

Tue, 13 Oct 2026 00:00:00 +0000

If a table has no nulls and no duplicates, can you confidently publish the analysis?

Not necessarily. Even if the data is entirely correct, the calculation might be wrong; even if calculated correctly, the comparison might be flawed, or correlation might be mistaken for causation. These three types of failures occur at different stages and require distinct checks to catch them.

Data Analytics Skills divides these into two skills: Analyze Data Quality to check the data, and Validate Data to check the analysis. These two gates guard against different risks; missing either one leads to leakage.

How Big Is the Market? Deliver an Estimate You Can Interrogate

Mon, 12 Oct 2026 00:00:00 +0000

“What is the size of this market?” The most common response from a Data Agent is a number that appears precise. The hardest deliverable is an estimation framework that can be interrogated and adjusted.

The focus of the Market Sizing skill is not to pad answers with zeros, but to ensure scale estimations have boundaries, sources, and assumptions, while explicitly stating where evidence is insufficient when it is lacking.

When Metrics Drop: Reproduce the Change Before Discussing Causes and Actions

Sat, 10 Oct 2026 00:00:00 +0000

“Conversion rates dropped; the new version must be unusable.”

This statement skips two critical questions: Are the metrics truly comparable? Does the change genuinely stem from product experience? An investigation must first rule out changes in definitions, coverage, or denominators before attributing the movement to the business itself.

Data Analytics Skills divides this work into two Skills: Metric Diagnostics explains the change, while Product & Business Analysis translates that explanation into evidence-based business decisions. The former owns “what happened,” and the latter owns “what to do.”

From Defining Success to Sustained Operations: The Complete KPI System Loop

Fri, 09 Oct 2026 00:00:00 +0000

Many teams maintain a long list of KPIs yet cannot clarify three things: what success means, whether they are currently on track, and what the next step should be. As the number of metrics increases, judgment often deteriorates.

Data Analytics Skills breaks this down into two Skills: Design KPIs defines success, while KPI Reporting organizes actual performance, targets, drivers, and actions into operational readouts. Together, they form a closed loop from measurement contracts to sustained operations.

Gather Enough Business Context to Continue

Thu, 08 Oct 2026 00:00:00 +0000

“Help me understand why conversion fell.” If a data agent immediately finds tables, writes SQL, and slices channels, it may answer the wrong question very efficiently. What are the numerator and denominator? Does conversion mean registration, activation, or payment? Which window changed? What decision will the result support?

Gather Business Context puts the request back into business coordinates before computation begins. Its output is not a final diagnosis. It is a Context Note that makes the next analytical step safe to start.

Who Routes the 15 Data Analytics Skills?

Wed, 07 Oct 2026 00:00:00 +0000

A data agent may know how to design metrics, diagnose anomalies, inspect quality, run notebooks, draw charts, build dashboards, and publish reports. That breadth creates a subtle failure mode: every tool contributes, yet no component owns the actual question.

The Index in the Data Analytics Skills collection is interesting because it acts less like a homepage and more like a control plane. It decides whether a request belongs in analytics, which workflow owns it, how conflicting sources are handled, and what “done” means.

How to Build a Data Agent: A Working Map from 23 Articles

Sun, 04 Oct 2026 00:00:00 +0000

After surveying many Data Agent products, a team beginning implementation still faces five basic questions: What work should the system own? Which data should it use? How may it execute? How will we prove the result? Who remains accountable when it fails?

Those questions are more durable than a vendor list. They connect definition, architecture, autonomy, evaluation, and rollout.

The diagram below maps those questions onto an operating path: how a task enters the system, how semantics constrain planning and execution, and how evidence, approval, read-back, and feedback close the loop.

A Data Agent Vendor Map Based on System Position, Not Labels

Thu, 17 Sep 2026 00:00:00 +0000

The easiest Data Agent market map to draw incorrectly is a wall of logos that mixes cloud platforms, BI applications, internal systems, open-source frameworks, and research projects. They may serve different jobs, occupy different layers, and accept different production responsibilities.

A useful map has two axes: system position and delivery model. Find peers first, then compare them.

The First Step in Enterprise Data Agent Adoption Is Not Model Selection

Tue, 15 Sep 2026 00:00:00 +0000

The first enterprise Data Agent decision is usually not the most capable model or the number of agents. Choose a frequent, verifiable, low-impact segment of work and define what correct completion looks like. Otherwise a smooth demo reaches production with no credible test of trust.

Rollout is a staged transfer of responsibility. Each step toward production gives the agent another duty and requires new evidence plus a return path.

How to Read Data Agent Benchmarks Before Trusting the Ranking

Mon, 14 Sep 2026 00:00:00 +0000

A first-place Data Agent is not automatically the best procurement choice. A leaderboard says which submissions performed better under a particular task set, data environment, tool policy, budget, and scoring rule. An enterprise needs to know whether the system can deliver under its definitions, permissions, cost, and failure conditions.

The most useful way to read a ranking is backward through its measurement chain.

OpenAI Data Analytics Skills as Reviewable Work Protocols

Sun, 13 Sep 2026 00:00:00 +0000

“Why did conversion fall?” A demo agent can quickly locate a table, write SQL, draw a line, and suggest several causes. Delivery exposes the harder questions: What is the denominator? Is the current period complete? Did channel mix change? Are the “causes” measured contributions or a plausible story?

The Data Analytics Skills are useful because they turn analytical responsibility, handoffs, and completion criteria into reusable work protocols—not because of one special prompt.

When Is a Data Agent Report Actually Delivered?

Sun, 13 Sep 2026 00:00:00 +0000

An agent has generated a report on declining new-customer conversion. The task is not finished. A business leader needs to know whether the conclusion supports a decision, an analyst needs to recompute material values, and an operations team may need an investigation ticket. They require different artifacts and may have different data rights.

Delivery is complete when an authorized recipient can understand, verify, and use the result. Recommendation, approval, submission, confirmed effect, and business impact must remain separate states.

How Far Data Agent Governance Must Extend

Sat, 12 Sep 2026 00:00:00 +0000

A regional manager and a corporate analyst can ask the same question—“How is channel conversion performing?”—and be entitled to different answers. Row-level filtering in the database is not enough if a cache, export, or shared report can later deliver the corporate result to the regional user.

Governance cannot be a system prompt that says “do not reveal sensitive information.” It must cover discovery, model context, tool invocation, runtime, delivery, and business actions, enforced by systems the model cannot override.

If the SQL Runs, Can You Trust the Data Agent Answer?

Thu, 10 Sep 2026 00:00:00 +0000

A successful query, attractive chart, and complete report do not independently make an answer trustworthy. The agent may have selected the wrong source, bound the wrong metric, executed correct SQL over incomplete data, and then described correlation as causation.

One accuracy score compresses these failures into a number and hides high-cost errors. A better evaluation follows the analysis chain layer by layer and sends each failure back to the component that can repair it.

Why Agent-Generated SQL Must Not Run Directly

Wed, 09 Sep 2026 00:00:00 +0000

A model that emits SQL has proposed an action; it has not earned production execution authority. Even a SELECT can scan terabytes, expose sensitive columns, invoke an external function, or return a plausible result after an incorrect join.

The execution layer converts model intent into a controlled operation: validate before running, constrain during execution, verify afterward, and retain evidence for every side effect.

Why Data Agent Tasks Still Fail When the Agent Can Plan

Wed, 09 Sep 2026 00:00:00 +0000

“New-customer conversion is down. Find the cause and recommend what to do.” The agent queries channels, then regions. The third query times out, so it restarts from the beginning. Or it produces a twelve-step plan, reads the first result, and forgets which hypothesis the task was meant to test. It appears to reason, yet the work never finishes.

The planning layer is not a checklist generator. It turns a complex objective into an execution process that preserves state, checks evidence, recovers from failure, and hands control to a person when necessary.

The Data Agent Access Layer: Finding the Right Data Before Querying

Tue, 08 Sep 2026 00:00:00 +0000

“Why did new-customer conversion fall this month?” A warehouse may contain a production funnel model, a similarly named test table, and a spreadsheet from last quarter’s campaign. All three are reachable. All three have plausible columns. If the agent chooses the wrong one, polished SQL and charts only make the error more persuasive.

Before query generation, the access layer must answer three questions: What may this identity access? What should this task use? Is the selected evidence sufficient for the claim? It is not a pipe that dumps every schema into a prompt. It is a permission-aware discovery and context-routing system.

Why Stronger Data Agents Need a Semantic Layer

Tue, 08 Sep 2026 00:00:00 +0000

Give a model the schemas for orders, payments, and customers and it can quickly produce executable SQL. Ask “What was revenue last month?” and the real work begins. Does revenue mean booked value, cash received, net receipts, or recognized revenue? Which date applies? In which period do refunds belong?

Those are not universal facts for a model to infer. They are enterprise contracts. As an agent gains tools and a longer execution chain, the cost of propagating one incorrect definition into a report or action increases.

Data Agent Levels L0–L5: Autonomy Transfers Responsibility

Sun, 06 Sep 2026 00:00:00 +0000

One system writes SQL. Another invokes SQL and Python, observes errors, and replans. The second system has more tools, but tool count alone does not make it more autonomous. The real questions are: Who sets the goal? Who organizes the work? Who is authorized to act? Who verifies the result? Who recovers—and remains accountable—when it fails?

Data Agent levels are therefore best understood as a transfer of responsibility, not a feature checklist. At each level, the agent inherits more operations, judgment, and risk.

Five Data Agent Routes: Compare Products by the Work They Own

Sat, 05 Sep 2026 00:00:00 +0000

One Data Agent turns a business question into SQL. Another runs queries and Python, then writes a report. A third edits a production pipeline. They share a category name, but they should not share one scorecard.

The useful unit of classification is a workflow, not a vendor. Ask four questions: What enters the system? Which part of the work does it own? What does it deliver? What is the blast radius when it fails? Those questions reveal five recurring routes.

The SQL Ran. Why Is the Answer Still Wrong?

Fri, 04 Sep 2026 00:00:00 +0000

The most dangerous result in analytics is often not a failed query. It is a query that runs cleanly, returns a precise number, produces a polished chart—and answers the wrong question.

Suppose an operator asks, “How many new customers did we acquire this month?” The system finds a customer table, counts distinct IDs by created_at, and returns 12,486. The query is reproducible and syntactically correct. But Sales defines a new customer as a first-time payer, while Finance excludes refunded transactions and internal test accounts. The query counted new customer records, not the metric that will drive the budget decision.

What Is a Data Agent? Four Practical Tests

Thu, 03 Sep 2026 00:00:00 +0000

“Why did conversion fall this week?”

An NL2SQL tool can translate that sentence into a query. A data agent has a larger job. It must establish which product and funnel the question refers to, decide whether “this week” means a calendar week or a rolling seven-day window, and respect what the current user is allowed to see. It then has to find trusted data, apply the right metric definition, investigate the change, run and check its queries, and return evidence with the conclusion.