secops-setup-antigravity
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
Discovery
75%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 has good completeness with explicit 'Use when' triggers and is highly distinctive due to the specific product focus. However, it lacks concrete action details (what configuration steps are involved) and could benefit from additional trigger term variations to catch more user phrasings.
Suggestions
Add specific concrete actions like 'set up authentication, configure API endpoints, establish connections' to improve specificity
Expand trigger terms to include variations like 'install', 'connect', 'SecOps setup', 'MCP server', or 'Google security integration'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Google SecOps Remote MCP Server for Antigravity) and implies configuration actions, but doesn't list specific concrete actions like 'create API keys', 'set authentication', or 'configure endpoints'. | 2 / 3 |
Completeness | Clearly answers both what (configure Google SecOps Remote MCP Server for Antigravity) and when (when user asks to 'set up' or 'configure' security tools for Antigravity) with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes some natural keywords ('set up', 'configure', 'security tools', 'Antigravity') but missing common variations like 'install', 'connect', 'SecOps setup', 'MCP configuration', or 'Google security'. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting Google SecOps Remote MCP Server for Antigravity specifically - unlikely to conflict with other skills due to the unique product/tool combination. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
57%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 structure for guiding SecOps configuration but lacks the concrete, executable details needed for reliable execution. The reliance on external templates without showing their structure, combined with missing validation steps for JSON manipulation, creates ambiguity. The role-play preamble wastes tokens.
Suggestions
Remove the 'You are an expert...' preamble - it adds no value and wastes tokens
Show the expected structure of mcp_config.template.json inline or provide a concrete example of the final merged output
Add explicit validation steps: verify JSON is valid after merge, confirm file was written successfully, check that existing servers weren't overwritten
Replace 'Warn the user that this token is temporary' with the actual warning text to display
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient but includes some unnecessary framing ('You are an expert...') and could tighten the prerequisite section. The role-play preamble adds no value for Claude. | 2 / 3 |
Actionability | Provides concrete bash commands for gcloud auth, but the core configuration steps rely on reading external template files and use placeholder syntax without showing the actual template structure or expected output format. | 2 / 3 |
Workflow Clarity | Steps are sequenced but lack validation checkpoints. No explicit verification that the merge succeeded, no error handling for missing files or invalid JSON, and the 'Note: Warn the user' is vague rather than actionable. | 2 / 3 |
Progressive Disclosure | Appropriately structured for its scope. References external files (template, .env.example) at one level deep with clear signaling. Content is well-organized into logical sections without being monolithic. | 3 / 3 |
Total | 9 / 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.