skills.rest
abzhaw
abzhawCOMMUNITY
Explore all skills by this author →
GitHub

secrets-management

Enforce secret handling policies across Julia environments, CI pipelines, and runtime services.

Updated Feb 21, 2026
Search Tags:#security#secrets#credentials#best-practices#env#gitignore#rotation
One-click install
npx skills add https://github.com/abzhaw/juliaz_agents --skill secrets-management-abzhaw
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: secrets-management
Source: https://github.com/abzhaw/juliaz_agents/tree/main/.agent/skills/secrets-management
Command: npx skills add https://github.com/abzhaw/juliaz_agents --skill secrets-management-abzhaw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Secrets management is critical to prevent credential leakage, enforce rotation, and minimize blast radius across services.

Core Features & Use Cases

  • Never commit secrets — enforce .gitignore and secret-scan practices.
  • Rotate credentials regularly — implement scheduled rotation and automatic rotation workflows.
  • Least privilege — restrict keys to the minimal scope required by each service.
  • Validate at startup — fail fast if required keys are missing and redact sensitive values in logs.
  • Redact in logs — avoid exposing full keys in logs and monitoring.
  • Credential rotation schedule — maintain documented schedules for API keys, DB passwords, and tokens.
  • Secrets inventory — maintain an up-to-date inventory of credentials and their usage.

Quick Start

Add a .env.secrets file with your credentials and enable startup validation across services.

Frequently Asked Questions about secrets-management

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is the best way to schedule credential rotation for API keys and database passwords?▼

Secrets rotation involves implementing scheduled and automatic workflows to update API keys, DB passwords, and tokens regularly. You should maintain a documented rotation schedule and an up-to-date secrets inventory to minimize blast radius.

Why should I validate required keys at application startup?▼

Redacting sensitive environment variables requires enforcing policies that mask secret values before they reach monitoring tools. This prevents exposing full keys in logs while still allowing non-sensitive application diagnostic data to be recorded.

What happens if required secrets are missing during startup validation?▼

Enforcing least privilege requires restricting keys to the minimal scope required by each runtime service. This minimizes the blast radius by ensuring that a compromised credential only grants limited access to specific operational services.

What is the best way to manage a secrets inventory for multiple runtime services?▼

Startup validation fails fast if required keys are missing, halting the application before it can operate insecurely. This ensures that runtime services only boot when all necessary credentials are present and properly configured.

Related Skills

Explore More Software Engineering Skills→
abzhawabzhaw

environment-config

Manage environment variables and secret keys across development, staging, and production.

Community
Intermediate
onesmartguyonesmartguy
2

secrets-management

Manage sensitive credentials securely across CI/CD pipelines and secret stores.

Community
Advanced
AmidVoshakulAmidVoshakul

secrets-management

Integrate HashiCorp Vault and AWS Secrets Manager for CI/CD secret retrieval.

Community
Advanced
Clear-CapabilitiesClear-Capabilities
73

agentic-security:security-rotate-leak

Rotate leaked API keys and credentials end-to-end across supported providers.

Official
Advanced