Helps the user configure the Google SecOps Remote MCP Server for Antigravity. Use this when the user asks to "set up" or "configure" the security tools for Antigravity.
Install with Tessl CLI
npx tessl i github:google/mcp-security --skill secops-setup-antigravity72
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
Setup automation script
.env file read
100%
100%
Template file read
100%
100%
gcloud auth print-access-token
100%
100%
Temporary token warning
0%
100%
project_id placeholder replaced
100%
100%
server_url placeholder replaced
100%
100%
auth_token placeholder replaced
100%
100%
Existing config read
60%
100%
Config merge (not overwrite)
100%
100%
Correct output path
0%
100%
gcloud auth prerequisite check
0%
100%
Without context: $0.5042 · 2m 13s · 18 turns · 71 in / 9,307 out tokens
With context: $0.5154 · 1m 59s · 21 turns · 1,022 in / 7,778 out tokens
Config merge correctness
PROJECT_ID from .env
100%
100%
SERVER_URL from .env
100%
100%
gcloud auth command used
100%
100%
auth_token placeholder replaced
100%
100%
project_id placeholder replaced
100%
100%
server_url placeholder replaced
100%
100%
Existing server preserved
100%
100%
SecOps servers present
100%
100%
Correct output path
20%
100%
Valid JSON structure
100%
100%
Without context: $0.2474 · 1m 10s · 11 turns · 16 in / 5,155 out tokens
With context: $0.7307 · 2m 47s · 32 turns · 288 in / 10,421 out tokens
Onboarding documentation
gcloud auth login step
100%
100%
quota project step
0%
100%
PROJECT_ID required
25%
100%
CUSTOMER_ID required
100%
100%
REGION required
100%
100%
.env file recommended
0%
100%
Temporary token warning
0%
100%
Correct config file path
0%
100%
Merge instruction
0%
100%
Verification: list 3 soar cases
0%
100%
Without context: $0.2639 · 1m 33s · 13 turns · 18 in / 4,836 out tokens
With context: $0.4247 · 1m 42s · 22 turns · 185 in / 5,650 out tokens
Table of Contents
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.