secrets

Initialize Infisical and generate .env files for backend and frontend environments.

Updated Dec 14, 2025
One-click install
npx skills add https://github.com/toobutta/maptelli --skill secrets-toobutta
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: secrets
Source: https://github.com/toobutta/maptelli/tree/main/.claude/skills/secrets
Command: npx skills add https://github.com/toobutta/maptelli --skill secrets-toobutta

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Infisical secrets management for Maptelli — initialize project, export env files, harden backend config, create .env.example, and add GitHub Actions CI/CD integration.

Core Features & Use Cases

  • Initialize Infisical for the Maptelli project, generate environment files for local development, harden backend config against insecure defaults, create a .env.example template, and wire up GitHub Actions for CI/CD secret injection.
  • Generate backend/.env and frontend/.env.local files from Infisical, and optionally inject secrets at runtime with Infisical Run.

Quick Start

Initialize Infisical for the Maptelli project and generate local .env files for backend and frontend.

Frequently Asked Questions about secrets

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

FAQPage Schema
How do I generate .env files for backend and frontend using Infisical?

You can generate backend/.env and frontend/.env.local files from Infisical by initializing the project and exporting environment variables to securely configure local development without manual entry.

How do I inject Infisical secrets into GitHub Actions CI/CD workflows?

Injecting Infisical secrets into GitHub Actions CI/CD involves wiring up the integration to automatically pull and inject secure configuration variables during pipeline execution for backend and frontend environments.

What is the best way to harden backend config against insecure defaults?

Harden backend config by applying Infisical secrets management to replace insecure defaults with securely injected environment variables, ensuring configuration hardening during project initialization and local development setup.

Do I need a .env.example template when managing secrets with Infisical?

Yes, creating a .env.example template is part of the Infisical secrets management workflow to document required environment variables for backend and frontend without exposing actual secret values.

Can I inject Infisical secrets at runtime instead of generating static .env files?

Yes, you can optionally inject secrets at runtime using Infisical Run instead of generating static backend/.env and frontend/.env.local files, providing flexible secure configuration for local development.