Import environment variables and secrets from a file to cloud and local .env. Requires authentication. Use for Agentuity cloud platform operations
Scanned 2/12/2026
Install via CLI
openskills install agentuity/docs---
name: agentuity-cli-cloud-env-import
description: Import environment variables and secrets from a file to cloud and local .env. Requires authentication. Use for Agentuity cloud platform operations
version: "0.1.24"
license: Apache-2.0
allowed-tools: "Bash(agentuity:*)"
argument-hint: "<file>"
metadata:
command: "agentuity cloud env import"
tags: "mutating creates-resource slow api-intensive requires-auth"
---
# Cloud Env Import
Import environment variables and secrets from a file to cloud and local .env
## Prerequisites
- Authenticated with `agentuity auth login`
## Usage
```bash
agentuity cloud env import <file> [options]
```
## Arguments
| Argument | Type | Required | Description |
|----------|------|----------|-------------|
| `<file>` | string | Yes | - |
## Options
| Option | Type | Required | Default | Description |
|--------|------|----------|---------|-------------|
| `--org` | optionalString | Yes | - | import to organization level (use --org for default org) |
## Examples
Import variables from backup file:
```bash
bunx @agentuity/cli cloud env import .env.backup
```
Import from .env.local file:
```bash
bunx @agentuity/cli cloud env import .env.local
```
Import to organization level:
```bash
bunx @agentuity/cli cloud env import .env.shared --org
```
## Output
Returns JSON object:
```json
{
"success": "boolean",
"imported": "number",
"envCount": "number",
"secretCount": "number",
"skipped": "number",
"path": "string",
"file": "string",
"scope": "string"
}
```
| Field | Type | Description |
|-------|------|-------------|
| `success` | boolean | Whether import succeeded |
| `imported` | number | Number of items imported |
| `envCount` | number | Number of env vars imported |
| `secretCount` | number | Number of secrets imported |
| `skipped` | number | Number of items skipped |
| `path` | string | Local file path where variables were saved (project scope only) |
| `file` | string | Source file path |
| `scope` | string | The scope where variables were imported |
No comments yet. Be the first to comment!
Playbook for creating and editing uCoz landing pages via MCP tools (`templates_tool`, `ftp_tool`, `modules_tool`). Use for tasks such as: "build a landing page", "update the homepage as a landing page", "create a promo page on the homepage", "add a lead form / menu / SEO to the homepage". Homepage: `page_list`, `page_get`; first publish — `page_update` with full `page_tmpl`; HTML edits after generation — `patch_template` (module_id=2, template_id=1), not `update_template`. Activate the mail f...
Interact with the Paperclip control plane API to manage tasks, coordinate with other agents, and follow company governance. Use when you need to check assignments, update task status, delegate work, post comments, set up or manage routines (recurring scheduled tasks), or call any Paperclip API endpoint. Do NOT use for the actual domain work itself (writing code, research, etc.) — only for Paperclip coordination.
Digital Audio Workstation usage, music composition, interactive music systems, and game audio implementation for immersive soundscapes.
Instantly.ai cold email outreach API - manage campaigns, leads, accounts, and analytics. Use for cold email automation, lead management, campaign creation/monitoring, and email account warmup.
Run a single Terminal-Bench problem through Paperclip in a bounded, human-in-the-loop improvement cycle until the smoke passes, the board rejects the next fix, the iteration budget is exhausted, or a real blocker is named. Each iteration runs a bounded smoke against an isolated Paperclip App worktree, captures artifacts, diagnoses the exact stop point with `/diagnose-why-work-stopped`, requests board confirmation before any product fix, then reruns against the same worktree. Use whenever an i...