reports

Name: reports
Availability: InStock
Author: himes19

Generates .report.json configs and renders CRM charts from workspace data.

Updated Apr 12, 2026

Search Tags:#charts #dashboard #json #crm #sql #report-generation #pivot-views

Ready to run

npx skills add https://github.com/himes19/pulsevolt-infra --skill reports-himes19

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: reports
Source: https://github.com/himes19/pulsevolt-infra/tree/main/skills/crm/reports
Command: npx skills add https://github.com/himes19/pulsevolt-infra --skill reports-himes19

SYSTEM DOCUMENTATION & REQUIREMENTS

## What problem does it solve? CRM teams need a scalable way to generate, organize, and share dashboards and inline charts from workspace data without writing repetitive SQL or JSON configurations.

## Core Features & Use Cases

Generate .report.json configurations for interactive charts (bar, line, area, pie, donut, radar, scatter, funnel) and inline chat reports.
Use post-report checklists to ensure PIVOT views exist and queries are safe, and save reports in workspace paths for reuse.
Leverage v_{object} PIVOT views to power deterministic SQL across CRM objects.

Quick Start

Create a basic .report.json in your workspace to render a simple CRM chart panel, such as deals by stage.

Frequently Asked Questions about reports

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

FAQPage Schema

How do I generate interactive CRM charts without writing SQL manually?▼

You can generate CRM charts by creating .report.json configurations that leverage v_{object} pivot views for deterministic SQL, automating chart rendering without manual queries.

What chart types are supported when building inline dashboards from workspace data?▼

Inline dashboards support bar, line, area, pie, donut, radar, scatter, and funnel chart types rendered directly from workspace data using .report.json schemas.

How does the post-report checklist ensure safe query generation?▼

The post-report checklist enforces safe queries by verifying required PIVOT views exist and validating query safety before saving the .report.json configuration in workspace paths.

Can I use pivot views to filter CRM objects across multiple report configurations?▼

Yes, v_{object} PIVOT views power deterministic SQL across CRM objects, allowing you to apply filters and generate multiple .report.json configurations for reuse.

What is the best way to organize and reuse CRM report configurations?▼

Save .report.json configurations in workspace paths for reuse, applying the post-report checklist to ensure PIVOT views exist and queries remain safe across CRM objects.