qbr-deck-assembly

Assembles QBR decks and briefing docs from HubSpot and Postgres data.

20.2k|3.4k|Updated Oct 5, 2024
One-click install
npx skills add https://github.com/kortix-ai/suna --skill qbr-deck-assembly
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qbr-deck-assembly
Source: https://github.com/kortix-ai/suna/tree/main/packages/starter/templates/marketplace/runtime/skills/qbr-deck-assembly
Command: npx skills add https://github.com/kortix-ai/suna --skill qbr-deck-assembly

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Preparing quarterly business reviews requires manually pulling usage data, health scores, support tickets, and expansion signals from multiple systems, then assembling them into a consistent deck for every account due that week.

Core Features & Use Cases

  • Due-account discovery: Reads the QBR date property in HubSpot and selects every account whose next review falls within the configured lookahead window.
  • Read-only data pulls: Queries Postgres for usage and adoption trends across three quarters and HubSpot for health scores, support summaries, CSM notes, and expansion signals.
  • Draft deck and briefing doc generation: Creates a seven-section Google Slides deck plus a companion Google Doc with backup detail under the configured decks folder, one pair per due account.
  • Use Case: A weekly cron fires the QBR-prep sweep, and the agent produces a sourced draft deck and briefing doc for each account due, flagging declining usage trends and data-backed expansion opportunities for the CSM.

Quick Start

Ask the agent to run this week's QBR prep sweep and produce draft decks and briefing docs for every account due within the lookahead window.

Frequently Asked Questions about qbr-deck-assembly

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

FAQPage Schema
How do I automate QBR deck preparation for customer accounts?

Run the weekly QBR-prep sweep, which finds accounts whose QBR date falls within the lookahead window, pulls usage trends from Postgres and account data from HubSpot, and assembles a draft deck plus briefing doc per account.

How does the skill decide which accounts are due for a QBR?

It reads the configured QBR date property on every HubSpot account and selects those whose date falls within the lookahead window from today. Accounts with no date value are skipped and noted in the run summary.

Can the agent write back to HubSpot or Postgres during QBR prep?

No. Both connectors are strictly read-only; the agent cannot change usage records, health scores, CSM notes, or deals. The only outputs are the new deck and briefing doc under the decks folder.

What data sources does QBR deck assembly require?

It requires read-only access to Postgres for usage and adoption metrics across three quarters, HubSpot for health scores, support tickets, CSM notes, and expansion signals, plus Google Slides and Docs for output.

Why was an account skipped in the weekly QBR sweep?

An account is skipped when its QBR date property has no value, since the skill will not guess a cadence. Skipped accounts are listed in the run summary so the gap can be corrected in HubSpot.

Does the agent send or present the finished QBR deck?

No. The agent's job ends at a finished draft pair under the decks folder. It never shares, presents, emails, or posts the deck or briefing doc; presenting is the CSM's responsibility.