Awesome-omni-skills antigravity-workflows-v2

Antigravity Workflows workflow skill. Use this skill when the user needs Orchestrate multiple Antigravity skills through guided workflows for SaaS MVP delivery, security audits, AI agent builds, and browser QA and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

install

source · Clone the upstream repo

git clone https://github.com/diegosouzapw/awesome-omni-skills

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/diegosouzapw/awesome-omni-skills "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/antigravity-workflows-v2" ~/.claude/skills/diegosouzapw-awesome-omni-skills-antigravity-workflows-v2 && rm -rf "$T"

manifest: skills/antigravity-workflows-v2/SKILL.md

Antigravity Workflows

Overview

This public intake copy packages

plugins/antigravity-awesome-skills/skills/antigravity-workflows

from

https://github.com/sickn33/antigravity-awesome-skills

into the native Omni Skills editorial shape without hiding its origin.

Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.

This intake keeps the copied upstream files intact and uses

metadata.json

plus

ORIGIN.md

as the provenance anchor for review.

Antigravity Workflows Use this skill to turn a complex objective into a guided sequence of skill invocations.

Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: How to Run This Skill, Copy-Paste Prompts, Limitations.

When to Use This Skill

Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.

The user wants to combine several skills without manually selecting each one.
The goal is multi-phase (for example: plan, build, test, ship).
The user asks for best-practice execution for common scenarios like:
Shipping a SaaS MVP
Running a web security audit
Building an AI agent system

Operating Table

Situation	Start here	Why it matters
First-time use	`metadata.json`	Confirms repository, branch, commit, and imported path before touching the copied workflow
Provenance review	`ORIGIN.md`	Gives reviewers a plain-language audit trail for the imported source
Workflow execution	`resources/implementation-playbook.md`	Starts with the smallest copied file that materially changes execution
Supporting context	`resources/implementation-playbook.md`	Adds the next most relevant copied source file without loading the entire package
Handoff decision	`## Related Skills`	Helps the operator switch to a stronger native skill when the task drifts

Workflow

This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.

docs/WORKFLOWS.md for human-readable playbooks.
data/workflows.json for machine-readable workflow metadata.
Product delivery request -> ship-saas-mvp
Security review request -> security-audit-web-app
Agent/LLM product request -> build-ai-agent-system
E2E/browser testing request -> qa-browser-automation
Domain-driven design request -> design-ddd-core-domain

Imported Workflow Notes

Imported: Workflow Source of Truth

Read workflows in this order:

```
docs/WORKFLOWS.md
```
for human-readable playbooks.
```
data/workflows.json
```
for machine-readable workflow metadata.

Imported: Default Workflow Routing

Product delivery request ->
```
ship-saas-mvp
```
Security review request ->
```
security-audit-web-app
```
Agent/LLM product request ->
```
build-ai-agent-system
```
E2E/browser testing request ->
```
qa-browser-automation
```
Domain-driven design request ->
```
design-ddd-core-domain
```

Imported: How to Run This Skill

Identify the user's concrete outcome.
Propose the 1-2 best matching workflows.
Ask the user to choose one.
Execute step-by-step:
- Announce current step and expected artifact.
- Invoke recommended skills for that step.
- Verify completion criteria before moving to next step.
At the end, provide:
- Completed artifacts
- Validation evidence
- Remaining risks and next actions

Examples

Example 1: Ask for the upstream workflow directly

Use @antigravity-workflows-v2 to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.

Explanation: This is the safest starting point when the operator needs the imported workflow, but not the entire repository.

Example 2: Ask for a provenance-grounded review

Review @antigravity-workflows-v2 against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why.

Explanation: Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.

Example 3: Narrow the copied support files before execution

Use @antigravity-workflows-v2 for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.

Explanation: This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.

Example 4: Build a reviewer packet

Review @antigravity-workflows-v2 using the copied upstream files plus provenance, then summarize any gaps before merge.

Explanation: This is useful when the PR is waiting for human review and you want a repeatable audit packet.

Best Practices

Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.

Keep the imported skill grounded in the upstream repository; do not invent steps that the source material cannot support.
Prefer the smallest useful set of support files so the workflow stays auditable and fast to review.
Keep provenance, source commit, and imported file paths visible in notes and PR descriptions.
Point directly at the copied upstream files that justify the workflow instead of relying on generic review boilerplate.
Treat generated examples as scaffolding; adapt them to the concrete task before execution.
Route to a stronger native skill when architecture, debugging, design, or security concerns become dominant.

Troubleshooting

Problem: The operator skipped the imported context and answered too generically

Symptoms: The result ignores the upstream workflow in

plugins/antigravity-awesome-skills/skills/antigravity-workflows

, fails to mention provenance, or does not use any copied source files at all. Solution: Re-open

metadata.json

ORIGIN.md

, and the most relevant copied upstream files. Load only the files that materially change the answer, then restate the provenance before continuing.

Problem: The imported workflow feels incomplete during review

Symptoms: Reviewers can see the generated

SKILL.md

, but they cannot quickly tell which references, examples, or scripts matter for the current task. Solution: Point at the exact copied references, examples, scripts, or assets that justify the path you took. If the gap is still real, record it in the PR instead of hiding it.

Problem: The task drifted into a different specialization

Symptoms: The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better. Solution: Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.

Related Skills

```
@advogado-especialista-v2
```
- Use when the work is better handled by that native specialization after this imported skill establishes context.
```
@aegisops-ai-v2
```
- Use when the work is better handled by that native specialization after this imported skill establishes context.
```
@agent-evaluation-v2
```
- Use when the work is better handled by that native specialization after this imported skill establishes context.
```
@agent-framework-azure-ai-py-v2
```
- Use when the work is better handled by that native specialization after this imported skill establishes context.

Additional Resources

Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.

Resource family	What it gives the reviewer	Example path
`references`	copied reference notes, guides, or background material from upstream	`references/n/a`
`examples`	worked examples or reusable prompts copied from upstream	`examples/n/a`
`scripts`	upstream helper scripts that change execution or validation	`scripts/n/a`
`agents`	routing or delegation notes that are genuinely part of the imported package	`agents/n/a`
`assets`	supporting assets or schemas copied from the source package	`assets/n/a`

implementation-playbook.md

Imported Reference Notes

Imported: Copy-Paste Prompts

Use @antigravity-workflows to run the "Ship a SaaS MVP" workflow for my project idea.

Use @antigravity-workflows and execute a full "Security Audit for a Web App" workflow.

Use @antigravity-workflows to guide me through "Build an AI Agent System" with checkpoints.

Use @antigravity-workflows to execute the "QA and Browser Automation" workflow and stabilize flaky tests.

Use @antigravity-workflows to execute the "Design a DDD Core Domain" workflow for my new service.

Imported: Limitations

This skill orchestrates; it does not replace specialized skills.
It depends on the local availability of referenced skills.
It does not guarantee success without environment access, credentials, or required infrastructure.
For stack-specific browser automation in Go,
```
go-playwright
```
may require the corresponding skill to be present in your local skills repository.