set-secret

Write a secret value into a Pixie tool's .env without printing it.

6|1|Updated May 17, 2026
One-click install
npx skills add https://github.com/AlexKapadia/Pixie --skill set-secret
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: set-secret
Source: https://github.com/AlexKapadia/Pixie/tree/main/.claude/skills/set-secret
Command: npx skills add https://github.com/AlexKapadia/Pixie --skill set-secret

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writes a secret value into a Pixie tool's .env without exposing it in outputs or logs.

Core Features & Use Cases

  • One-tool-per-invocation workflow with strict validation.
  • Prevents secret leakage by not echoing values back to the user.
  • Updates or appends a single key in the tool's .env while preserving existing entries.

Quick Start

Provide the tool_id, key, and value, and I will securely write the secret into tools/<tool_id>/.env.

Frequently Asked Questions about set-secret

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

FAQPage Schema
How do I securely set secrets in a .env file without exposing the value in logs?

Securely setting secrets in a .env file involves writing the value directly to the file without echoing it back. This approach validates inputs, updates the key while preserving existing entries, and prevents secret leakage in outputs or logs.

What is the best way to append a single secret key to an existing .env file?

Appending a single secret key to an existing .env file requires a one-tool-per-invocation workflow that validates inputs and confirms the tool exists. It updates or appends the specific key while preserving all existing entries.

Does Pixie tool secrets management support validating declared secret keys in tool.json?

Pixie tool secrets management optionally checks tool.json for a declared secret key before writing. It requires a tool_id, key, and value, and confirms the target tool exists before securely updating the .env file.

How do I write environment variables to a specific tool's .env file using uv run?

Writing environment variables to a specific tool's .env file uses a Python one-liner invoked via uv run. You provide the tool_id, key, and value, and it updates the .env file located in the tools directory without exposing the secret.

Can I update multiple tool .env files at once during secrets management?

Updating multiple tool .env files at once is not supported; the system operates one tool at a time. This strict validation approach ensures secure secrets management by focusing on a single tool_id per invocation to prevent leakage.