Orchestrate multiple Antigravity skills through guided workflows for SaaS MVP delivery, security audits, AI agent builds, and browser QA.
67
Quality
52%
Does it follow best practices?
Impact
91%
1.68xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/antigravity-antigravity-workflows/SKILL.mdQuality
Discovery
32%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 identifies a clear orchestration role across multiple domains but suffers from missing explicit trigger guidance and relies on internal terminology ('Antigravity skills') that users wouldn't naturally use. The lack of a 'Use when...' clause significantly limits Claude's ability to know when to select this skill over others.
Suggestions
Add an explicit 'Use when...' clause with natural trigger phrases like 'build a SaaS app', 'run a security audit', 'create an AI agent', or 'test in browser'
Replace or explain 'Antigravity skills' with user-facing language, or list the specific skills being orchestrated
Expand with concrete actions for each workflow type (e.g., 'generates project scaffolding, runs security scans, deploys test environments')
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Antigravity skills, SaaS MVP delivery, security audits, AI agent builds, browser QA) and the general action (orchestrate through guided workflows), but doesn't list specific concrete actions within each area. | 2 / 3 |
Completeness | Describes what it does (orchestrate workflows for various tasks) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes some relevant terms like 'SaaS MVP', 'security audits', 'AI agent builds', 'browser QA', but 'Antigravity skills' is internal jargon and missing common user phrases like 'build an app', 'test my site', 'security check'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'Antigravity skills' and specific workflow types provides some distinctiveness, but terms like 'security audits' and 'browser QA' could overlap with standalone security or testing skills. | 2 / 3 |
Total | 7 / 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 content is well-organized and concise, with good progressive disclosure pointing to external workflow definitions. However, it could be more actionable by showing concrete examples of skill invocation syntax and would benefit from explicit error handling/validation checkpoints in the workflow execution process.
Suggestions
Add a concrete example showing the actual syntax for invoking a skill during workflow execution (e.g., what does 'Invoke recommended skills for that step' look like in practice?)
Include explicit error recovery guidance: what should happen if a workflow step fails or completion criteria aren't met?
Consider adding a brief example of what 'Verify completion criteria' looks like for at least one workflow step
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, with no unnecessary explanations of concepts Claude would already know. Every section serves a clear purpose and the bullet points are tight. | 3 / 3 |
Actionability | Provides a clear 5-step process and routing table, but lacks executable code examples. The copy-paste prompts are helpful but the actual workflow execution steps are somewhat abstract (e.g., 'Invoke recommended skills' without showing how). | 2 / 3 |
Workflow Clarity | The 5-step process is clearly sequenced with verification ('Verify completion criteria before moving to next step'), but lacks explicit validation checkpoints or error recovery guidance. What happens if a step fails is not addressed. | 2 / 3 |
Progressive Disclosure | Excellent structure with clear references to external files (docs/WORKFLOWS.md, data/workflows.json) that are one level deep. Content is appropriately split between overview here and detailed playbooks elsewhere. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
5c5ae21
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.