Secrets Management

Reviewed 2026-10-14securityPrompt / Rule# secrets # ci-cd # vault # github-actions # rotation

Community skill with a short procedure for handling CI/CD secrets safely: Vault, cloud secret managers, GitHub Actions, workload identity and rotation.

Security Reviewed

Three Markdown files with no scripts or network access; the rules tell the agent not to print secret values.

Install Secrets Management in Google Antigravity

Antigravity loads skills from .agents/skills/ in your project or ~/.gemini/config/skills/ for all projects (official docs). Full guide

EasiestOption 1: paste this to your Antigravity agent

Install the "Secrets Management" skill for Google Antigravity.
Follow the steps at https://www.antigravityskills.org/install/secrets-management.md (source: https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/secrets-management).
Before running anything, show me what you will download and whether it includes scripts, and wait for my OK.
Install it into this project (.agents/skills/) unless I say global. When done, check that Antigravity lists it as an installed skill.

The agent reads the install file, shows you what it will download and waits for your OK.

Option 2: install it yourself

1. Download the repository
```
git clone --depth 1 https://github.com/sickn33/antigravity-awesome-skills.git /tmp/ag-skills && git -C /tmp/ag-skills log -1 --format=%h
```
We reviewed commit a307264. If the second command prints a different hash, the skill may have changed since our review.
2. Copy the skill into this project (workspace skill)
```
mkdir -p .agents/skills && cp -r /tmp/ag-skills/skills/secrets-management .agents/skills/
```
Run from your project root. Antigravity reads workspace skills from .agents/skills/<folder>/; this folder holds SKILL.md and references/ (2 Markdown files, no scripts).
3. Or install it for all projects (global skill)
```
mkdir -p ~/.gemini/config/skills && cp -r /tmp/ag-skills/skills/secrets-management ~/.gemini/config/skills/
```
Use this instead of the previous step. Copy only the skills you need: the repo README warns that a large watched skills folder can overload Antigravity's context.
4. Check that Antigravity sees it
Antigravity app: start a new conversation and ask "What skills do you have?"; secrets-management should be listed. Antigravity CLI: run /skills (/skills reload in a session that was already open).

The repository's own installer (npx agentic-awesome-skills --antigravity --skills <ids> --dry-run, README) can also install selected skills; the copy steps above use the standard Antigravity skill folders and install only this one.

Using Claude Code, Cursor or Codex? See other assistants below.

What is Secrets Management?

secrets-management is a small community-contributed skill in sickn33's antigravity-awesome-skills collection. It tells the agent how to design or repair secret retrieval for an authorised system: pick the existing backend (Vault, a cloud secret manager or the host's store), prefer short-lived workload identity, keep pull-request jobs apart from privileged jobs, rotate in four steps, and check logs for leaks using synthetic secret markers. It is instructions only, with two short reference checklists.

How to use Secrets Management?

Install the skill, then ask for help with a concrete secrets task, for example moving a CI database password into Vault or auditing a GitHub Actions workflow. The agent identifies secret names, owners and consumers without printing values, then follows the six-step procedure and the verification list.

Key features of Secrets Management

✓We counted at a307264: the folder has 3 files, SKILL.md (47 lines, 2,836 bytes) and two references, vault-setup.md (13 lines) and github-secrets.md (13 lines); there are no scripts
✓We counted: the procedure has 6 steps and the verification list has 5 checks, including that a different workload or environment is denied and that logs contain no secret markers even on failure
✓SKILL.md says rotation must go through prepare, consumer switch, verification and old-credential revocation, and that a failed rotation must not leave the database and secret store on different credentials
✓SKILL.md says masking cannot make logging secrets safe and that deleting a log entry does not count as revoking an exposed credential
✓The two sources it cites are GitHub's secure-use guidance for Actions and HashiCorp's Vault production hardening page; we did not open them, so check those pages for specifics
✓Difference from a tool: it never touches a secret store itself and tells the agent to inspect configuration without displaying values, so it works as a checklist for the agent, not as an integration

When to use Secrets Management

1Auditing a GitHub Actions workflow for secrets in shell source or logs
2Planning a secret rotation with a rollback path
3Checking that a pull-request job cannot reach privileged credentials

Source and files

Repository: sickn33/antigravity-awesome-skills (MIT)
Upstream risk label: critical
Added upstream: 2026-02-27
SKILL.md size: 2.8 KB
Files in the skill folder: SKILL.md · references
Listing synced: 2026-10-05 from commit bdacd76

Installation & Setup Guide

Agent Rules / Prompt Setup

