revenue-truth

Verify revenue and funnel claims against live ThumbGate billing telemetry.

25|7|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/IgorGanapolsky/ThumbGate --skill revenue-truth
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: revenue-truth
Source: https://github.com/IgorGanapolsky/ThumbGate/tree/main/.claude/skills/revenue-truth
Command: npx skills add https://github.com/IgorGanapolsky/ThumbGate --skill revenue-truth

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

It prevents you from making incorrect claims about revenue, conversions, or funnel performance by forcing the agent to use live production billing telemetry instead of stale snapshots or internal planning docs.

Core Features & Use Cases

  • Live revenue verification: Runs the canonical production billing summary pipeline before answering any question involving money, conversion, traffic, or “why we didn’t make X,” and uses the tool output as the only allowed source of truth.
  • Credential-aware sourcing: Clearly reports whether it was able to fetch hosted billing data or had to use a local fallback due to missing keys, so answers don’t silently degrade.
  • Attribution quality and gaps reporting: Includes channel telemetry quality and explicitly calls out what’s missing, reducing the risk of confident but wrong narratives in regulated or audit-heavy contexts.
  • Use Case: When leadership asks for “today’s revenue” or “what drove conversions in the last 30 days,” the skill ensures the response is backed by the live billing endpoint output.

Quick Start

Run revenue-truth to fetch live ThumbGate billing summary output and base any money-related answer strictly on that output.

Frequently Asked Questions about revenue-truth

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

FAQPage Schema
How do I verify live revenue figures before reporting them?

Verify live revenue figures by running a production billing telemetry script before answering. This ensures reported revenue and conversion numbers match live billing telemetry instead of stale snapshots.

What is revenue attribution verification and when do I need it?

Revenue attribution verification confirms paid orders and funnel performance against live billing telemetry. You need it when answering questions about booked revenue or why conversion targets were missed.

How do I prevent incorrect revenue claims in agent-driven reporting?

Prevent incorrect revenue claims by forcing the agent to quote live billing telemetry output. The agent must run a status script first and explicitly state if missing credentials force a local fallback.

Does this approach work without billing telemetry credentials?

It works without credentials but treats the local fallback as non-truth. The agent must explicitly state missing credentials so answers do not silently degrade when hosted billing data is unavailable.

What are the limitations of using local fallback data for funnel analytics?

Local fallback data is treated as non-truth and cannot be quoted as verified revenue. Limitations include missing attribution quality gaps and the inability to support confident claims in audit-heavy contexts.