resolving-secrets

Wrap shell commands to resolve secret references in environment variables.

Updated Jan 16, 2026
One-click install
npx skills add https://github.com/jeninh/ampskills-dotfile --skill resolving-secrets
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: resolving-secrets
Source: https://github.com/jeninh/ampskills-dotfile/tree/main/.agents/skills/resolving-secrets
Command: npx skills add https://github.com/jeninh/ampskills-dotfile --skill resolving-secrets

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill wraps shell commands to resolve secret references that are stored in environment variables, replacing placeholders with actual credentials at runtime to streamline secure automation.

Core Features & Use Cases

  • Resolve credentials for CLI tools such as synu, crush, gh, hut, and similar commands to avoid manual prompts.
  • On-demand secret substitution ensures automated scripts run without interactive prompts.
  • Compatible with the Fish shell and the opx Fish function to wrap commands reliably across environments.

Quick Start

Wrap a credential-sensitive command using the resolver and run it to verify that environment variables are substituted at execution time. Example: fish -c "opx gh issue view 123"

Frequently Asked Questions about resolving-secrets

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

FAQPage Schema
How do I resolve secrets in environment variables for CLI tools?

To resolve secrets in environment variables, you can wrap shell commands so placeholders are replaced with actual credentials at runtime. This streamlines secure automation by injecting credentials on demand during execution.

Why does my gh or hut command prompt for credentials in automated scripts?

Commands prompt for credentials when environment variables contain unresolved secret references. Wrapping the invocation to resolve credentials at runtime ensures automated scripts run without interactive prompts interrupting execution.

Do I need fish shell to resolve env vars for secure command invocation?

Yes, resolving secrets for secure command invocation requires the fish shell and the opx fish function. These dependencies integrate with standard credential workflows to reliably wrap and execute commands.

How do I run credential-sensitive commands using opx in fish shell?

To run credential-sensitive commands using opx in fish shell, wrap the target command with the resolver. For example, execute `fish -c "opx gh issue view 123"` to substitute environment variables at execution time.

What is the best way to manage CLI credentials for automated scripts?

The best way to manage CLI credentials for automated scripts is on-demand secret substitution. By wrapping commands to resolve references at runtime, you avoid manual prompts and ensure reliable execution across environments.