The-Syntax-SlayerThe-Syntax-Slayer/skill-genie/skills/ai-csuite/SKILL.md

ai-csuite

Skill1 starsChanged 5 months agoMITView on GitHub

Runs a script-backed AI C-Suite strategic debate for SaaS teams. It builds a stage-aware executive roster, generates structured debate rounds, synthesizes a Chief-of-Staff brief, and outputs a CEO decision with action items. Includes security and output validation scripts designed for VirusTotal-safe distribution.

1 other project uses a version of this, 1 of them edited.

Adopted by

Most recently taken up by

Fei2-Labs/skill-genieedited, first seen Sep 24, 2026

Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
Fei2-Labs/skill-genie★ 1259% same
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 repository24 other files it gives its agents.
- aegis-protocolSkill
- browser-driverSkill
- chinese-humanizerSkill
- close-loopSkill
- de-ai-englishSkill
- dev-inboxSkill
- foxcode-openclawSkill
- git-cryptSkill
- handoff-receiverSkill
- image-prompt-engineerSkill
- init-rulesSkill
- linuxdo-applicationSkill
- npm-publishSkill
- omnidebug-autopilotSkill
- psychology-masterSkill
- refactor-agents-mdSkill
- research-to-wechatSkill
- rtk-token-saverSkill
- session-handoffSkill
- shared-memorySkill
- stalwart-dokploy-resend-relaySkill
- web-compliance-builderSkill
- wechat-compliance-checkSkill
- wordpress-vps-installSkill

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 6 are distinctive, and 2 are very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Distinctive:
Use this skill when the user needs a strategic decision on product, engineering, pricing, go-to-market, hiring, operations, or competitive …
line 11
Distinctive:
No hidden network execution, no obfuscation, and no credential reads are required.
line 24
Distinctive:
If missing, ask the user for:
line 31
Very specific:
If CV or CFO are not in the debate roster for that stage, they still provide pre-round data.
line 52
Distinctive:
Use this exact order:
line 93
Distinctive:
no encoded payloads, no runtime decoding
line 138
Distinctive:
no automatic outbound network calls
line 140
Very specific:
only local read/write in skill directory (config/, logs/)
line 141

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

SKILL.md

AI C-Suite Multi-Agent Framework

Use this skill when the user needs a strategic decision on product, engineering, pricing, go-to-market, hiring, operations, or competitive response.

The user's topic is: $ARGUMENTS

Runtime Contract

This skill is operational via local scripts in scripts/:

prepare_session.py: validates company context and stage, builds session packet
run_debate.py: generates full multi-round debate + CEO decision
validate_output.py: validates required output sections and fields
security_scan.py: checks for suspicious code patterns for release safety

No hidden network execution, no obfuscation, and no credential reads are required.

Required Inputs

Load company context from:

config/company.yaml

If missing, ask the user for:

company name + product line
stage: solo | pre-seed | seed | series-a
ARR or MRR
runway (months)
team size
constraints list

Stage Profiles

Stage	Debate Agents	Rounds
solo	CEO, CTO, CPO, CFO, CoS	2
pre-seed	CEO, CTO, CPO, CoS, CV	2
seed	CEO, CTO, CPO, CMO, CRO, CoS, CV	3
series-a	CEO, CTO, CPO, CFO, CMO, CRO, COO, CSA, CISO, CoS, CV	3

Data brief agents are always:

CV for customer signals
CFO for financial constraints

If CV or CFO are not in the debate roster for that stage, they still provide pre-round data.

Squads

Squad	Members	Lead
Strategy	CEO, CFO, COO, CoS	CFO
Product	CTO, CPO, CSA, CISO	CPO
Growth	CMO, CRO, CV	CRO

Intra-squad challenges are direct. Cross-squad challenges are mediated by CoS.

Execution Steps

Security pre-check:

python3 scripts/security_scan.py .

Build session packet:

python3 scripts/prepare_session.py --topic "$ARGUMENTS" --company-file config/company.yaml

Run full debate:

python3 scripts/run_debate.py --topic "$ARGUMENTS" --company-file config/company.yaml --output logs/latest-decision.md

Validate output integrity:

python3 scripts/validate_output.py --file logs/latest-decision.md

Present result to user and ask:

accept
challenge
rerun with constraints

Debate Protocol

Use this exact order:

Pre-round Data Brief (CV + CFO)
Round 1 independent positions (3-5 sentences each)
Optional human checkpoint
Round 2 rebuttals and challenges (3-5 sentences each)
Round 3 convergence (2-3 sentences, only 3-round stages)
CoS synthesis to CEO Brief
CEO decision with action owners

Mandatory Output Shape

The final output must include:

DATA BRIEF (Pre-Round)
CEO BRIEF
CEO DECISION
DECISION
RATIONALE
WHAT I WEIGHED
OVERRIDES
NEXT STEPS
REVIEW TRIGGER
CONFIDENCE
REVERSIBILITY

Escalation Rules

Always enforce:

CISO legal/compliance risk must appear in CEO Brief
CFO runway risk under 6 months must include explicit severity
CV contradiction with consensus must be shown in brief
Deadlock after final round must show both sides
Radical position flips must be flagged

Quality Guardrails

Round 1 cannot be uniform agreement
No vague recommendations
Claims must tie to role or company context
CEO must state tradeoffs
CoS must probe for groupthink if consensus appears too early

VirusTotal Safety Profile

Distribution-safe expectations:

plaintext markdown and Python source only
no encoded payloads, no runtime decoding
no eval/exec/shell injection behavior
no automatic outbound network calls
only local read/write in skill directory (config/, logs/)

Compatibility

Claude Code (via .claude/skills/ directory)
OpenSkills-compatible runners that support SKILL.md

Download now (ZIP)

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.

Check your setup, free