Youtube Search
ZeroPointRepo/youtube-skills
A skill your agent uses when the user wants to find YouTube content on any topic: searching for videos or channels, finding creators who cover a subject, discovering tutorials, talks, or expert…
Build a Quarterly Business Review (QBR) deck structure and narrative for a customer account.
Install Qbr Deck
$ npx skills add mohitagw15856/pm-claude-skills --skill qbr-deck -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills qbr-deck --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/qbr-deck .claude/skills/qbr-deck && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "qbr-deck" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/qbr-deck into .claude/skills/qbr-deck/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qbr-deck", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/qbr-deckType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mohitagw15856/pm-claude-skills --skill qbr-deck -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills qbr-deck --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/qbr-deck .agents/skills/qbr-deck && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "qbr-deck" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/qbr-deck into .agents/skills/qbr-deck/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qbr-deck", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill qbr-deck -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills qbr-deck --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/qbr-deck .cursor/skills/qbr-deck && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "qbr-deck" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/qbr-deck into .cursor/skills/qbr-deck/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qbr-deck", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mohitagw15856/pm-claude-skills.git --path skills/qbr-deck--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mohitagw15856/pm-claude-skills --skill qbr-deck -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills qbr-deck --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/qbr-deck .gemini/skills/qbr-deck && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "qbr-deck" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/qbr-deck into .gemini/skills/qbr-deck/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qbr-deck", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mohitagw15856/pm-claude-skills qbr-deckInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mohitagw15856/pm-claude-skills --skill qbr-deck -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/qbr-deck .github/skills/qbr-deck && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "qbr-deck" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/qbr-deck into .github/skills/qbr-deck/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qbr-deck", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill qbr-deck -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mohitagw15856/pm-claude-skills qbr-deck --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/qbr-deck .opencode/skills/qbr-deck && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "qbr-deck" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/qbr-deck into .opencode/skills/qbr-deck/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qbr-deck", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
qbr-deck- GitHub stars
- 1.4k
- Token cost
- ~2.7k tokens
- SKILL.md length
- 1,475 words
- Files
- 4 (incl. references)
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
Build a Quarterly Business Review (QBR) deck structure and narrative for a customer account.
- Works in 3 steps: [Specific action — owner — by when] → [Specific action — owner — by when] → [Specific action — owner — by when]
- Asked to prepare a QBR
- SKILL.md covers Required Inputs, QBR Principles, Output Format and Slide 1: Agenda (5 min), plus 15 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Qbr Deck is an agent skill from mohitagw15856/pm-claude-skills. Build a Quarterly Business Review (QBR) deck structure and narrative for a customer account. Use when asked to prepare a QBR, business review meeting, executive review, or quarterly check-in with a customer. Produces a slide-by-slide QBR structure with talking points, metrics review, value narrative, and mutual next steps.
Its SKILL.md is about 2.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `references/value-narrative.md`, `references/worked-example.md` and `templates/qbr-outline.md`).
It sits in Sales & Support, covering Customer success and Slides and decks. The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.
When your agent uses it
- Asked to prepare a QBR
- Business review meeting
- Executive review
- Quarterly check-in with a customer
Example prompts
- “/qbr-deck”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- [Specific action — owner — by when]
- [Specific action — owner — by when]
- [Specific action — owner — by when]
What it can do on your machine
Read from SKILL.md and the folder at commit 1cbf1f0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Qbr Deck loads about 2.7k tokens when it runs, and up to ~6.2k if it reads all its reference files. Until then it costs about 83 tokens; SKILL.md has 1,475 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 1,475 words, ~2,737 tokens.
Download SKILL.mdSave it as
.claude/skills/qbr-deck/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- qbr-deck
- description
- Build a Quarterly Business Review (QBR) deck structure and narrative for a customer account. Use when asked to prepare a QBR, business review meeting, executive review, or quarterly check-in with a customer. Produces a slide-by-slide QBR structure with talking points, metrics review, value narrative, and mutual next steps.
QBR Deck Skill
Produce a complete Quarterly Business Review deck — structured, data-backed, and customer-focused. A good QBR demonstrates value delivered, aligns on goals for the next quarter, and strengthens the executive relationship. It should never feel like a product demo or a vendor update.
Required Inputs
Ask for these if not already provided:
- Account name, CSM name, and customer stakeholders attending
- Contract details — ARR, contract start date, renewal date
- Last quarter's goals (from previous QBR or kickoff)
- Usage and adoption data — key metrics for the quarter
- Support summary — tickets raised, resolution time, any escalations
- Business outcomes the customer cares about — what success looks like for them
- Product updates or new features relevant to this customer
- Goals for next quarter
- Any open commercial conversations (expansion, renewal, at-risk signals)
QBR Principles
- Lead with customer outcomes, not product features
- Every metric should connect to a business result the customer cares about
- The agenda is a conversation, not a presentation — build in time for customer input at every stage
- Close with mutual commitments, not just vendor actions
Output Format
QBR: [Account Name] × [Your Company]
[Quarter] [Year] Business Review
Date: [Date] | Location / Call link: [TBC] Customer attendees: [Names and roles] [Your company] attendees: [Names and roles]
Slide 1: Agenda (5 min)
| Time | Topic | Owner |
|---|---|---|
| 0:00 | Welcome and introductions | CSM |
| 0:05 | [Last quarter] — how did we do? | CSM + Customer |
| 0:20 | Value delivered — business impact | CSM |
| 0:35 | What's coming — roadmap preview | CSM / Product |
| 0:45 | [Next quarter] — goals and priorities | Customer |
| 0:55 | Actions and mutual commitments | CSM |
| 1:00 | Close |
Talking point: "We've kept today to 60 minutes. We want as much of this to be a conversation as possible — please push back, redirect, and ask questions throughout."
Slide 2: Where We Are Together (2 min)
Partnership snapshot:
- Customer since: [Date]
- Contract value: £/$/€[ARR]/year
- Renewal date: [Date]
- Active users: [N] of [N] licensed seats ([X]% adoption)
- Products / modules active: [List]
Talking point: "Before we dive in — a quick picture of where we are. [X] months in, [Y] active users, and this is our [Nth] QBR together."
Slide 3: Last Quarter — Goals We Set Together (5 min)
| Goal | Set in [Last QBR / Kickoff] | Status |
|---|---|---|
| [Goal 1] | [What we committed to] | ✅ Achieved / ⚠️ Partial / ❌ Missed |
| [Goal 2] | [What we committed to] | ✅ Achieved / ⚠️ Partial / ❌ Missed |
| [Goal 3] | [What we committed to] | ✅ Achieved / ⚠️ Partial / ❌ Missed |
For any partial or missed goal: state what happened and what changes next quarter.
Talking point: "Let's start with accountability. Here's what we said we'd achieve last quarter — let's be honest about where we landed."
Slide 4: Usage and Adoption (5 min)
Quarter-over-quarter trend:
| Metric | [Q-1] | [Q] | Change |
|---|---|---|---|
| Monthly active users | [N] | [N] | +/-X% |
| Sessions per user per week | [N] | [N] | +/-X% |
| [Key feature 1] adoption | [X]% | [X]% | +/-X% |
| [Key feature 2] adoption | [X]% | [X]% | +/-X% |
Highlights:
- [Positive adoption trend to call out]
- [Feature or workflow with strongest engagement]
Opportunity:
- [Feature with low adoption that could drive more value — link to their goals]
Talking point: "Usage is [up / stable / something we want to talk about]. The area I'd like to focus on is [feature] — we're not seeing the adoption we'd expect given [their goal], and I want to understand why."
Slide 5: Business Impact — Value Delivered (10 min)
Lead with outcomes, not activity.
[Outcome 1: customer's primary success metric]
- Before: [baseline]
- Now: [current state]
- Impact: [quantified business result — time saved, revenue influenced, cost reduced, risk mitigated]
[Outcome 2]
- [Same structure]
[Outcome 3]
- [Same structure]
Customer evidence (use if available):
"[Quote from champion or user about value experienced]"
Talking point: "This is the section I most want your input on. Are these the outcomes that matter to your business? Are there other ways you're measuring success that we should be tracking?"
Slide 6: Support Summary (3 min)
| Metric | This quarter | Last quarter | Trend |
|---|---|---|---|
| Tickets raised | [N] | [N] | ↑ / → / ↓ |
| Average resolution time | [X hrs] | [X hrs] | ↑ / → / ↓ |
| P1 / critical issues | [N] | [N] | ↑ / → / ↓ |
| CSAT score | [X/10] | [X/10] | ↑ / → / ↓ |
Notable issues this quarter:
- [Any escalation or major ticket — brief summary and resolution]
What we're doing differently:
- [Any process change or improvement based on support patterns]
Slide 7: What's Coming — Roadmap Preview (5 min)
Focus only on what's relevant to this customer's goals. Do not dump the full roadmap.
| Feature / Improvement | Expected | Why it matters to [Account Name] |
|---|---|---|
| [Feature 1] | [Q+1] | [Direct link to their goal or pain point] |
| [Feature 2] | [Q+1 / Q+2] | [Direct link] |
| [Feature 3] | [H2] | [Direct link] |
Talking point: "I've filtered the roadmap to what I think matters most to your team. I'd love your reaction — are these the right priorities from your perspective?"
Slide 8: Next Quarter — Your Goals (10 min)
Customer input section — facilitate, don't present.
Prompt questions:
- "What does success look like for your team in [next quarter]?"
- "What's the biggest challenge you're trying to solve in the next 90 days?"
- "Is there anything about the way you're using [product] you want to change?"
Capture live:
| Goal for next quarter | Owner (customer) | How we'll support it | How we'll measure it |
|---|---|---|---|
| [Goal 1] | [Name] | [CSM / product action] | [Metric] |
| [Goal 2] | [Name] | [CSM / product action] | [Metric] |
Slide 9: Mutual Commitments (5 min)
[Your company] commits to:
- [Specific action — owner — by when]
- [Specific action — owner — by when]
- [Specific action — owner — by when]
[Account Name] commits to:
- [Specific action — owner — by when]
- [Specific action — owner — by when]
Next touchpoint: [Date of next check-in or mid-quarter review]
Show full SKILL.md (589 more words)Show less
Slide 10: Thank You + Open Q&A (5 min)
- Recap the one headline from today: [The single most important thing you want them to remember]
- Confirm actions are captured and shared after the call
- Ask: "Is there anything we didn't cover today that you wanted to raise?"
Preparation Checklist
- Usage data pulled and QoQ comparison calculated
- Last QBR goals reviewed — status confirmed before the meeting
- Business outcomes framed in customer language (not product language)
- Roadmap filtered to this account's specific use cases
- Customer's goals for next quarter researched or pre-confirmed with champion
- Executive sponsor briefed on any sensitive topics before the call
- Actions from previous QBR reviewed — any outstanding items addressed
Deeper Materials
This skill ships with support files — use them when they are available:
references/value-narrative.md— The QBR Value Narrative: Their Numbers, Not Your Features. Apply it while producing the output; it carries the calibration and judgment calls the method summary above compresses.templates/qbr-outline.md— a fill-in version of the deliverable with the quality gates inline. Offer it when the user wants to work the document themselves rather than have it generated.
Scoring Rubric (0–40)
Score any output of this skill before handing it over; 32+ is ship-quality.
| Dimension | 0 | 5 | 10 |
|---|---|---|---|
| Outcome framing | Value slide is product activity (logins, sessions, features shipped) dressed as impact | Business outcomes present but unquantified, or quantified in vendor units rather than the customer's own metrics and currency | Every value claim is a before/after in the customer's units (hours, spend, attrition, £/$), and shaky attribution is disclosed rather than claimed |
| Accountability honesty | Last quarter's goals missing, or every goal quietly marked achieved; problems and escalations omitted | Goals graded but misses lack a cause and a changed plan; support issues mentioned only in passing | Every goal graded ✅/⚠️/❌ with cause and corrective plan for misses, and the quarter's worst moment (outage, escalation, disputed number) gets its own airtime with what changes next |
| Customer airtime & facilitation | Deck is a one-way vendor presentation; no customer input sections | Agenda nominally includes customer slots but talking points don't actually hand over the floor, or airtime totals under 20 minutes | Customer holds 20+ minutes by the agenda, the goals slide is pure facilitation with prompts and a live-capture table, and multiple talking points explicitly invite pushback |
| Commitments & relevance | No mutual commitments; roadmap is a full product dump | Commitments exist but are vendor-only or undated; some roadmap items lack a link to this customer's goals | Both sides own named, dated commitments, every roadmap row states why it matters to this account, and a next touchpoint is booked before the deck ends |
Quality Checks
- Every slide has a talking point, not just a title
- Value slide leads with business outcomes, not product activity
- Roadmap preview links each item to a customer goal
- Mutual commitments section has real owners on both sides
- Customer has at least 20 minutes of airtime in the agenda
Anti-Patterns
- Do not fill the QBR with product activity metrics — lead with business outcomes the customer cares about
- Do not present a roadmap without linking each item to a customer goal — vendor priorities are not a QBR agenda
- Do not run a QBR as a one-sided presentation — it must include structured time for the customer to speak
- Do not close a QBR without documented mutual commitments with named owners on both sides
- Do not skip the "what's not working" slide — suppressing problems erodes trust and misses renewal risks
Example Trigger Phrases
- "Prepare a QBR."
- "Build the business review deck for this customer."
- "Prepare the executive review."
- "Plan the quarterly check-in with this account."
© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 3 other files (references) in skills/qbr-deck of mohitagw15856/pm-claude-skills.
- SKILL.md
- references/value-narrative.md
- references/worked-example.md
- templates/qbr-outline.md
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Qbr Deck next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Qbr Deck this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~2.7k | Automated safety check: Pass | MIT | |
| Youtube SearchZeroPointRepo/youtube-skills | 1k | 1 repos | ~1.8k | Automated safety check: Pass | MIT | |
| YtZeroPointRepo/youtube-skills | 1k | 1 repos | ~951 | Automated safety check: Pass | MIT | |
| Loki Modedavila7/claude-code-templates | 33k | 7 repos | ~7.1k | Automated safety check: Warn | MIT | |
| Account Researchexplorium-ai/gtm-skills | 185 | — | ~2.8k | Automated safety check: Pass | MIT | |
| Expansion Retentiontech-leads-club/agent-skills | 7k | — | ~5.6k | Automated safety check: Pass | Custom licence |
Similar skills
Yt
ZeroPointRepo/youtube-skills
A skill your agent uses when YouTube is relevant: pasted video links or IDs, @handles, quick video lookups, summaries, channel latest uploads, topic search, or any request involving YouTube content…
Loki Mode
davila7/claude-code-templates
Multi-agent autonomous startup system for Claude Code. An agent skill from davila7/claude-code-templates.
Account Research
explorium-ai/gtm-skills
Account research skill for Claude Code and Codex: generate a high-signal company intelligence brief including firmographics, technographics, funding history, hiring signals, business events, recent…
Expansion Retention
tech-leads-club/agent-skills
When the user wants to reduce churn, build expansion revenue, automate customer success, or optimize net revenue retention.
Revops
sickn33/agentic-awesome-skills
Design and improve revenue operations, lead lifecycle rules, scoring, routing, handoffs, and CRM process automation.
More from mohitagw15856/pm-claude-skills
All 1,348 skills in this repoCar Tco
mohitagw15856/pm-claude-skills
Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…
Cs Health Scorecard
mohitagw15856/pm-claude-skills
Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.
Exit Waterfall
mohitagw15856/pm-claude-skills
Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.
Feature Prioritisation
mohitagw15856/pm-claude-skills
Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.
Fire Number
mohitagw15856/pm-claude-skills
Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.
Freelance Rate
mohitagw15856/pm-claude-skills
Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.
Related
Categories
Questions about Qbr Deck
What does Qbr Deck do?
Build a Quarterly Business Review (QBR) deck structure and narrative for a customer account. Qbr Deck is an agent skill from mohitagw15856/pm-claude-skills. Build a Quarterly Business Review (QBR) deck structure and narrative for a customer account.
When should I use Qbr Deck?
Qbr Deck fits situations like: asked to prepare a QBR; business review meeting; executive review; quarterly check-in with a customer.
How do I install Qbr Deck in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill qbr-deck -a claude-code`. Or copy the skill folder (skills/qbr-deck in mohitagw15856/pm-claude-skills) into .claude/skills/qbr-deck in your project. Claude Code loads it when a task matches its description.
How do I install Qbr Deck in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill qbr-deck -a codex`. Or copy the skill folder (skills/qbr-deck in mohitagw15856/pm-claude-skills) into .agents/skills/qbr-deck in your project. Codex loads it when a task matches its description.
Can I use Qbr Deck in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitagw15856/pm-claude-skills --skill qbr-deck -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/qbr-deck, .gemini/skills/qbr-deck, .github/skills/qbr-deck and .opencode/skills/qbr-deck in your project.
What does Qbr Deck need to run?
SKILL.md names no scripts, command-line tools or credentials: Qbr Deck is instructions for the agent only.
Does Qbr Deck access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Qbr Deck safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Qbr Deck use?
Qbr Deck is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Qbr Deck use?
About 2.7k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.5k tokens, read only when the agent opens those files.
What are the alternatives to Qbr Deck?
Skills that share tags, products or a category with Qbr Deck: Youtube Search (ZeroPointRepo/youtube-skills, 1k stars), Yt (ZeroPointRepo/youtube-skills, 1k stars), Loki Mode (davila7/claude-code-templates, 33k stars) and Account Research (explorium-ai/gtm-skills, 185 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Qbr Deck?
mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.
Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.