agents/reports/ltx-sales-daily-report/SKILL.md
Generate LTX Studio sales opportunities report and credit limit alerts. Covers pipeline by rep/product (yesterday + QTD), new PELs/PQLs, future meetings, and enterprise orgs at 80%+ token usage. Use when: sales standup, pipeline review, account health check, or when asked for 'sales numbers' or 'credit alerts'.
npx skillsauth add lightricks/ltx-analytics-agents ltx-sales-daily-reportInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Two reports delivered to #ltx-sales-auto-report:
bq --project_id=ltx-dwh-explore query --use_legacy_sql=false --format=pretty "$(cat queries/sales_opportunities_daily_report.sql)"
The query returns:
Key tables:
ltx-dwh-prod-processed.marketing.final_sf_lead_opportunityltx-dwh-prod-processed.web.pql_ltxstudio_leads_for_sfFormat per references/report-template.md (Sales Opportunities section).
bq --project_id=ltx-dwh-explore query --use_legacy_sql=false --format=pretty "$(cat queries/credit_limit_alerts_by_org_active.sql)"
Only orgs active in last 7 days at 80%+ usage.
Format per references/report-template.md (Credit Limit Alerts section).
Enterprise segmentation logic: See shared/bq-schema.md
shared/product-context.md — LTX Studio overview, user types, business modelqueries/credit_limit_alerts_by_org_active.sql — Credit limit alerts (active orgs only)references/sales-opportunities-spec.md — Opportunities query structure and tablesreferences/report-template.md — Output formatting example--project_id=ltx-dwh-exploreis_enterprise_user flag — use org-based enterprise logicltx_studio = true on sales funnel tableopportunity_id is not null for actual opportunities onlySAFE_DIVIDE for all percentage calculationsUser: "Sales opportunities report"
User: "Show me the pipeline by rep"
User: "Credit limit alerts"
User: "Which enterprise accounts are near their credit limit?"
User: "Run the sales report"
development
Adds the analyst layer (segmentation framing, filter/KPI surfacing, LTX-specific definitions, contextual follow-ups) on top of any Data MasterMind data interaction for LTX stakeholders (PMs, marketers, design, leadership). Wraps `get-data` / `validate-data` / `understand-data` / `visualize-data` — dialing intensity from a full guided session (for "look into X", "investigate Y", "do an analysis of …") down to a compressed wrap (for "what's MRR?", "is this number right?"). Output mode (chat-only or HTML artifact) is chosen up front for session-style asks. Always asks about Enterprise / paid non-Enterprise / Free segmentation and Studio-feature tier-gating when relevant. Do NOT use only when the user explicitly opts out ("just give me the number, no extras") or for templated feature dashboards (that's the Hex-based `dashboard-builder`).
data-ai
Generate LTX Studio product daily report with revenue, usage by segment (Enterprise, Pilot, Paying Non-Enterprise, Free), and DoD/DOW-avg comparisons. Use when: daily product standup, executive reporting, or when asked for 'yesterday's product numbers'.
data-ai
Generate LTX Studio marketing & sales daily report with lead gen, spend, PELs/PQLs, sales metrics, and top org usage vs 7-day averages. Use when: daily marketing standup, GTM review, or when asked for 'marketing numbers' or 'lead performance'.
tools
Generate the LTX weekly leadership Slack post covering Open Source (HuggingFace LTX-2 family), API (revenue, endpoints, leads, industries), and Studio Enterprise (contracts, pilots, LTX-model consumption share). Runs every Monday via n8n: BigQuery → JSON parse → Slack render → LLM TL;DR → Slack webhook. Use when: weekly exec update, leadership Slack channel automation, or when asked for 'last week's LTX numbers'.