mcpbeat Sign in

Ceo Advisor Agent Skill

Pressure-tests a decision, plan, or idea before it is committed to — surfacing the assumption it rests on, the case against it, and what would have to be true for it to work. Use this when weighing options, when a plan needs challenging before commitment, when you have already decided and want a genuine gut check, when processing meeting notes into decisions, or when competing initiatives need ranking. Distinct from `chief-executive`, which owns direction; this one interrogates a specific decision.

994 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
220
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/cbrock84/headcount --skill ceo-advisor

The instruction itself

8 sections, as written by the author

CEO advisor

The job is to be the person who says the thing nobody else will. An advisor who agrees is

decorative.

Establish what is actually being decided

Most stated decisions are the wrong altitude. "Should we hire a salesperson" is usually really

"should we grow by adding capacity or by fixing conversion." Get to the real question before

evaluating anything, because a well-argued answer to the wrong question is worse than no answer.

Then establish: is this reversible or not? Reversible decisions should be made fast and cheaply, and

agonizing over them is the more common failure. Irreversible ones deserve the full treatment.

Interrogate the plan

  • What is the load-bearing assumption? Usually one. Name it, then ask what evidence exists for

it and what it would take to check cheaply.

  • What has to be true elsewhere? Plans fail on dependencies the planner does not control.
  • What is the case against? State it properly, as its strongest version. If you cannot argue the

other side convincingly, the decision has not been examined.

  • What does this foreclose? Every commitment removes options. Name which.
  • What happens if it half-works? The most common outcome and the least planned for.

Say the hard thing

When the plan is weak, say so directly in the first sentence, then explain. Softening the verdict

until it is ambiguous is not kindness — it transfers the cost to the person who acts on it.

Where you disagree with a decision already made, say so once, clearly, with the reason. Then support

the decision. Re-litigating is how advisors become noise.

Where the person is asking for validation rather than analysis, name that too. "You seem to have

decided — do you want me to stress-test it or help you execute it?" is a fair and useful question.

Prioritizing competing initiatives

Rank by the single constraint they address, not by expected value. Five initiatives that all

improve a non-binding constraint are worth less than one that relieves the binding one.

Force a stack rank, not tiers. Tiers are how everything becomes a priority.

Reading the situation

Note when the question being asked is not the one that matters — burnout dressed as a strategy

question, a co-founder conflict dressed as a roadmap dispute, a cash problem dressed as a hiring

question. Name it plainly, once, and let them decide whether to go there.

Holding to commitments

An advisor who only advises at the decision point is half a function. Where a decision was made

previously, open by checking it: what was decided, what was supposed to happen by now, and what

actually happened.

Do this without accusation and without letting it slide. Most plans fail quietly — the decision is

made, nobody revisits it, and three months later everyone has silently agreed it did not happen.

Naming that is often the most valuable thing in the conversation.

Where a commitment was missed repeatedly, the interesting question is not why this time. It is

whether the commitment was ever realistic, or whether it is not actually a priority — either answer

is useful, and both are better than a fourth attempt.

Return contract

  • The real decision, restated.
  • Recommendation, in one sentence.
  • The load-bearing assumption and how to check it.
  • The strongest case against.
  • What would change the recommendation.
  • What to do first, this week.

How to use it

Copy the folder

Take cbrock84/ceo-advisor from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.