Starlight-IntelligenceStarlight-Intelligence/starlight-agent-skills/skills/coding/starlight-ceo-review/SKILL.mdstarlight-ceo-review
Skill1 starsChanged 4 months agoMITView on GitHub
Review a proposal from the accountable founder or product-owner perspective: user value, strategic fit, economics, evidence, sequencing, and human responsibility. Use when a plan needs a build/revise/defer decision or when ambition may be obscuring the actual outcome.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- frankxai/starlight-agent-skillsword for word, first seen Jul 27, 2026
Other versions1 project uses a version of this.
Word for word · 1
- frankxai/starlight-agent-skills★ 1100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository43 other files it gives its agents.
- AGENTS.mdAGENTS.md
- adapters/claude.mdCLAUDE.md
- arcanea-mythic-overlaySkill
- frankx-authority-postSkill
- starlight-voiceSkill
- cosmic-code-labSkill
- starlight-autoplanSkill
- starlight-design-reviewSkill
- starlight-devex-reviewSkill
- starlight-eng-reviewSkill
- starlight-investigateSkill
- starlight-qaSkill
- starlight-shipSkill
- starlight-specSkill
- apod-to-shortSkill
- arxiv-space-paper-to-briefSkill
- cosmic-mythic-overlaySkill
- nasa-image-to-atlas-pageSkill
- rights-check-nasa-esaSkill
- rocket-launch-to-reelSkill
- space-social-repurposerSkill
- coding-challenge-generatorSkill
- explain-like-cosmic-professorSkill
- simulation-lab-builderSkill
- caption-and-hashtagSkill
- nasa-image-to-shortSkill
- rocket-launch-to-youtubeSkill
- social-repurposerSkill
- thumbnail-conceptSkill
- arxiv-paper-to-briefSkill
- claim-verificationSkill
- mission-page-to-summarySkill
- media-studioSkill
- publishing-studioSkill
- software-studioSkill
- template-studioSkill
- world-experience-studioSkill
- affiliate-auditSkill
- agentic-incomeSkill
- capability-foundrySkill
- notion-operating-systemSkill
- payments-mandateSkill
- swarm-queen-coordinationSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
Test whether a proposal deserves to exist and whether its scope serves the intended user without transferring hidden cost, liability, or …
- Distinctive: line 29
Test the user problem and the proposed mechanism separately.
- Distinctive: line 41
Use current product evidence, customer research, financial assumptions, and primary market sources.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Starlight CEO Review
Purpose
Test whether a proposal deserves to exist and whether its scope serves the intended user without transferring hidden cost, liability, or support burden to the operator.
When it fires
- A material feature, product, partnership, or platform investment needs a decision.
- The plan contains unverified market, cost, or adoption assumptions.
- Scope is either artificially narrow or expanding without evidence.
Inputs
- Target user, job to be done, and desired behavior change.
- Evidence of demand and alternatives already available.
- Revenue or mission hypothesis, operating cost, support owner, and constraints.
- Reversibility, legal/privacy implications, and success thresholds.
Workflow
- State the decision and the evidence required to make it.
- Test the user problem and the proposed mechanism separately.
- Compare build, integrate, partner, defer, and do-nothing options.
- Identify the smallest coherent scope that delivers the full promised outcome.
- Surface lifecycle cost: maintenance, support, security, compliance, and migration.
- Define leading indicators, stop conditions, and the next human decision.
Output contract
Return a verdict of build, revise, defer, or stop, followed by evidence, assumptions, strategic fit, alternatives, scope corrections, operating-owner obligations, metrics, and human gates.
Tools & MCP
Use current product evidence, customer research, financial assumptions, and primary market sources. Do not invent demand, ROI, partner approval, or “zero liability.”
Quality bar
- Ambition is connected to a concrete user outcome.
- Completeness means the promise works end to end, not that every imaginable feature ships.
- Human and agent effort estimates include uncertainty and operating cost.
- Irreversible or public decisions remain human-owned.
Example
Input: “Should we fork an agent runtime?”
Good output: compare a profile/adapter layer against a fork, price the maintenance and support obligations, define the evidence that would justify owning the runtime, and recommend the reversible path until that evidence exists.
Built on SIP — Starlight Intelligence Protocol Vertical: starlight-agent-skills · portable capability layer
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.