env-storage-user-skill

Pi user-level skill for loading the user's master .env + .env.production secrets into a project (or saving a project's env files back into the masters). Installed once per machine; the skill + user-data live at ~/.pi/agent/skills/env-storage/.

Packages

Package details

skill

Install env-storage-user-skill from npm and Pi will load the resources declared by the package manifest.

$ pi install npm:env-storage-user-skill
Package
env-storage-user-skill
Version
0.1.0
Published
Aug 25, 2026
Downloads
140/mo · 140/wk
Author
taro81
License
MIT
Types
skill
Size
19.2 KB
Dependencies
0 dependencies · 0 peers
Pi manifest JSON
{
  "skills": [
    "./skills"
  ]
}

Security note

Pi packages can execute code and influence agent behavior. Review the source before installing third-party packages.

README

env-storage-user-skill

A Pi user-level skill for loading the user's master .env + .env.production secrets into a project (or saving a project's env files back into the masters). The skill lives at ~/.pi/agent/skills/env-storage/ once installed and is accessible globally across every project — pi update of any other package can never overwrite it.

The masters are real secret values for the user (Modal token id + secret, Trigger.dev dev + prod keys, etc.) and live in the same folder. This skill never reads env file contents into the model context — it copies bytes disk-to-disk via the shell and reports only metadata (existence, line counts, redacted key names).

Install

Once per machine (global, not project-local):

pi install npm:env-storage-user-skill@latest

The skill files are dropped into ~/.pi/agent/skills/env-storage/ (skill content in SKILL.md + assets/; user-data masters in .env + .env.production). Pi's skill auto-discovery picks it up globally — you can /skill:env-storage (Load) from any project after install.

Usage

From any project root:

/skill:env-storage

You'll be asked which operation:

  • Load — copy ~/.pi/agent/skills/env-storage/.env<cwd>/.env, and .env.production<cwd>/.env.production.
  • Update — copy <cwd>/.env~/.pi/agent/skills/env-storage/.env, and <cwd>/.env.production~/.pi/agent/skills/env-storage/.env.production.

Both copy verbatim. Existing destinations require confirmation.

Typical setup flow before invoking relay-system-setup:

  1. Run /skill:env-storage (Load) on a fresh project — populates .env + .env.production with the user's secrets.
  2. Run /skill:relay-system-setup (from the relay-code-pi package) to scaffold the project. The setup skill validates that Modal keys are present in .env (line-prefix count only — never reads values).

Where the data lives

Path Role
~/.pi/agent/skills/env-storage/SKILL.md Skill instructions (this package).
~/.pi/agent/skills/env-storage/assets/.env Dev seed template (placeholder keys, shipped with the package).
~/.pi/agent/skills/env-storage/assets/.env.production Prod seed template (placeholder keys, shipped with the package).
~/.pi/agent/skills/env-storage/.env User data — real dev values.
~/.pi/agent/skills/env-storage/.env.production User data — real prod values.
<cwd>/.env The project's dev .env — Load/Update target.
<cwd>/.env.production The project's prod .env.production — Load/Update target.

pi update / re-install of this package never touches the user-data .env + .env.production — Pi's package install only manages the skill files (SKILL.md, assets/).

Safety

This skill copies bytes disk-to-disk. Secret values never enter the model context. Never cat/type/Read any env file in this skill's flow — only wc -l and grep -cE '^KEY=' file for counts and redacted key names.

License

MIT