dashboard-querying

Test API endpoints and choose dynamic fetching or static embedding for dashboards.

Updated Jan 20, 2026

Search Tags:#workflow #API #authentication #dashboard #data-fetching #dynamic #static

Ready to run

npx skills add https://github.com/BLSQ/mcp_servers --skill dashboard-querying

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dashboard-querying
Source: https://github.com/BLSQ/mcp_servers/tree/main/.claude/skills/dashboard-querying
Command: npx skills add https://github.com/BLSQ/mcp_servers --skill dashboard-querying

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables dashboards to fetch data reliably by selecting between dynamic API calls and static embedded data.

Core Features & Use Cases

Decision workflow to test API endpoint availability and choose dynamic fetching or static embedding.
Guidance for dynamic fetching with cookie-based authentication and multi-table data orchestration.
Static data embedding as a fallback with loading states, error handling, and data transformation templates.

Quick Start

Use this skill to determine how your dashboard should fetch data: test the API endpoint, decide between dynamic vs static data, and implement the appropriate fetch or embedding strategy.

Frequently Asked Questions about dashboard-querying

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

FAQPage Schema

How do I reliably fetch dashboard data when API endpoints are unstable?▼

To reliably fetch dashboard data, test the API endpoint availability first, then choose between dynamic API calls or static embedded data. This decision workflow ensures data continuity by coordinating multi-table retrieval and providing static embedding as a fallback with error handling.

How do I handle cookie-based authentication for dashboard API calls?▼

Cookie-based authentication for dashboard API calls is handled through dynamic fetching guidance that manages session cookies and coordinates data retrieval across multiple tables. This ensures authenticated requests succeed while maintaining fallback strategies for data continuity.

When should I use static data embedding instead of dynamic API fetching for dashboards?▼

Use static data embedding instead of dynamic API fetching when endpoint testing indicates the API is unavailable or unreliable. Static embedding provides a reliable fallback with loading states, error handling, and data transformation templates to ensure continuous dashboard operation.

What is the best way to orchestrate multi-table data retrieval for dashboards?▼

The best way to orchestrate multi-table dashboard data retrieval is through a coordinated workflow that tests API endpoints, implements dynamic fetching with cookie-based authentication, and applies static embedding with data transformation templates as fallbacks.

Why does my dashboard data fetching fail without error handling templates?▼

Dashboard data fetching fails without error handling templates because no fallback mechanisms exist to manage API unavailability or session timeouts. Implementing loading states, static data embedding, and error handling ensures data continuity when dynamic API calls encounter issues.