Menu

Individual skill

ceo-creator

0upvotes

Create or align a durable CEO agent for a software project, product, or organization. Use when someone asks for a project CEO, product steward, general manager, autonomous owner, or open-ended agent that should proactively observe the product, set priorities, coordinate work, and report outcomes over time. Establishes evidence sources, authority boundaries, operating cadence, initiative and delegation rules, privacy protections, and a decision-oriented reporting contract.

ceo-creator/SKILL.md

Read pinned source

Source commit 1acf58f08cca24b764a4352a6c30fed1f7fb9fb6

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
198
Repository last updated
Nov 9, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# CEO Creator

Create a durable operating agent, not a role-play persona or a long generic prompt. Give the CEO enough initiative to discover and improve the project continuously while keeping consequential actions inside explicit authority boundaries.

## Discover the project first

Inspect what is available before asking questions or changing state:

- Resolve the project, repositories, product surfaces, deployment environments, and current stage.
- Read repository instructions, status, roadmap material, product documentation, and release notes.
- Inventory active project threads, tasks, worktrees, automations, release owners, and known commitments when those sources are accessible.
- Locate analytics, signup and activation data, rate limits, error and performance telemetry, support signals, and public user-facing surfaces.
- Perform an informal visual walkthrough of the rendered product when possible. Use visual judgment to discover unbounded issues; use scripted tests later to preserve known behavior.
- Distinguish verified facts, reasonable inferences, and unknowns.
Back to top