skill-ceo-review
Skill17 starsChanged 48 days agoNo licenceView on GitHub
CEO/founder-mode review for skill creation and improvement. Challenges whether the skill is solving the right problem, surfaces the 10x version, and stress-tests the design before you invest in writing test cases. Four modes: SCOPE EXPANSION (dream bigger — what should this skill really do?), SELECTIVE EXPANSION (hold scope + cherry- pick improvements), HOLD SCOPE (maximum rigor on the current design), SCOPE REDUCTION (strip the skill to its sharp edge). Use when asked to "rethink this skill", "is this ambitious enough", "challenge my skill design", "think bigger about this skill", or "review my skill before I build it". Proactively suggest when the user seems uncertain about what their skill should do, when the skill description feels generic, when the skill is doing too many things, or when the user has just written a first draft and wants honest feedback before testing.
In this repository31 other files it gives its agents.
- ai-paper-readerSkill
- alignSkill
- askSkill
- blueprintSkill
- cavemanSkill
- checkSkill
- claude-cliSkill
- clean-codeSkill
- codex-cliSkill
- cog-replicateSkill
- colab-cliSkill
- debug-issueSkill
- execute-processSkill
- executeSkill
- interface-designSkill
- jammingSkill
- log-papercutsSkill
- opencode-cliSkill
- opencode-fusionSkill
- planSkill
- quick-decisionSkill
- reddit-post-builderSkill
- seedance-prompt-enSkill
- senior-engineer-brainstormSkill
- simple-writingSkill
- slack-notifySkill
- sleep-on-doneSkill
- steve-jobs-thinkingSkill
- TerminalSkill
- the-razorSkill
- wdytSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
16 rules. About 0 are common, 12 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈12
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “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.
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.