querying-noibu-data

Route Noibu analytics queries to the correct data tool with field semantics.

5|10|Updated May 11, 2026
One-click install
npx skills add https://github.com/Noibu/ai-plugin --skill querying-noibu-data
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: querying-noibu-data
Source: https://github.com/Noibu/ai-plugin/tree/main/src/skills/querying-noibu-data
Command: npx skills add https://github.com/Noibu/ai-plugin --skill querying-noibu-data

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This reference provides clear guidance on Noibu's data tools, their field semantics, and routing rules so users can choose the correct tool (e.g., noibu_search_sessions, noibu_get_page_visits, noibu_get_domain) and interpret results accurately.

Core Features & Use Cases

  • Canonical tool routing for common analytics questions (sessions, page visits, funnel visualization, journeys, and integrations).
  • Centralized domain resolution guidance and the required rationale for each tool call.
  • Direct links to topic references (references/sessions.md, references/page-visits.md, references/integrations.md) to fetch detailed field definitions and usage patterns.

Quick Start

Consult this reference to understand Noibu tool routing and data field semantics before composing a query.

Frequently Asked Questions about querying-noibu-data

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

FAQPage Schema
How do I query Noibu session data for specific analytics use cases?

Noibu analytics routing directs domain resolution queries to noibu_get_domain, session-level investigations to noibu_search_sessions, and page-level analytics to noibu_get_page_visits, with each call requiring a documented rationale and adherence to field semantics.

What's the best way to resolve domains before searching Noibu page visits?

Resolving domains before searching page visits involves calling noibu_get_domain to establish routing context, then applying field semantics from the page-visits reference to ensure noibu_get_page_visits targets the correct domain scope with proper rationale.

How do I render funnel visualizations using Noibu analytics data?

Rendering funnel visualizations using Noibu analytics involves following canonical routing references to identify session and page visit queries, then consulting linked reference documents for detailed field definitions and rendering patterns to construct the visualization.

When do I need to reference Noibu's canonical documentation for field semantics?

You need to reference Noibu's canonical documentation for field semantics whenever composing queries across sessions, page visits, journeys, or integrations, ensuring every tool call includes a rationale and follows documented query constraints to interpret results accurately.

Can I use Noibu data tools to access journey and integration analytics?

Yes, you can access journey and integration analytics by following canonical reference routing rules, which provide pointers to specific reference documents containing field definitions and usage patterns for those data scopes, with each query requiring a documented rationale.

Why does my Noibu data query require a rationale for each tool call?

Noibu data queries require a rationale for each tool call to ensure accurate domain resolution, proper application of field semantics, and adherence to documented routing rules that direct queries to the correct analytics tool for sessions, page visits, or integrations.