CtrlK
BlogDocsLog inGet started
Tessl Logo

ccg

Claude-Codex-Gemini tri-model orchestration via /ask codex + /ask antigravity (or gemini), then Claude synthesizes results

64

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-structured, actionable orchestration workflow with concrete commands, a clear sequenced process, and appropriate error-recovery fallbacks. The primary weakness is redundancy between the 'How It Works' and 'Execution Protocol' sections, which cover the same flow twice.

Suggestions

Consolidate the 'How It Works' and 'Execution Protocol' sections into a single sequenced workflow to remove the duplicated decompose -> invoke -> collect -> synthesize description.

If a brief 'How It Works' overview is kept, reduce it to a one-line summary and defer all step detail to the 'Execution Protocol' to avoid restating the same four steps.

DimensionReasoningScore

Conciseness

The body is mostly efficient and avoids explaining known concepts, but the 'How It Works' code block and the 'Execution Protocol' section both describe the same decompose -> invoke -> collect -> synthesize flow, which is duplicative and could be tightened.

2 / 3

Actionability

It provides concrete, executable commands ('omc ask codex "<codex prompt>"', 'npm install -g @openai/codex', 'agy --version'), specific artifact paths ('.omc/artifacts/ask/codex-*.md'), and concrete guidance on what each advisor prompt should cover.

3 / 3

Workflow Clarity

The process is clearly sequenced into numbered steps (Decompose -> Invoke -> Collect -> Synthesize) with an error-recovery 'Fallbacks' section and a synthesis checklist that explicitly calls out conflicts and chosen direction.

3 / 3

Progressive Disclosure

The skill is self-contained in a single well-organized file with clear sections (When to Use, Requirements, How It Works, Execution Protocol, Fallbacks, Invocation) and needs no external references.

3 / 3

Total

11

/

12

Passed

Description

67%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific and distinctive, clearly conveying the mechanism (call codex + antigravity/gemini, then synthesize) and its niche. Its main weaknesses are the absence of explicit 'when to use' trigger guidance and reliance on technical/command jargon over natural user phrasing.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when you want a second opinion or cross-check from multiple models before deciding.'

Include natural trigger terms users would actually say, such as 'second opinion', 'cross-check models', or 'compare model outputs', rather than only command syntax like '/ask codex'.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'tri-model orchestration via /ask codex + /ask antigravity (or gemini), then Claude synthesizes results' — naming the specific calls and the synthesis step rather than vague language.

3 / 3

Completeness

It clearly states what the skill does but has no 'Use when...' clause or equivalent explicit trigger guidance, so completeness is capped at 2 per the judging guidelines.

2 / 3

Trigger Term Quality

Terms like 'tri-model orchestration', '/ask codex', and '/ask antigravity' are command syntax/jargon rather than natural user phrasing; the model names (codex, gemini, antigravity) are relevant but common variations like 'second opinion' or 'cross-check models' are missing.

2 / 3

Distinctiveness Conflict Risk

The tri-model orchestration niche via specifically named external CLIs (Codex, Antigravity/Gemini) plus synthesis is a clear, distinct niche unlikely to trigger for unrelated skills.

3 / 3

Total

10

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
Yeachan-Heo/oh-my-claudecode
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.