agentuity-cli-cloud-env-import

Import environment variables from a file to cloud and local .env.production. Requires authentication. Use for Agentuity cloud platform operations

⭐3stars🔀5forks📁View on GitHub🕐Updated Jan 5, 2026

When & Why to Use This Skill

This Claude skill automates the management of environment variables by importing them from local files directly to the Agentuity cloud platform and local production environments. It streamlines the DevOps workflow by ensuring configuration consistency across cloud and local setups, reducing manual entry errors, and maintaining secure authentication protocols for cloud platform operations.

Use Cases

  • Production Deployment: Synchronizing local environment configurations with the Agentuity cloud platform during the final stages of a release cycle.
  • Environment Migration: Bulk importing variables from legacy .env files to a new Agentuity project to accelerate infrastructure setup.
  • Configuration Auditing: Ensuring that the local .env.production file perfectly matches the cloud-side environment variables to prevent configuration drift and deployment failures.
  • Secure Onboarding: Allowing developers to securely push project-specific secrets to the cloud platform using authenticated CLI commands within the Claude agent environment.
nameagentuity-cli-cloud-env-import
descriptionImport environment variables from a file to cloud and local .env.production. Requires authentication. Use for Agentuity cloud platform operations
version"0.0.104"
licenseApache-2.0
allowed-tools"Bash(agentuity:*)"
argument-hint"<file>"
command"agentuity cloud env import"
tags"mutating creates-resource slow api-intensive requires-auth requires-project"

Cloud Env Import

Import environment variables from a file to cloud and local .env.production

Prerequisites

  • Authenticated with agentuity auth login
  • Project context required (run from project directory or use --project-id)

Usage

agentuity cloud env import <file>

Arguments

Argument Type Required Description
<file> string Yes -

Examples

Import environment variables from .env file:

bunx @agentuity/cli cloud env import .env

Import from .env.local file:

bunx @agentuity/cli cloud env import .env.local

Output

Returns JSON object:

{
  "success": "boolean",
  "imported": "number",
  "skipped": "number",
  "path": "string",
  "file": "string"
}
Field Type Description
success boolean Whether import succeeded
imported number Number of items imported
skipped number Number of items skipped
path string Local file path where variables were saved
file string Source file path