migrate-to-nql

Migrate React components from SQL data fetching to NQL-based useNqlQuery hooks.

Updated Jul 25, 2025
One-click install
npx skills add https://github.com/narrative-io/data-collaboration-mcp --skill migrate-to-nql
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrate-to-nql
Source: https://github.com/narrative-io/data-collaboration-mcp/tree/main/.claude/skills/migrate-to-nql
Command: npx skills add https://github.com/narrative-io/data-collaboration-mcp --skill migrate-to-nql

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Migrating React components from Snowflake SQL-based data fetching to Narrative's NQL-based queries to unlock materialized views and reduce client-side processing.

Core Features & Use Cases

  • End-to-end migration guidance for React components, from identifying SQL calls to replacing them with useNqlQuery hooks.
  • Design of NQL queries that leverage materialized views and sample results, including handling of stable dependencies and case sensitivity.
  • Guidance on updating component usage and validating results with error handling and testing.

Quick Start

Run the migration to replace direct SQL data fetching with NQL-based hooks in your React components.

Frequently Asked Questions about migrate-to-nql

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

FAQPage Schema
How do I migrate React components from direct SQL to NQL queries?

To migrate React data fetching to NQL, identify direct SQL calls and replace them with the useNqlQuery hook. This transition leverages materialized views to reduce client-side processing and requires careful handling of query structure and case sensitivity.

What is the benefit of using NQL hooks instead of SQL in React applications?

Using NQL hooks in React applications unlocks access to materialized views and reduces client-side data processing. By replacing direct SQL patterns with NQL-based queries, components benefit from optimized data fetching and stable dependency management.

How do I handle case sensitivity and dependencies when designing NQL queries?

Designing stable NQL queries requires careful handling of case sensitivity and stable dependencies. You must structure queries correctly and optimize React dependencies to ensure reliable production use when replacing direct SQL data fetching.

Can I use the useNqlQuery hook to replace all direct SQL calls in my React app?

Yes, you can replace direct SQL data fetching by implementing the useNqlQuery hook. The migration involves designing stable NQL queries that leverage materialized views, updating component usage, and validating results with proper error handling.

What are the limitations of migrating to NQL in React components?

Limitations during NQL migration involve the strict requirement for careful handling of case sensitivity, query structure, and React dependency optimization. Reliable production use demands proper error handling and thorough result validation after replacing SQL calls.

Does migrating to NQL require updating error handling in React components?

Yes, migrating to NQL requires updating error handling in React components. Replacing SQL patterns with the useNqlQuery hook involves implementing proper error handling and dependency management to validate results and ensure reliable production use.