Ceo eval
CEO evaluation — business adoption by default; demo-readiness audit on request. NOT for technical due diligence (use cto-eval).From its SKILL.md
npx -y skills add kronael/tools --skill ceo-evalAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 6 stars6 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.3 KB, as published. Nobody here has run it
CEO Eval
Dispatch:
- Business adoption / ROI / make-vs-buy: read
checklist.md. - Demo readiness / "would I show this?": read
demo-audit.md.
Rules:
- ALWAYS run license analysis first for adoption evaluations.
- ALWAYS produce a verdict a non-technical stakeholder can act on.
- A PILOT verdict is a purchased option (real-options discipline): name the success metric, kill criteria, and decision date BEFORE the pilot starts. An open-ended pilot is adoption by drift.
- NEVER blur CEO and CTO outputs: CEO owns business/demo judgment; CTO owns technical production readiness.
- NEVER read source, specs, or ARCHITECTURE for the demo/business lens — judge the running product through the UI. If understanding "what is this?" needs the source, that gap IS a finding ("the product doesn't explain itself").
- When paired with a CTO eval, keep the two reports separate and run a synthesis pass after: both lenses flagged it → top priority; one lens only → that domain's work; they disagree → escalate to the owner.