Agent skill

Secrets Management

by aiming-lab in aiming-lab/MetaClaw

A skill your agent uses when handling API keys, passwords, tokens, private keys, or any sensitive credential.

MITAuto-check: notesDevOps & Cloud

Install Secrets Management

skills CLI
$ npx skills add aiming-lab/MetaClaw --skill secrets-management -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install aiming-lab/MetaClaw secrets-management --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/aiming-lab/MetaClaw.git skills-src && mkdir -p .claude/skills && cp -r skills-src/memory_data/skills/secrets-management .claude/skills/secrets-management && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
secrets-management
GitHub stars
3.5k
Token cost
~246 tokens
SKILL.md length
91 words
Files
1
Skills in repo
36
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when handling API keys, passwords, tokens, private keys, or any sensitive credential.

  • Works in 5 steps: Never hardcode secrets in source files,… → Use environment variables for local… → Use a secrets manager (AWS Secrets… → …
  • Handling API keys
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Any sensitive credential

What it does

Secrets Management is an agent skill from aiming-lab/MetaClaw. Use this skill when handling API keys, passwords, tokens, private keys, or any sensitive credential. Never hardcode secrets in source code — apply this whenever the word "key", "token", "password", or "secret" appears in the task.

Its SKILL.md is about 250 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in DevOps & Cloud, covering Secrets management. The repository describes itself as: 🦞 Just talk to your agent — it learns and EVOLVES 🧬. The licence is MIT.

When your agent uses it

  • Handling API keys
  • Any sensitive credential

Example prompts

  • “password”
  • “secret”
  • “/secrets-management”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Never hardcode secrets in source files, configs committed to git, or logs.
  2. Use environment variables for local development (python-dotenv).
  3. Use a secrets manager (AWS Secrets Manager, HashiCorp Vault, 1Password CLI) in production.
  4. Add .env and *.pem to .gitignore before the first commit.
  5. Rotate secrets immediately if they are exposed (leaked in a commit, log, or error message).

What it can do on your machine

Read from SKILL.md and the folder at commit 922caf3. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Secrets Management loads about 246 tokens when it runs. Until then it costs about 62 tokens; SKILL.md has 91 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~62
When it runs · the whole SKILL.md, loaded when a task matches
~246

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NoteMentions a .env fileSKILL.md:13
    4. Add `.env` and `*.pem` to `.gitignore` before the first commit.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from aiming-lab/MetaClaw at commit 922caf3, republished under its MIT licence (© aiming-lab). 91 words, ~246 tokens.

Download SKILL.mdSave it as .claude/skills/secrets-management/SKILL.md (or your agent's skills folder).
name
secrets-management
description
Use this skill when handling API keys, passwords, tokens, private keys, or any sensitive credential. Never hardcode secrets in source code — apply this whenever the word "key", "token", "password", or "secret" appears in the task.
category
security

Secrets Management

Rules:

  1. Never hardcode secrets in source files, configs committed to git, or logs.
  2. Use environment variables for local development (python-dotenv).
  3. Use a secrets manager (AWS Secrets Manager, HashiCorp Vault, 1Password CLI) in production.
  4. Add .env and *.pem to .gitignore before the first commit.
  5. Rotate secrets immediately if they are exposed (leaked in a commit, log, or error message).

Scanning: Use ggshield, truffleHog, or git-secrets in CI to block secret commits.

Anti-patterns:

  • os.environ.get('KEY', 'hardcoded_default') in production code.
  • Logging full request/response bodies that may contain tokens.

© aiming-lab, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in memory_data/skills/secrets-management of aiming-lab/MetaClaw.

Open the folder on GitHubat commit 922caf3

Compare with similar skills

Secrets Management next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Secrets Management compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Secrets Management this skillaiming-lab/MetaClaw3.5k—~246Automated safety check: NotesMIT
Iron Proxy Gateway for NanoClawnanocoai/nanoclaw31k—~4.6kAutomated safety check: NotesMIT
LangBot Deployment Guidelangbot-app/LangBot18k—~1.2kAutomated safety check: NotesApache-2.0
Env Var Conventionssgl-project/sglang37k2 repos~2.9kAutomated safety check: PassApache-2.0
Mac Fleet Maintenancesteipete/agent-scripts7.3k—~4.8kAutomated safety check: PassMIT
Add Config Env Varbaserow/baserow6.1k—~1.1kAutomated safety check: PassCustom licence

Similar skills

  • Installs or refreshes Iron Proxy and its Iron Control web console for NanoClaw, with a local Docker setup, database, credentials and a human approval bridge.

    31k GitHub stars~4.6k tokensUpdated 2 days ago
    DevOps & CloudAuto-check: notes
  • LangBot Deployment Guide

    langbot-app/LangBot

    Deploys and configures a LangBot instance with Docker Compose or Kubernetes, covering config.yaml, the Box sandbox runtime, the plugin runtime and the global API key.

    18k GitHub stars~1.2k tokensUpdated today
    DevOps & CloudAuto-check: notes
  • Env Var Conventions

    sgl-project/sglang

    Conventions for SGLang environment variables — where to define, how to access, how to name, and how to deprecate.

    37k GitHub starsUsed in 2 repos~2.9k tokens
    DevOps & CloudAuto-check passed
  • Mac Fleet Maintenance

    steipete/agent-scripts

    Inventories and maintains a fleet of Macs from a desired-state file: package updates, repo and Xcode sync, and disk, backup and security health reports.

    7.3k GitHub stars~4.8k tokensUpdated 3 days ago
    DevOps & CloudAuto-check passed
  • Add Config Env Var

    baserow/baserow

    Add a Baserow configuration environment variable for the backend, frontend, or both, and propagate it through settings, Nuxt runtime config, Docker Compose, documentation, consumers, and tests as…

    6.1k GitHub stars~1.1k tokensUpdated today
    DevOps & CloudAuto-check passed
  • Edgeone Makers CLI

    TencentEdgeOne/edgeone-makers-tools

    EdgeOne Makers CLI command reference. An agent skill from TencentEdgeOne/edgeone-makers-tools.

    1.9k GitHub starsUsed in 1 repo~739 tokens
    DevOps & CloudAuto-check: notes

More from aiming-lab/MetaClaw

All 36 skills in this repo
  • Data Validation First

    aiming-lab/MetaClaw

    Use this skill before any data analysis, transformation, or modeling.

    3.5k GitHub stars~230 tokensUpdated 4 mo ago
    Auto-check passed
  • A skill your agent uses when implementing any endpoint, form handler, CLI tool, or function that accepts external input.

    3.5k GitHub stars~251 tokensUpdated 4 mo ago
    Auto-check passed
  • A skill your agent uses when writing shell scripts, Python automation, or any unattended batch job.

    3.5k GitHub stars~225 tokensUpdated 4 mo ago
    Auto-check passed
  • A skill your agent uses when building production services, pipelines, or automation that needs to be debugged, monitored, or audited.

    3.5k GitHub stars~247 tokensUpdated 4 mo ago
    Auto-check passed
  • Agent Task Handoff

    aiming-lab/MetaClaw

    A skill your agent uses when delegating a subtask to a sub-agent, spawning a parallel worker, or handing off work across sessions.

    3.5k GitHub stars~258 tokensUpdated 4 mo ago
    Auto-check passed
  • A skill your agent uses when writing messages in async channels (Slack, GitHub issues, email threads) where the reader may not have context and cannot ask follow-up questions immediately.

    3.5k GitHub stars~224 tokensUpdated 4 mo ago
    Auto-check passed

Categories

Questions about Secrets Management

What does Secrets Management do?

A skill your agent uses when handling API keys, passwords, tokens, private keys, or any sensitive credential. Secrets Management is an agent skill from aiming-lab/MetaClaw. Use this skill when handling API keys, passwords, tokens, private keys, or any sensitive credential.

When should I use Secrets Management?

Secrets Management fits situations like: handling API keys; any sensitive credential.

How do I install Secrets Management in Claude Code?

Run `npx skills add aiming-lab/MetaClaw --skill secrets-management -a claude-code`. Or copy the skill folder (memory_data/skills/secrets-management in aiming-lab/MetaClaw) into .claude/skills/secrets-management in your project. Claude Code loads it when a task matches its description.

How do I install Secrets Management in Codex?

Run `npx skills add aiming-lab/MetaClaw --skill secrets-management -a codex`. Or copy the skill folder (memory_data/skills/secrets-management in aiming-lab/MetaClaw) into .agents/skills/secrets-management in your project. Codex loads it when a task matches its description.

Can I use Secrets Management in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add aiming-lab/MetaClaw --skill secrets-management -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/secrets-management, .gemini/skills/secrets-management, .github/skills/secrets-management and .opencode/skills/secrets-management in your project.

What does Secrets Management need to run?

SKILL.md names no scripts, command-line tools or credentials: Secrets Management is instructions for the agent only.

Does Secrets Management access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Secrets Management safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Secrets Management use?

Secrets Management is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Secrets Management use?

About 246 tokens (SKILL.md is roughly 984 characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Secrets Management?

Skills that share tags, products or a category with Secrets Management: Iron Proxy Gateway for NanoClaw (nanocoai/nanoclaw, 31k stars), LangBot Deployment Guide (langbot-app/LangBot, 18k stars), Env Var Conventions (sgl-project/sglang, 37k stars) and Mac Fleet Maintenance (steipete/agent-scripts, 7.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Secrets Management?

aiming-lab (a GitHub organization) maintains it in aiming-lab/MetaClaw, which has 3,458 GitHub stars. The repository holds 36 skills in this directory. The repository was last updated on June 7, 2026.

Source: aiming-lab/MetaClaw on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.