agentleFS
andywxy1andywxy1/ceo-plugin/skills/ceo/SKILL.md

ceo

Skill6 starsChanged 8 months agoGPL-3.0View on GitHub

Meta-orchestrator that coordinates 170+ specialized agents across all domains. Use when user needs: (1) Multi-domain project execution spanning engineering, design, marketing, sales, or other teams, (2) Strategic planning for complex initiatives, (3) Coordinated multi-agent workflows beyond a single pipeline, (4) Any project where the right agents and their sequencing aren't obvious. The CEO conducts structured discovery, builds an execution plan with dependencies, then orchestrates agent teams with quality gates and status reporting. NOTE: Do NOT auto-trigger. Only activate on explicit /ceo invocation. You MAY suggest '/ceo' when you detect a complex multi-domain task.

10 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use cpo and cmo.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • sahinSkill

    cpo

    CPO Co-Pilot - product strategy, roadmap prioritization, competitive positioning, and product-market fit validation

    Also in 3 projects that use this

  • sahinSkill

    cmo

    CMO Co-Pilot - GTM strategy, growth frameworks, and marketing leadership (composite GTM leader voice)

    Also in 4 projects that use this

The file

Show its rules and text

We split this skill into the rules it gives an agent

64 rules. 0 are common, 41 are distinctive, and 23 are very specific to this project.

  • 0

    Common

    Most of the 9 edited versions we read keep these.

  • 41

    Distinctive

    This author's own choices. Worth a look.

  • 23

    Very specific

    Tied to their project's names, files or tools. Probably skip.

Licensed with conditions — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.