skills/ceo-advisor/SKILL.md
Use when the user is a CEO, founder, or executive facing a decision that feels high-stakes, irreversible, or lonely -- hiring/firing a leader, raising capital, managing a board conflict, navigating a crisis, or deciding whether to pivot. NEVER for generic business strategy Claude already knows (Porter's, SWOT, OKRs) or for operational/IC-level work (marketing plans, code reviews, sprint planning).
npx skillsauth add sharkitect-solutions/sharkitect-claude-toolkit ceo-advisorInstall 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.
| What the CEO says | What they actually need | Why the obvious answer is wrong | |---|---|---| | "Help me write a strategic plan" | A decision about what to STOP doing | Most CEOs have too many initiatives, not too few. Strategy is saying no. | | "I need to hire a VP of Sales" | Diagnosis of why current sales are broken | A VP hire into a broken system produces an expensive firing in 9 months. | | "Should I raise a Series A?" | Clarity on whether the business model works | Raising before product-market fit buys runway but delays the reckoning. | | "My board is difficult" | A pre-wiring and communication discipline | Boards become "difficult" when they learn bad news in the meeting instead of before it. | | "We need to move faster" | Fewer priorities, not more people | Adding headcount to a confused organization makes it slower, not faster. | | "Help me prepare for the board meeting" | Identification of the 1-2 decisions the board should actually make | Board packages that inform without requesting decisions waste everyone's time. | | "I need a crisis plan" | Immediate triage -- is this actually a crisis? | 80% of "crises" are fire drills. Real crises have existential consequences within 90 days. | | "We need to restructure" | Diagnosis of whether the problem is structure or people | Reorgs that move boxes without changing who is in the boxes change nothing. |
When a CEO brings a problem, classify it FIRST. The category determines the approach.
What kind of CEO problem is this?
|
+-- STRATEGY (rare, high-stakes, irreversible)
| Examples: pivot vs persevere, enter new market, M&A, major partnership
| Approach: Force a decision deadline. Gather data for 1-2 weeks max.
| Trap: Analysis paralysis. Strategy decisions degrade with delay.
| Key question: "What would have to be true for this to work?"
|
+-- PEOPLE (emotional, time-sensitive, high organizational impact)
| Examples: fire a leader, resolve co-founder conflict, key person leaving
| Approach: Separate the emotional from the operational. Decide the "what"
| before the "how." Act within days, not weeks.
| Trap: Avoiding the conversation. Every day of delay costs team trust.
| Key question: "If I inherited this team today, would I hire this person?"
|
+-- CAPITAL (irreversible, numbers-driven, long-tail consequences)
| Examples: fundraise, major investment, pricing change, cost restructuring
| Approach: Model 3 scenarios (base, upside, downside). Decide based on
| the downside you can survive, not the upside you hope for.
| Trap: Optimism bias. CEOs systematically overestimate revenue timelines.
| Key question: "Can we survive the downside scenario for 18 months?"
|
+-- CRISIS (urgent, existential risk, public-facing)
| Examples: revenue cliff, PR incident, key customer loss, legal threat
| Approach: See Crisis Taxonomy below. Classify severity first.
| Trap: Treating every urgent thing as a crisis. Most are fire drills.
| Key question: "Does this threaten company survival within 90 days?"
Company dynamics change fundamentally at specific headcount thresholds. Each transition requires a different CEO, or the same CEO behaving like a different person.
1 to 10 people (Founder-Doer)
10 to 30 people (Founder-Manager)
30 to 75 people (CEO-Operator)
75 to 150 people (CEO-Executive)
150 to 500 people (CEO-Institution-Builder)
The Data Dump (50 slides, no narrative)
The "Everything Is Fine" (hiding problems)
The Surprise Ask (requesting something without pre-wiring)
The No-Decision Meeting (presenting info without requesting a vote)
Should you raise external capital?
|
+-- Are unit economics proven (LTV > 3x CAC)?
| +-- NO --> Do not raise. Fix unit economics first. Raising capital to fund
| | negative unit economics buys time but deepens the hole.
| +-- YES --> Continue.
|
+-- Is your market winner-take-all or winner-take-most?
| +-- NO --> Consider bootstrapping. If the market supports multiple winners,
| | you may not need venture speed. Profitable growth > funded growth.
| +-- YES --> Raising makes sense. Speed matters. Continue.
|
+-- Do you have 12+ months of runway right now?
| +-- NO --> Start raising IMMEDIATELY. You are behind.
| | Accept: terms will be worse because you have no leverage.
| +-- YES --> Good position. You have leverage. Be selective.
|
+-- Strategic money or financial money?
+-- STRATEGIC (corporate VC, industry player):
| Good when: you need distribution, partnerships, or domain expertise.
| Bad when: the strategic investor is also a potential acquirer or competitor.
| Watch for: right of first refusal, information rights that leak to competitors.
+-- FINANCIAL (traditional VC, growth equity):
Good when: you need pure capital and operational advice.
Bad when: the investor has a conflicting portfolio company.
Watch for: aggressive liquidation preferences, board control provisions.
Not all crises are equal. Classify before you act.
Revenue Crisis (runway under 6 months)
People Crisis (key person departing, co-founder conflict, culture collapse)
Market Crisis (major competitor move, platform risk, regulatory threat)
Reputation Crisis (PR incident, data breach, public failure)
When hands-on is genius:
When hands-on is pathological:
The test: "Am I doing this because only I can, or because I do not trust my team?" If it is trust, the problem is your hiring, not your involvement.
BEFORE (bad CEO communication in an all-hands during layoffs):
"As you know, the macroeconomic environment has presented challenges across the industry. After careful consideration and strategic review, we have made the difficult decision to right-size our organization to better position ourselves for sustainable long-term growth. This restructuring will affect approximately 15% of our workforce. We remain committed to our mission and confident in our future. HR will be reaching out to affected individuals with details about severance packages and transition support."
Problems: corporate speak hides responsibility, passive voice removes the CEO from the decision, "right-size" is a euphemism that insults everyone's intelligence, no acknowledgment of what the CEO did wrong that led here.
AFTER (honest CEO communication):
"I am letting 45 people go this week. I owe you an honest explanation of why.
We grew too fast in Q2 and Q3 based on revenue projections that did not materialize. That forecasting failure is mine -- I approved the hiring plan.
Here is what happens next. Every affected person gets 12 weeks of severance, 3 months of health insurance, and job placement support starting today. Their managers are having individual conversations right now.
For everyone staying: our runway is now 18 months. We are not doing another round of cuts. I will share our revised financial plan at Thursday's team meeting so you can see the numbers yourselves.
I know trust is earned, not declared. I will answer every question you have."
Why this works: CEO owns the mistake, uses specific numbers, explains what happens next, and does not hide behind euphemisms or committees.
development
When the user wants help with paid advertising campaigns on Google Ads, Meta (Facebook/Instagram), LinkedIn, Twitter/X, or other ad platforms. Also use when the user mentions 'PPC,' 'paid media,' 'ad copy,' 'ad creative,' 'ROAS,' 'CPA,' 'ad campaign,' 'retargeting,' or 'audience targeting.' This skill covers campaign strategy, ad creation, audience targeting, and optimization.
testing
--- name: using-sharkitect-methodology description: Use when starting any conversation in a Sharkitect workspace OR before any task involving NEW pricing, positioning, proposal, strategy, plan-execution, or schema-design work — mandates invocation of Sharkitect-specific methodology skills (pricing-strategy, marketing-strategy-pmm, smb-cfo, hq-revenue-ops, executing-plans, brainstorming) under the same anti-rationalization discipline as using-superpowers. Documentation has failed 4 times across H
testing
Use when user says 'end session', 'wrap up', 'stop for the day', 'done for today', 'close out', 'save session', 'wrapping up', or invokes /end-session. Runs the full 9-step end-of-session protocol: resource audit, MEMORY.md update, lessons capture, plan status, pending items, workspace checklist, .tmp/ audit, git commit+push, Supabase brain sync, session brief, summary. Final step schedules a detached self-kill of the current session ONLY (3s delay) so the window closes cleanly. Other claude.exe processes (active workspaces) are NOT touched -- orphan cleanup is handled separately by Claude-Orphan-Cleanup-Hourly with proper age safeguards. Do NOT use for: mid-session quick saves (use session-checkpoint), skill syncing (use sync-skills.py), brain memory queries (use supabase-sync.py pull), document freshness reviews (use document-lifecycle), resource gap detection (use resource-auditor).
testing
Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's comprehensive "Signs of AI writing" guide. Detects and fixes patterns including: inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, passive voice, negative parallelisms, and filler phrases.