antigravity-workflows

Orchestrate multiple Antigravity skills through guided workflows for SaaS MVP delivery, security audits, AI agent builds, and browser QA.

1.68x

Quality

45%

Does it follow best practices?

Impact

91%

1.68x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/antigravity-antigravity-workflows/SKILL.md

Quality

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 and names four specific workflow domains, which provides some useful context. However, it lacks explicit trigger guidance ('Use when...'), relies on internal terminology ('Antigravity skills'), and doesn't list concrete actions beyond the high-level 'orchestrate' and 'guided workflows'. The breadth of domains covered without clear differentiation criteria increases conflict risk with more specialized skills.

Suggestions

Add an explicit 'Use when...' clause specifying trigger scenarios, e.g., 'Use when the user wants to build a complete SaaS product, run a security audit, create an AI agent, or perform browser-based QA testing across multiple steps.'

Replace internal jargon like 'Antigravity skills' with user-facing language, and add natural trigger terms users would say such as 'build an app', 'launch a product', 'test my site', 'penetration test'.

List more concrete actions for each workflow type, e.g., 'Coordinates project scaffolding, deployment pipelines, vulnerability scanning, agent configuration, and automated browser testing.'

Dimension	Reasoning	Score
Specificity	It names a domain (orchestrating Antigravity skills) and lists several workflow types (SaaS MVP delivery, security audits, AI agent builds, browser QA), but the actions are described at a high level ('orchestrate', 'guided workflows') rather than listing concrete actions like 'generate project scaffolding' or 'run security scans'.	2 / 3
Completeness	It describes what the skill does (orchestrate workflows) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the 'what' is also somewhat vague, placing this at 1.	1 / 3
Trigger Term Quality	Includes some relevant keywords like 'SaaS MVP', 'security audits', 'AI agent builds', and 'browser QA' that users might mention, but 'orchestrate multiple Antigravity skills' is internal jargon. Missing common user-facing variations like 'build an app', 'test my website', 'pen test', or 'create a SaaS product'.	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 the broad scope covering four different domains could overlap with individual skills for each of those areas.	2 / 3
	Total	7 / 12 Passed

Implementation

57%

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

This is a reasonable orchestration skill that provides clear routing logic and a structured execution process, but falls short on actionability—it lacks concrete examples of what a workflow execution actually looks like and relies heavily on external files without showing their structure. The workflow steps need more explicit validation criteria and error recovery paths to be truly robust.

Suggestions

Add a concrete example showing one workflow execution trace (e.g., 'Ship a SaaS MVP' with specific step names, artifacts produced, and validation checks at each stage).

Define explicit completion criteria for each workflow step rather than the vague 'Verify completion criteria before moving to next step'—show what success looks like.

Add a failure/recovery path: what should happen when a step fails or a referenced skill is unavailable, including how to communicate this to the user.

Remove or significantly trim the 'Copy-Paste Prompts' section—these are repetitive and don't add instructional value for Claude.

Dimension	Reasoning	Score
Conciseness	The skill is mostly efficient but includes some unnecessary sections like the 'Copy-Paste Prompts' block (5 examples that are largely redundant) and the 'Limitations' section which states obvious things Claude would already understand. The workflow routing table and execution steps are lean.	2 / 3
Actionability	The skill provides a clear step-by-step process and a routing table, but lacks concrete executable examples. There are no actual code/commands, no sample workflow execution trace, and the guidance relies on external files (docs/WORKFLOWS.md, data/workflows.json) without showing what those contain or how to parse them. The 'Verify completion criteria' step 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 'completion' means at each step.	2 / 3
Progressive Disclosure	The skill appropriately serves as an overview/orchestration layer, pointing to docs/WORKFLOWS.md and data/workflows.json as one-level-deep references. Related skills are clearly listed. The content is well-organized with clear section headers and doesn't try to inline the full workflow definitions.	3 / 3
	Total	9 / 12 Passed

Validation

90%

Warnings & errors only

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: boisenoise/skills-collections
Commit: 431bfad

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.