Ultimate multi-agent framework for Google Antigravity. Orchestrates specialized domain agents (PM, Frontend, Backend, Mobile, QA, Debug) via Serena Memory.
64
45%
Does it follow best practices?
Impact
96%
6.40xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agent-skills/ohmg/SKILL.mdQuality
Discovery
17%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description relies heavily on technical jargon and buzzwords ('Ultimate multi-agent framework', 'Orchestrates', 'Serena Memory') without explaining concrete capabilities or when to use the skill. While it mentions specific agent types, it fails to describe what actions those agents perform or what triggers should cause Claude to select this skill over others.
Suggestions
Add a 'Use when...' clause specifying trigger scenarios, e.g., 'Use when the user mentions Google Antigravity, anti-gravity projects, or needs multi-domain coordination for Antigravity development.'
Replace abstract 'orchestrates' with concrete actions each agent performs, e.g., 'PM agent creates specs, Frontend agent builds UI components, QA agent runs test suites.'
Include natural user-facing keywords that someone would actually say when needing this skill, rather than internal technical terms like 'Serena Memory'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain ('Google Antigravity') and mentions orchestrating specialized agents with specific roles (PM, Frontend, Backend, Mobile, QA, Debug), but doesn't describe concrete actions - only abstract 'orchestrates' without explaining what that means in practice. | 2 / 3 |
Completeness | Partially addresses 'what' (orchestrates agents) but is vague about actual capabilities. Completely missing 'when' - no 'Use when...' clause or explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Uses technical jargon ('multi-agent framework', 'Serena Memory', 'orchestrates') that users wouldn't naturally say. 'Google Antigravity' is the only potentially natural term, but lacks common variations or user-facing keywords. | 1 / 3 |
Distinctiveness Conflict Risk | 'Google Antigravity' provides some distinctiveness, but 'multi-agent framework' and generic agent roles (Frontend, Backend, QA) could overlap with other development or orchestration skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is well-structured and concise, effectively using tables and code blocks to convey information efficiently. However, it lacks depth in workflow clarity for multi-agent coordination scenarios and could benefit from more complete executable examples showing the full orchestration lifecycle with validation steps.
Suggestions
Add a complete workflow example showing the full coordination cycle: PM planning → agent spawn → task execution → QA review, with explicit validation checkpoints between stages
Include expected output examples for key commands like `oh-my-ag agent:spawn` and `/coordinate` so Claude knows what success looks like
Add error recovery guidance for common failure scenarios in multi-agent coordination (e.g., agent spawn failures, memory state conflicts)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Content is lean and efficient with no unnecessary explanations. Tables, code blocks, and quick reference sections maximize information density without explaining concepts Claude already knows. | 3 / 3 |
Actionability | Provides concrete commands and configuration examples, but lacks complete executable workflows. The agent spawning and coordination patterns are shown as snippets rather than full working examples with expected outputs. | 2 / 3 |
Workflow Clarity | Multi-step coordination is mentioned ('PM planning → agent spawning → QA review') but lacks explicit validation checkpoints or error recovery steps. The workflow for complex multi-agent orchestration needs clearer sequencing and feedback loops. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections (Core Concepts, Installation, Usage, Configuration). Content is appropriately structured for a skill overview without unnecessary nesting or monolithic blocks. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
c033769
Table of Contents
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.