amanpal3/Dr-SKILLs / .agent/skills/antigravity-agents
antigravity-agents
FlaggedA multi-agent orchestration skill for building, deploying, and coordinating specialized AI agents that work together like an elite squad. Use this skill whenever the user wants to: assign tasks to multiple AI agents, build an agentic pipeline or workflow, create a team of specialized agents (coding, UI/UX, security, database, planning, debugging, etc.), run autonomous multi-step operations, or orchestrate complex projects where different agents handle different roles. Trigger this skill aggressively — if the user mentions "agents", "squad", "team", "pipeline", "orchestrate", "automate workflow", "multi-step task", "assign tasks", or any mention of splitting a big project into specialized roles, this skill MUST be used.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 15.9 KB |
| references/agent-prompts.md | markdown | 7.9 KB |
| references/api-design-guide.md | markdown | 6.5 KB |
| references/code-standards.md | markdown | 5.4 KB |
| references/gtm-templates.md | markdown | 4.8 KB |
| references/security-checklist.md | markdown | 6.4 KB |
| scripts/init_project.sh | script | 4.6 KB |
| templates/ARCHITECTURE.md | markdown | 2.4 KB |
| templates/BRAND_GUIDE.md | markdown | 3.8 KB |
| templates/MISSION_LOG.md | markdown | 1.3 KB |
| templates/SPRINT_PLAN.md | markdown | 2.5 KB |
references/gtm-templates.md
View on GitHub# GTM Templates — Cap America's Launch Playbooks
> *"A plan is nothing. Planning is everything."*
---
## Template 1 — Full GTM Launch Plan
```markdown
# GTM Launch Plan: [Product/Feature Name]
Owner: [Name] | Launch Date: [Date] | Tier: [1 Major / 2 Feature / 3 Minor]
## North Star Metric
[Single number that defines launch success]
## Success Metrics
| Metric | 30 Days | 60 Days | 90 Days |
|---|---|---|---|
| Signups | | | |
| Activated Users | | | |
| Revenue / MQLs | | | |
## ICP for This Launch
- Title: [Job title]
- Company: [Size, industry, stage]
- Pain: [Use their exact words]
- Trigger: [What makes them ready to buy now]
## Positioning Statement
For [ICP] who [pain], [product] is a [category] that [benefit].
Unlike [competitor], we [differentiator].
## Channel Plan
| Channel | Tactic | Owner | KPI |
|---|---|---|---|
| Email | Announce to list | | 40% open rate |
| LinkedIn | Founder post | | 500 reach |
| Product Hunt | Launch post | | Top 10 |
| SEO | Launch blog post | | 200 organic visits |
## Pre-Launch Checklist
- [ ] Landing page live + mobile tested
- [ ] Analytics firing (GA4 events verified)
- [ ] Email sequence live and tested
- [ ] Support team briefed
- [ ] Social posts scheduled
- [ ] Sales team has battle cards
## Launch Day Runbook
| Time | Action | Owner |
|---|---|---|
| T-24h | Final QA + stakeholder brief | PM |
| T-0h | Go live | Eng |
| T+1h | All channels activated | Marketing |
| T+4h | First metrics check | PM |
| T+24h | Public metrics report | PM |
```
---
## Template 2 — ICP Profile
```markdown
# ICP Profile: [Segment Name]
## Firmographics
- Industry:
- Company Size:
- Revenue Range:
- Geography:
- Funding Stage:
## Buyer Persona
- Title:
- Reports To:
- Watering Holes: [LinkedIn groups, newsletters, Slack communities]
## Pain Points (Before Your Product)
1.
2.
3.
## Trigger Events (When They're Ready to Buy)
-
-
## Qualification (BANT)
- Budget: [Do they have budget?]
- Authority: [Can they sign?]
- Need: [Do they have the pain?]
- Timeline: [Solving this in 90 days?]
## Where to Find Them
- LinkedIn: [Title + company size + industry filters]
- Communities: [Specific groups]
- Events: [Conferences they attend]
```
---
## Template 3 — Positioning Doc
```markdown
# Positioning Doc: [Product Name]
Version: 1.0 | Date: [Date]
## Category
[What category does this product live in?]
## Target Customer
[Primary ICP — one paragraph]
## Value Proposition
[2–3 sentences: what it does, for whom, measurable outcome]
## Differentiation
| Competitor | Their Strength | Our Edge |
|---|---|---|
| | | |
## Proof Points
- [Customer quote with name, title, company]
- [Stat with source]
- [Case study outcome]
## Messaging Pillars
1. [Pillar]: [Supporting message]
2. [Pillar]: [Supporting message]
3. [Pillar]: [Supporting message]
## Tagline Options
-
-
```
---
## Template 4 — 5-Touch Outreach Sequence
```markdown
# Outreach Sequence: [Campaign Name]
ICP: [Persona] | Goal: [Book meeting / trial signup] | Length: 5 touches
## Touch 1 — Cold Email (Day 0)
Subject: [Specific to their company or role]
Format: AIDA — Attention → Interest → Desire → Action
CTA: [Book 20-min call / reply yes or no]
## Touch 2 — LinkedIn Connect (Day 2)
Message (300 char max): [Personalized observation + reason to connect]
## Touch 3 — Follow-Up Email (Day 5)
Subject: Re: [original]
Body: [Add new value — case study, insight, stat]
## Touch 4 — LinkedIn DM (Day 8)
Message: [Reference their content or company news]
## Touch 5 — Breakup Email (Day 12)
Subject: Re: [original]
Body: Low-pressure close. Leave door open. No hard sell.
```
---
## Template 5 — Competitor Battle Card
```markdown
# Battle Card: vs [Competitor]
## Their Pitch
[How they position to buyers]
## Their Weaknesses (from G2/reviews)
- [Weakness 1 — customer language]
- [Weakness 2]
## Common Objection: "We already use [Competitor]"
Response: "Most of our customers came from [Competitor]. The main thing they flagged was [weakness]. Has that been your experience?"
## Why We Win
| Their Weakness | Our Strength | Proof |
|---|---|---|
| | | |
```
---
## Template 6 — Investor Metrics Brief
```markdown
# Investor Brief: [Company Name]
Round: [Seed/A/B] | Ask: $[Amount]
## One-Liner
[What you do in one sentence]
## Problem
[Market pain — quantified]
## Solution
[Your product — outcome-focused, one sentence]
## Market Size
- TAM: $[X]B | SAM: $[X]M | SOM: $[X]M (3-year target)
## Traction
- [MRR / ARR / Users / Retention]
- [Key customer or category]
## Business Model
- Revenue: [How you make money]
- Unit Economics: CAC $[X] | LTV $[X] | LTV:CAC [X]x
## Use of Funds
| Area | Amount | Outcome |
|---|---|---|
| Engineering | $[X] | [What ships] |
| GTM | $[X] | [Revenue target] |
## The Ask
$[Amount] for [N] months to reach [Milestone].
```
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |