moliboy5000/ccg
plugins/cache/omc/oh-my-claudecode/4.8.2/skills/ccg/SKILL.md
Claude-Codex-Gemini tri-model orchestration via /ask codex + /ask gemini, then Claude synthesizes results
development
Updated Apr 19, 2026
$ install --global
skillsauthnpx skillsauth add moliboy5000/.claude ccgInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 19, 2026, 4:06 AM5.5s1 file scanned
SKILL.md
- name:
- ccg
- description:
- Claude-Codex-Gemini tri-model orchestration via /ask codex + /ask gemini, then Claude synthesizes results
CCG - Claude-Codex-Gemini Tri-Model Orchestration
CCG routes through the canonical /ask skill (/ask codex + /ask gemini), then Claude synthesizes both outputs into one answer.
Use this when you want parallel external perspectives without launching tmux team workers.
When to Use
- Backend/analysis + frontend/UI work in one request
- Code review from multiple perspectives (architecture + design/UX)
- Cross-validation where Codex and Gemini may disagree
- Fast advisor-style parallel input without team runtime orchestration
Requirements
- Codex CLI:
npm install -g @openai/codex(or@openai/codex) - Gemini CLI:
npm install -g @google/gemini-cli omc askcommand available- If either CLI is unavailable, continue with whichever provider is available and note the limitation
How It Works
1. Claude decomposes the request into two advisor prompts:
- Codex prompt (analysis/architecture/backend)
- Gemini prompt (UX/design/docs/alternatives)
2. Claude runs via CLI (skill nesting not supported):
- `omc ask codex "<codex prompt>"`
- `omc ask gemini "<gemini prompt>"`
3. Artifacts are written under `.omc/artifacts/ask/`
4. Claude synthesizes both outputs into one final response
Execution Protocol
When invoked, Claude MUST follow this workflow:
1. Decompose Request
Split the user request into:
- Codex prompt: architecture, correctness, backend, risks, test strategy
- Gemini prompt: UX/content clarity, alternatives, edge-case usability, docs polish
- Synthesis plan: how to reconcile conflicts
2. Invoke advisors via CLI
Note: Skill nesting (invoking a skill from within an active skill) is not supported in Claude Code. Always use the direct CLI path via Bash tool.
Run both advisors:
omc ask codex "<codex prompt>"
omc ask gemini "<gemini prompt>"
3. Collect artifacts
Read latest ask artifacts from:
.omc/artifacts/ask/codex-*.md
.omc/artifacts/ask/gemini-*.md
4. Synthesize
Return one unified answer with:
- Agreed recommendations
- Conflicting recommendations (explicitly called out)
- Chosen final direction + rationale
- Action checklist
Fallbacks
If one provider is unavailable:
- Continue with available provider + Claude synthesis
- Clearly note missing perspective and risk
If both unavailable:
- Fall back to Claude-only answer and state CCG external advisors were unavailable
Invocation
/oh-my-claudecode:ccg <task description>
Example:
/oh-my-claudecode:ccg Review this PR - architecture/security via Codex and UX/readability via Gemini
Related Skills
moliboy5000/figma-generate-diagram
tools
VerifiedTrustedCommunity
MANDATORY prerequisite — load this skill BEFORE every `generate_diagram` tool call. NEVER call `generate_diagram` directly without loading this skill first. Trigger whenever the user asks to create, generate, draw, render, sketch, or build a diagram — flowchart, architecture diagram, sequence diagram, ERD or entity-relationship diagram, state diagram or state machine, gantt chart, or timeline. Also trigger when the user mentions Mermaid syntax or wants a system architecture, decision tree, dependency graph, API call flow, auth handshake, schema, or pipeline visualized in FigJam. Routes to type-specific guidance, sets universal Mermaid constraints, and tells you when to use a different diagram type or skip the tool entirely (mindmaps, pie charts, class diagrams, etc.).
SKILL.mdUpdated Jul 26, 2026
moliboy5000/codex-orchestrator
development
VerifiedTrustedCommunity
DEFAULT PIPELINE for all tasks requiring execution. You (Claude) are the strategic orchestrator. Codex agents are your implementation army - hyper-focused coding specialists. Trigger on ANY task involving code, file modifications, codebase research, multi-step work, or implementation. This is NOT optional - Codex agents are the default for all execution work. Only skip if the user explicitly asks you to do something yourself.
SKILL.mdUpdated Jul 13, 2026
moliboy5000/video-interaction-mapper
development
VerifiedTrustedCommunity
This skill should be used when the user asks to analyze a UI screen recording and map interaction states into Figma. Trigger for requests such as "put video frames in Figma", "extract states from my recording", "map interactions from video to Figma", "analyze this screen recording", "create a storyboard from my video", "deconstruct this interaction in Figma", "annotate the UI states in my recording", or "pull the key moments from this video into Figma". Also trigger when the user references a video file (.mp4, .mov, .webm, .avi) together with Figma, design review, interaction analysis, prototypes, or UI states. The skill extracts key visual moments from a video, infers interaction triggers, and builds an annotated Figma Design storyboard using native Figma annotations and uploaded screenshot assets.
SKILL.mdUpdated Jul 13, 2026
moliboy5000/generate-project-plan
development
VerifiedTrustedCommunity
Generate a FigJam project plan board from a PRD plus codebase context. Interactive flow: research → propose sections → per-section deep research → per-section content + block-shape proposal → create FigJam → skeleton → fill → diagrams → wrap. Each content block (section, nested section, intro callout, table, multi-column text, sticky column, diagram section, metadata strip) has its own subskill reference file. Use when the user asks for 'project plan in FigJam', 'interactive project plan', '/generate-project-plan', or provides a PRD and wants per-section confirmation on content + rendering.
SKILL.mdUpdated Jul 13, 2026