get-env-var

Retrieve Infisical environment variables and inject them into the shell.

3.2k|690|Updated Aug 25, 2025
One-click install
npx skills add https://github.com/Devin-AXIS/iPolloWork --skill get-env-var
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: get-env-var
Source: https://github.com/Devin-AXIS/iPolloWork/tree/main/.opencode/skills/get-env-var
Command: npx skills add https://github.com/Devin-AXIS/iPolloWork --skill get-env-var

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps users retrieve secrets, such as tokens or API keys, from their Infisical workspace and inject them into the current shell environment, ensuring that subsequent commands can access them seamlessly.

Core Features & Use Cases

  • Secret Management: Fetch and use secrets from Infisical without manual lookup or copying.
  • Environment Setup: Quick access to critical secrets needed for operations like API calls or service access.
  • Use Case: Before making an API call, use this Skill to securely inject the API key into the shell environment, simplifying the process of executing commands that require authentication.

Quick Start

Run the command from the repository root: export NAME=$(infisical secrets get NAME --plain --silent)

Frequently Asked Questions about get-env-var

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

FAQPage Schema
How do I inject environment variables from Infisical into a shell session?

Inject environment variables from Infisical into a shell session by using the command `export NAME=$(infisical secrets get NAME --plain --silent)` from your repository root. This securely retrieves secrets and makes them immediately available to subsequent commands or scripts.

What is the best way to fetch API keys for CI/CD pipelines without manual copying?

Fetching API keys for CI/CD pipelines without manual copying is best handled by retrieving secrets directly from an Infisical workspace and injecting them into the shell environment. This ensures sensitive tokens are managed securely and accessed seamlessly by deployment workflows.

Can I use Infisical for secret management in development workflows?

Yes, you can use Infisical for secret management in development workflows. It securely retrieves tokens or API keys from a team workspace and injects them into the shell environment, allowing developers to execute commands requiring authentication without manual lookup.

Does secure deployment with Infisical require any additional dependencies?

Secure deployment with Infisical does not require additional dependencies for this Skill. It operates using scripts to fetch and inject secrets directly into the shell environment, streamlining the setup process for CI/CD pipelines and development workflows.

Why are my environment variables not working after fetching them from a secret manager?

If environment variables are not working after fetching them from a secret manager, ensure the export command is formatted correctly as `export NAME=$(infisical secrets get NAME --plain --silent)`. This command must run from the repository root to properly inject the values into the active shell.