antigravity-workflows
Orchestrate multiple Antigravity skills through guided workflows for SaaS MVP delivery, security audits, AI agent builds, and browser QA.
Install with Tessl CLI
npx tessl i github:sickn33/antigravity-awesome-skills --skill antigravity-workflows70
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 lists specific workflow types, which provides moderate specificity. However, it lacks explicit trigger guidance ('Use when...') and relies on specialized terminology that users may not naturally use. The absence of when-to-use criteria significantly limits Claude's ability to select this skill appropriately.
Suggestions
Add an explicit 'Use when...' clause specifying triggers like 'when user wants to build a complete application', 'run a full security review', or 'set up end-to-end testing'
Include more natural user language variations such as 'build an MVP', 'check for vulnerabilities', 'automate browser testing', or 'create an AI bot'
Clarify what 'orchestrate' means concretely - e.g., 'coordinates multiple tools in sequence', 'manages multi-step projects', or 'combines skills for complex tasks'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Antigravity skills, workflows) and lists specific use cases (SaaS MVP delivery, security audits, AI agent builds, browser QA), but 'orchestrate' and 'guided workflows' are somewhat abstract without explaining concrete actions performed. | 2 / 3 |
Completeness | Describes what it does (orchestrate skills for various workflows) 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', 'browser QA', but these are fairly specialized. Missing common variations users might say like 'build an app', 'test my site', 'security check', or 'automation'. | 2 / 3 |
Distinctiveness Conflict Risk | The 'Antigravity skills' reference provides some distinctiveness, but terms like 'security audits' and 'browser QA' could overlap with dedicated security or testing skills. The orchestration role is somewhat unique but not clearly delineated. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured orchestration skill that efficiently communicates its purpose and workflow. The content is appropriately concise for a meta-skill that coordinates other skills. The main weakness is the lack of concrete examples showing actual skill invocation syntax or expected output formats from the referenced workflow files.
Suggestions
Add a concrete example showing what a single workflow step looks like when executed (e.g., 'Step 1: Planning - Invoking @concise-planning with output: [example artifact]')
Include a brief sample of what workflows.json structure looks like so Claude knows the expected schema when reading it
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, avoiding unnecessary explanations. It assumes Claude understands orchestration concepts and gets straight to actionable guidance without padding. | 3 / 3 |
Actionability | Provides a clear 5-step process and routing table, but lacks concrete executable examples. The workflow steps are described procedurally rather than with specific commands or code snippets for invoking skills. | 2 / 3 |
Workflow Clarity | Clear numbered sequence with explicit verification checkpoints ('Verify completion criteria before moving to next step') and defined outputs (artifacts, validation evidence, remaining risks). The workflow structure is well-defined for a meta-orchestration skill. | 3 / 3 |
Progressive Disclosure | Appropriately structured with clear references to external files (docs/WORKFLOWS.md, data/workflows.json) for detailed content. The skill itself serves as an overview with one-level-deep navigation to source materials. | 3 / 3 |
Total | 11 / 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 | |
- 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.