predictleads-dashboard

Generate an HTML dashboard from cached PredictLeads signals in a local SQLite database.

277|88|Updated Jan 4, 2026
One-click install
npx skills add https://github.com/Othmane-Khadri/YALC-the-GTM-operating-system --skill predictleads-dashboard
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: predictleads-dashboard
Source: https://github.com/Othmane-Khadri/YALC-the-GTM-operating-system/tree/main/.claude/skills/predictleads-dashboard
Command: npx skills add https://github.com/Othmane-Khadri/YALC-the-GTM-operating-system --skill predictleads-dashboard

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns cached PredictLeads results in your local SQLite database into a fast, shareable visual dashboard so you can review lead-quality signals without re-fetching or writing custom views.

Core Features & Use Cases

  • Signal-browsing HTML: Produces a single self-contained HTML page with per-company cards, signal count badges, and expandable details.
  • Review and filtering: Supports vertical filtering and sorting by signal density or recency to quickly compare candidates.
  • No extra API calls: Reads only from ~/.gtm-os/gtm-os.db, using the already-cached signals for a zero-network review flow.

Quick Start

Run predictleads-dashboard for a set of domains you already fetched in your local cache, then open the generated HTML to review and share the signal context with your teammate.

Frequently Asked Questions about predictleads-dashboard

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

FAQPage Schema
How do I visualize cached PredictLeads signals for prospect review?

An HTML dashboard visualizes cached PredictLeads signals by reading from your local SQLite database, compiling per-company signal counts and rendering filter and sort UI into a single self-contained file for prospect review.

Can I browse PredictLeads lead signals without making external API requests?

Yes, you can browse lead signals without making external API requests because the dashboard reads exclusively from the local SQLite cache at ~/.gtm-os/gtm-os.db, enabling a zero-network review flow for previously fetched data.

What's the best way to share lead signal context with non-technical teammates?

Generate a self-contained HTML dashboard with per-company cards, signal count badges, and expandable details that non-technical teammates can open directly in any browser without needing database access or API credentials.

Does the PredictLeads dashboard support filtering and sorting by signal density?

Yes, the HTML dashboard supports vertical filtering and sorting by signal density or recency, allowing you to quickly compare candidate companies based on their cached signal counts and callout timestamps.

Do I need a populated SQLite cache before generating a PredictLeads dashboard?

Yes, you need previously fetched PredictLeads signals stored in your local SQLite database at ~/.gtm-os/gtm-os.db, as the dashboard only reads cached data and does not fetch new signals or make external API requests.

Why does my PredictLeads dashboard show no data for certain domains?

The dashboard shows no data for domains that have not been previously fetched and cached in your local SQLite database, as it only reads from the existing cache and cannot retrieve signals for uncached domains.