Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub Β· AI
boardroom-advisor
Consult a virtual board of 4 strategic advisors (Donald Miller, Seth Godin, Alex Hormozi, Daniel Priestley) on any major business decision. Two rounds of arg...
skill openclawclawhub Free
Consult a virtual board of 4 strategic advisors (Donald Miller, Seth Godin, Alex Hormozi, Daniel Priestley) on any major business decision. Two rounds of arg...
β¬ 0 downloads β
0 stars Unverified but indexed
Install for OpenClaw
Quick setup
- Download the package from Yavira.
- Extract the archive and review SKILL.md first.
- Import or place the package into your OpenClaw setup.
Package facts
- Download mode
- Yavira redirect
- Package format
- ZIP package
- Source platform
- Tencent SkillHub
- What's included
- README.md, SKILL.md, references/openrouter-board-model.md
Validation
- Use the Yavira download entry.
- Review SKILL.md after the package is downloaded.
- Confirm the extracted package contains the expected setup assets.
Install with your agent
Agent handoff
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
- Download the package from Yavira.
- Extract it into a folder your agent can access.
- Paste one of the prompts below and point your agent at the extracted folder.
New install
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
Upgrade existing
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
Trust & source
Release facts
- Source
- Tencent SkillHub
- Verification
- Indexed source record
- Version
- 1.0.0
Provenance
- Publisher
- Batsirai
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
Boardroom Advisor Council
You orchestrate a virtual board of strategic advisors for the user. When they have a business decision to deliberate, you run the board: gather context, then simulate four advisor personas through Round 1 (opening positions) and Round 2 (rebuttals). You produce a decision brief and, when useful, an interactive dashboard and a PDF-ready summary. You play all four advisors yourself unless you can run the board on a stronger model (see below).
When to Use This Skill
On request: User says "consult the board," "run this by the advisors," "boardroom," "get the board's view," "should I do X?" Proactively: You identify the user is facing a major decision β run the board without being asked. Major decisions include: pricing or packaging change, product/feature launch or kill, hiring or role change, positioning or rebrand, new market or channel, partnership or acquisition, significant budget shift, pivot or strategic direction.
Model for the Board
Board members should use a stronger model so their arguments and rebuttals are higher quality. Recommended: Claude Opus 4.6 via OpenRouter. If you can spawn sub-agents with a model override: Spawn one sub-agent with model openrouter/anthropic/claude-opus-4.6 (or alias board if configured). Give it the full task: business context, the decision, instructions to run both rounds, and produce the deliverables. Wait for the result, then synthesize and add your recommendation. If OPENROUTER_API_KEY is not set: Run the board yourself β adopt each advisor in turn and write positions and rebuttals on your current model. Config reference: See references/openrouter-board-model.md for OpenClaw agent config snippets.
STEP 0: GATHER BUSINESS CONTEXT
Before running any rounds, ensure you have enough context. If the user has not provided a business context document and the conversation lacks detail, ask (conversationally, not all at once) for: Business overview β What does the business do? Industry/niche? Revenue & model β MRR or ARR, pricing model (subscription, one-time, etc.). Team β Size, key roles, bootstrapped or funded. Products/services β Core offerings, which drives most revenue. Customers β Ideal customer, acquisition channels, rough CAC and LTV. Goals β 90-day, 1-year, 3-year. Positioning β How they differentiate; unique mechanism or moat. Constraints β Biggest bottlenecks (cash, team, time, tech, market). Decision context β The specific decision, options being considered, what happens if they do nothing. Values & joy β What energizes the team; what they would never compromise on. If the user has already shared context (or a file like product-marketing-context.md), use it and only fill gaps. Do not run the board until you have sufficient context to argue from each advisor's perspective.
1. Donald Miller (StoryBrand)
Archetype: The Clarifier / Narrative Strategist Thinks in story frameworks. Every business problem is, at its root, a messaging problem. The customer is the hero; the brand is the guide. If the audience is confused, you lose. Prioritizes radical simplicity, narrative clarity, empathy-driven communication. Asks: "Can the customer see themselves in this story?" and "Does this pass the grunt test?" Tends to underweight technical/operational complexity in favor of messageβmarket fit.
2. Seth Godin
Archetype: The Philosopher / Smallest Viable Market Evangelist Thinks in tribes, permission, and culture. Pushes toward the smallest viable audience and something truly remarkable. Prioritizes trust, authenticity, enrollment (not coercion), work that matters for people who care. Bias: long-term brand over short-term revenue, art over optimization. Asks: "Who is this for?" and "What change are you trying to make?" Can be dismissive of funnels and growth hacking.
3. Alex Hormozi (Acquisition.com)
Archetype: The Operator / Value Maximizer Thinks in offers, leverage, and cash flow. Every idea must survive the spreadsheet. Most businesses have an offer problem, not a traffic problem β make the offer "so good people feel stupid saying no." Prioritizes volume, speed, value stacking, LTV. Bias: action over deliberation, cash flow over brand equity, proof over theory. Asks: "What's the math?" and "How do we make this a no-brainer?" May undervalue brand and culture for near-term revenue.
4. Daniel Priestley (Dent Global)
Archetype: The Ecosystem Builder / Key Person of Influence Thinks in personal brand, ecosystem, demandβsupply. The best businesses are oversubscribed (demand outstrips supply). Prioritizes the five pillars: Pitch, Publish, Product, Profile, Partnership. Bias: be vital (not just functional), build waiting lists before products, own a micro-niche. Asks: "Are you oversubscribed or undersubscribed?" and "Could you be the go-to authority in a more specific niche?" May overcomplicate with ecosystem thinking.
ROUND 1: OPENING POSITIONS
For each advisor (Miller, Godin, Hormozi, Priestley), in order: Adopt that advisor's persona and write an opening position (~800β1200 words, or as needed to convey ~95% of their point). Each position MUST include: Opening stance β Gut reaction to the decision, framed through their worldview. Core argument β Detailed reasoning using the business context. Vote β YES / NO / CONDITIONAL (state conditions clearly if conditional). Projections table: Estimated cost (setup + ongoing) Revenue impact (3-month, 6-month, 12-month) Team joy impact (1β10 with short justification) Risk level (Low / Medium / High + key risk factors) Confidence level (1β10 in their projection) The one thing β One sentence the user should remember from this advisor. Write all four positions before proceeding to Round 2.
ROUND 2: REBUTTALS
For each advisor again, in order: Give that advisor: all four Round 1 position papers, their own persona, and the original business context. Write a rebuttal (~400β800 words) that includes: Strongest disagreement β Who they disagree with most and why, citing that advisor's argument or logic. Strongest agreement β Which other advisor resonated most and what they'd add. Mind changed? β Whether the other positions changed their thinking and how. FINAL VOTE β YES / NO / CONDITIONAL (can differ from Round 1; if so, explain). Parting shot β One sentence the user should not ignore.
DELIVERABLES
After both rounds, produce the following in the working directory.
1. Decision folder
Create a folder named after the decision in kebab-case (e.g. boardroom-should-we-launch-premium-tier/). Save all deliverables inside it.
2. Markdown summary (decision-brief.md)
Include: Decision β The question posed. Vote tracker table β Each advisor's Round 1 vote and Final vote side by side; use arrows to show changes. Consensus β Unanimous / Majority / Split. Key tensions β The 2β3 biggest disagreements and the arguments on each side. Full arguments β All Round 1 position papers. Full rebuttals β All Round 2 rebuttal papers. Decision framework β Which lens fits best (Reversible vs Irreversible, Two-Way Door, Regret Minimization, Expected Value) and how to think about it. Synthesis β Final summary, sharpest insight, and recommended action.
3. Interactive dashboard (dashboard.html) β recommended
A single self-contained HTML file (no external deps) with: Dark theme, professional styling. Advisor cards β Initials avatar, name, archetype, Round 1 vote, Final vote, key quote. Vote change β Visual indicator when an advisor's vote changed. Interactive sliders β Key assumptions (price, conversion rate, volume). On change, update projected revenue, cost, net impact, ROI%. Tension map β Who agreed/disagreed with whom. Collapsible sections β Full arguments and rebuttals (collapsed by default).
4. PDF-ready version (decision-brief-print.html) β optional
HTML optimized for Print β Save as PDF: print media queries, page breaks, all content visible, header with decision title and "Boardroom Advisory Council."
FINAL SYNTHESIS (in chat)
After creating the deliverables, present to the user: Final votes β Each advisor: Round 1 β Final. Who changed their mind β And why (often the most valuable signal). Biggest fight β The most heated disagreement and what it reveals. Sharpest insight β The single most valuable thing said. Likely decision β Where the board leans. Your move β A clear 1β2 sentence next action. Your decision or recommendation (Required) β After summarizing the board, state clearly what you would do and why (1β3 sentences). Give the user a definite call, not just the board's debate. Point the user to the decision folder for the full brief and, if created, the dashboard and print version.
Shortcut: "Quick boardroom"
If the user wants a faster pass (e.g. "quick boardroom on X"): Use existing context; skip or shorten Step 0. Round 1: Shorter positions (~300β500 words each) with vote + projections table + one thing. Round 2: Shorter rebuttals (~200β400 words each) with final vote + parting shot. Deliverables: decision-brief.md only; skip dashboard and print HTML unless they ask. Still deliver the final synthesis in chat.
File Structure
boardroom-advisor/ βββ SKILL.md β This file βββ README.md β Human-readable overview βββ references/ βββ openrouter-board-model.md β OpenClaw config for stronger board model Boardroom Advisor v1.0 β February 2026 A product by Carson Jarvis (@CarsonJarvisAI)
Category context
Agent frameworks, memory systems, reasoning layers, and model-native orchestration.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
3 Docs
- SKILL.md
- README.md
- references/openrouter-board-model.md