skills.rest
YSheldon
YSheldonCOMMUNITY
Explore all skills by this author →
GitHub

environment-secrets

View, set, delete, and request environment secrets across shared, development, and production environments.

Updated Apr 12, 2026
Search Tags:#security#configuration#environment#secrets#variables#env-vars#request
One-click install
npx skills add https://github.com/YSheldon/Prompt-Log --skill environment-secrets-ysheldon
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: environment-secrets
Source: https://github.com/YSheldon/Prompt-Log/tree/main/.local/skills/environment-secrets
Command: npx skills add https://github.com/YSheldon/Prompt-Log --skill environment-secrets-ysheldon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manage environment variables and secrets securely within your projects by enabling safe visibility, configuration, and retrieval without embedding sensitive data in code.

Core Features & Use Cases

  • View environment variables and secrets across environments (shared, development, production) to audit configurations.
  • Set non-sensitive environment variables and delete obsolete ones, while ensuring secrets are requested from users and never hardcoded.
  • Request missing secrets from users when needed to enable features like API access, database connections, or feature toggles.

Quick Start

Query your current configuration and request any missing secrets to enable your application.

Frequently Asked Questions about environment-secrets

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

FAQPage Schema
How do I manage environment variables and secrets across different deployment environments?▼

You can manage environment variables and secrets by viewing, setting, and deleting configurations across shared, development, and production environments to ensure proper scoping and safe deployment.

How do I securely request missing secrets from users without hardcoding them?▼

You can securely request missing secrets from users directly when needed to enable features like API access or database connections, ensuring sensitive data is never embedded in code.

Can I view and audit existing environment variables across shared, development, and production environments?▼

Yes, you can view environment variables and secrets across shared, development, and production environments to audit configurations and verify that application settings are correctly scoped.

What is the best way to delete obsolete environment variables during application configuration?▼

The best way to delete obsolete environment variables is to use the deletion operation to remove non-sensitive configurations, while ensuring any required secrets are safely requested from users rather than hardcoded.

Why should I enforce environment scoping when setting up application secrets?▼

Enforcing environment scoping prevents configuration leaks by isolating development, production, and shared variables, ensuring that secrets and environment variables are only accessible within their intended deployment context.

Related Skills

Explore More Software Engineering Skills→
AgustinMadygrafAgustinMadygraf

0a-project-bootstrap-audit

Audit new Python project bootstrap structure and write findings to docs/todo.md.

Community
Intermediate
sgcarstrendssgcarstrends
21

env-config

Manage environment variables and secrets across dev, staging, and prod with SST integration.

Official
Intermediate
smith-hornsmith-horn
75

varlock

Mask environment variables and validate secrets via the Varlock CLI.

Official
Advanced
duanbiao2000duanbiao2000
3

secrets-management

Centralize secrets management across Vault, AWS, Azure, and Google for CI/CD pipelines.

Community
Advanced