antigravity-workflows
Orchestrate multiple Antigravity skills through guided workflows for SaaS MVP delivery, security audits, AI agent builds, and browser QA.
59
41%
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 ./plugins/antigravity-awesome-skills-claude/skills/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 domain (multi-skill orchestration for specific project types) but lacks concrete action details and has no explicit trigger guidance ('Use when...'). The reliance on product-specific terminology ('Antigravity skills') without natural user language reduces discoverability, and the absence of when-to-use guidance significantly hurts completeness.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user wants to build a SaaS product end-to-end, run a security audit workflow, create an AI agent project, or perform browser-based QA testing.'
List more concrete actions the skill performs, such as 'generates project plans, coordinates code generation with testing, produces security reports, and runs automated browser checks.'
Include natural trigger terms users would actually say, such as 'build an app', 'full-stack project', 'penetration test', 'end-to-end testing', or 'automated QA'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (SaaS MVP delivery, security audits, AI agent builds, browser QA) and the general action (orchestrate multiple skills through guided workflows), but doesn't list concrete actions like 'generate project scaffolding', 'run security scans', or 'execute browser tests'. | 2 / 3 |
Completeness | Describes what it does (orchestrate skills through guided workflows) but has no explicit 'Use when...' clause or equivalent trigger guidance. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the 'what' itself is also somewhat vague, so this scores a 1. | 1 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'SaaS MVP', 'security audits', 'AI agent builds', and 'browser QA', but these are fairly specific product terms. Missing common natural language variations users might say like 'build an app', 'test my site', 'check security', 'create a startup project', or 'workflow'. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'Antigravity skills' and specific workflow types (SaaS MVP, security audits, AI agent builds, browser QA) provides some distinctiveness, but 'orchestrate multiple skills' is generic enough to potentially overlap with other orchestration or workflow management skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a reasonable orchestration framework with clear routing logic and a defined execution sequence, but it lacks the concrete, actionable detail needed to guide Claude through actual workflow execution. The content is moderately concise but includes redundant sections (5 nearly identical copy-paste prompts, obvious limitations). The absence of bundle files makes it impossible to verify the referenced workflow sources, and the lack of concrete examples of step execution or failure handling weakens both actionability and workflow clarity.
Suggestions
Add a concrete example of executing one workflow end-to-end (e.g., 'ship-saas-mvp') showing what each step produces, which skills are invoked, and what completion criteria look like.
Define explicit validation/failure handling: what happens when a step fails, what retry logic applies, and what constitutes a blocking vs. non-blocking failure.
Consolidate the 5 copy-paste prompts into 1-2 examples with a note that the workflow name can be substituted, reducing token waste.
Provide the referenced bundle files (docs/WORKFLOWS.md, data/workflows.json) or remove the references if they don't exist, as unresolvable references reduce trust in the skill.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably concise but includes some unnecessary sections like 'When to Use This Skill' with bullet points that largely restate the description, and the 'Copy-Paste Prompts' section is repetitive (5 near-identical prompts). The Limitations section also explains obvious things Claude would know. | 2 / 3 |
Actionability | The workflow steps (identify outcome, propose workflows, execute step-by-step) provide a reasonable framework but remain abstract—there are no concrete examples of what 'invoke recommended skills' looks like in practice, no sample workflow execution, and no executable code or commands. The routing table is helpful but the actual execution guidance is vague. | 2 / 3 |
Workflow Clarity | The 5-step execution process is clearly sequenced and includes verification ('verify completion criteria before moving to next step'), but the validation checkpoints are implicit rather than explicit. There's no feedback loop for what happens when a step fails, and no concrete criteria for what 'verify completion' means for each workflow type. | 2 / 3 |
Progressive Disclosure | The skill references `docs/WORKFLOWS.md` and `data/workflows.json` as external sources, which is good progressive disclosure design. However, no bundle files are provided, so these references are unverifiable. The skill itself could benefit from splitting the copy-paste prompts into a separate file, and the inline content is somewhat bloated for what should be an overview. | 2 / 3 |
Total | 8 / 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 | |
- Repository
- sickn33/antigravity-awesome-skills
- Commit
0839f85
- 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.