antigravity-workflows

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

1.68x

Quality

41%

Does it follow best practices?

Impact

91%

1.68x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/antigravity-workflows/SKILL.md

The canonical home for this skill is antigravity-workflows in sickn33/agentic-awesome-skills

Quality

Content

50%Scale 1-3

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 high-level orchestration framework but lacks the concrete, actionable detail needed to be truly effective. The workflow steps are abstract ('invoke recommended skills,' 'verify completion criteria') without showing what these look like in practice. The referenced external files (docs/WORKFLOWS.md, data/workflows.json) are not provided in the bundle, making it impossible to verify the skill's completeness.

Suggestions

Add a concrete example of one complete workflow execution (e.g., 'ship-saas-mvp') showing the actual steps, skill invocations, and specific completion criteria for each phase.

Define explicit failure handling: what should happen when a step's completion criteria aren't met, including a validate-fix-retry loop.

Include or provide the referenced docs/WORKFLOWS.md and data/workflows.json files so the skill's references are verifiable and the content is self-contained.

Remove or consolidate the 5 copy-paste prompts into 1-2 examples—they are repetitive and consume tokens without adding value.

Dimension	Reasoning	Score
Conciseness	The skill is reasonably concise but includes some unnecessary sections like 'Copy-Paste Prompts' (5 examples that are largely redundant) and 'Limitations' that explain obvious things. The 'When to Use This Skill' section partially restates what the description already conveys.	2 / 3
Actionability	The workflow steps (identify outcome, propose workflows, execute step-by-step) provide a reasonable process but remain abstract—there are no concrete examples of what 'invoke recommended skills' or 'verify completion criteria' actually look like in practice. No executable code or specific commands are provided; the skill relies entirely on references to external files (docs/WORKFLOWS.md, data/workflows.json) without showing any actual workflow content.	2 / 3
Workflow Clarity	There is a clear 5-step sequence with some validation elements (verify completion criteria, validation evidence at the end), but the verification steps are vague and implicit rather than explicit. There's no feedback loop for what happens when a step fails or completion criteria aren't met, which is important for a multi-phase orchestration skill.	2 / 3
Progressive Disclosure	The skill references external files (docs/WORKFLOWS.md, data/workflows.json) and related skills, which is good progressive disclosure structure. However, no bundle files are provided, so these references are unverifiable. The SKILL.md itself could benefit from showing at least a brief example of one workflow's steps inline before pointing to external files.	2 / 3
	Total	8 / 12 Passed

Description

32%Scale 1-3

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 workflow types, which gives it some identity, but it lacks concrete action verbs and an explicit 'Use when...' clause. The trigger terms are a mix of useful domain keywords and internal jargon, and the broad scope across four domains increases conflict risk with more specialized skills.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user wants to run a multi-step workflow spanning project setup, security review, agent creation, or browser testing.'

Replace vague 'orchestrate' with concrete actions like 'coordinates project scaffolding, runs security scans, configures AI agent pipelines, and executes browser-based QA tests'.

Include natural user-facing trigger terms such as 'build an app', 'full project setup', 'end-to-end workflow', 'pen test', 'QA testing' to improve keyword coverage.

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 (orchestrates 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, bringing this to a 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 'QA testing'.	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 handling each of those areas separately.	2 / 3
	Total	7 / 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: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/antigravity-workflows/SKILL.md
Commit: 7520423

Reviewed: ~11 hours 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.