Follow these steps (taken from the project's own docs) to configure Secrets Management in your development environment.

Step 1: Claude Code (manual copy)claude

mkdir -p .claude/skills && cp -r /tmp/ag-skills/skills/secrets-management .claude/skills/

Not documented per skill by the repository; this uses Claude Code's standard .claude/skills/ folder after the clone above.

Step 2: Cursor: not documented by the projectcursor

The README lists installer targets for several hosts, but gives no per-skill Cursor path, so we do not list one.

Usage Example & Verification

Prompt / Request Example

1) SKILL.md example: "A deployment needs a database credential. The trusted job retrieves it through the configured identity and passes it only to the migration process." The skill then asks you to test missing access and an expired identity in staging.

2) Our example: "Review .github/workflows/deploy.yml with the secrets-management skill. Do any steps interpolate secrets into shell commands or run on pull requests from forks?"
-> The agent reads the workflow, reports each secret's consumer and scope, and suggests passing values through environment variables of the consuming step instead of expressions.

3) Our example: "Write a rotation plan for our Postgres password stored in Vault, with a rollback step."
-> The agent lays out prepare, switch consumers, verify, revoke old, and what to do if verification fails.

Security Review

Static review

Reviewed Date

2026-10-14

Audited Ref / Commit

a3072641b750a1fb2f6ce695a5f984ea3d4c3ec1

Reviewer

antigravityskills.org (static code review)

Three Markdown files with no scripts or network access; the rules tell the agent not to print secret values.

Full review: scope, findings, risks

Audit Scope:skills/secrets-management/SKILL.md, references/vault-setup.md and references/github-secrets.md read in full (3 files, no scripts); repository README install and disclaimer sections and LICENSE, at commit a307264 (2026-10-14). Static review only.

Key Findings:Instruction-only skill, three Markdown files, no scripts. No network calls, no environment variables, no API keys. It tells the agent to inspect configuration without displaying values, keep pull-request validation separate from privileged jobs, and not to alter real credentials or deploy secret infrastructure without authorisation.

Identified Operational Risks & Permissions:Low from the skill itself. Medium in use: the agent will be reading CI configuration and policy files that sit next to real secrets.

The folder contains SKILL.md and two reference files, all Markdown, with no scripts. There are no commands to run, no URLs fetched by the skill (two documentation links are listed as sources) and no credentials. The procedure repeatedly says to keep values out of output, logs and generated shell source, to test with synthetic secret markers and to get authorisation before changing real credentials. This is a static read of the files; we did not run the skill.

Operational Notes & Known Limitations

Known Limitations

•Instructions only: it does not connect to Vault, AWS or GitHub and cannot change a secret itself
•The reference files are 13 lines each, so they point you to the vendors' documentation rather than replacing it
•SKILL.md says not to alter real credentials or deploy secret infrastructure without authorisation
•Frontmatter marks it risk: critical, because an agent following it may read CI configuration that sits next to real secrets

Frequently Asked Questions

Is the Secrets Management skill safe?

It is three Markdown files with no scripts, no network calls and no credentials in them. Its own rules tell the agent to inspect configuration without displaying secret values and to supply secrets to the consuming process rather than printing them. The risk is context: an agent working in your CI config can see what is in it.

How do I install Secrets Management in Antigravity?

Clone sickn33/antigravity-awesome-skills, copy skills/secrets-management into .agents/skills/ (or ~/.gemini/config/skills/), then ask "What skills do you have?" (Antigravity CLI: /skills).

Does it install or configure Vault?

No. It gives a checklist for Vault access and rotation and tells the agent not to use a development-mode root token for deployment.

Which secret managers does it cover?

It names Vault, AWS Secrets Manager and GitHub Actions secrets; the detailed reference files cover Vault and GitHub only.

Is it an official HashiCorp or GitHub skill?

No. It is community-contributed to an independent collection and links to their documentation as sources.

Supported Platforms

antigravityclaude

View Source on GitHub

Keep exploring this topic

Browse the full Antigravity skills directory for more source-linked skills with install steps and static safety reviews.

More security skills #secrets #ci-cd #vault #github-actions Use cases

Related Skills

🛡️

Vulnerability Scanner

@sickn33

Community skill that teaches an agent to analyse a project for vulnerabilities (OWASP Top 10:2025, supply chain, attack surface, risk ranking) and ships a Python script that scans a folder.

Static review

securityowasp

🛡️

Container Security (Snyk)

@snyk

Snyk's container-security skill: scan Docker images for OS and app vulnerabilities via the Snyk MCP server and fix Dockerfiles.

Static reviewinstructions onlyneeds API keynetwork accesswrites files

container-securitydocker

🛡️

Metasploit Framework

@sickn33

Community skill that gives an agent a command reference for the Metasploit penetration-testing framework. It is an offensive-security skill: the upstream file is marked risk: offensive and meant for authorised assessments and lab use only.

Static reviewinstructions onlyoffensive tooloffline

securitymetasploit