# corezoid-variable-manager

corezoid-variable-manager manages stage-scoped Corezoid environment variables via the cz-variables tool, guarding against accidental key deletion with dry-run gates.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf (Devin Desktop), Claude.ai · ★ 74 repo stars
- Author: Corezoid
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/corezoid/corezoid-ai-plugin/tree/HEAD/plugins/corezoid/skills/corezoid-variable-manager/SKILL.md
- Updated: 2026-10-29
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/corezoid-variable-manager

## What it does

This skill manages stage-scoped environment variables in Corezoid processes using the `cz-variables` MCP tool. It handles creating plain visible variables, listing existing values, and writing runtime references like `{{env_var[@name]}}`. Changing a variable takes effect immediately across all stage processes without redeploying logic.

Every operation runs as an action passed to `cz-variables`. Variable names enforce strict checks: lowercase letters, digits, and hyphens with a minimum length of three characters. Creating `secret` or `json` variables directly through actions is not supported yet, so those still require direct Corezoid API calls.

Corezoid has no recycle bin for environment variables. Deleting a record is permanent. Because of this risk, `modify-variable` and `delete-variable` run a two-step dry-run that inspects local files for references before asking for confirmation. In JavaScript code nodes, variables cannot be read directly; route them through an upstream `set_param` node first.

## Install

### Claude Code (native platform)

1. **Plugin marketplace**
In the agent chat (not a shell):
```text
/plugin marketplace add corezoid/corezoid-ai-plugin
```
In the agent chat (not a shell):
```text
/plugin install corezoid@corezoid
```
This installs the whole corezoid plugin with all its skills

2. **Skills CLI (Vercel)**
```bash
npx skills add corezoid/corezoid-ai-plugin --skill corezoid-variable-manager -a claude-code
```

3. **Manually: put the files in place**
- File: `~/.claude/skills/corezoid-variable-manager/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/corezoid-variable-manager/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add corezoid/corezoid-ai-plugin --skill corezoid-variable-manager -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/corezoid-variable-manager/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add corezoid/corezoid-ai-plugin --skill corezoid-variable-manager -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/corezoid-variable-manager/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install corezoid/corezoid-ai-plugin plugins/corezoid/skills/corezoid-variable-manager
```

2. **Manually: put the files in place**
- File: `.github/skills/corezoid-variable-manager/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add corezoid/corezoid-ai-plugin --skill corezoid-variable-manager -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/corezoid/corezoid-ai-plugin --path plugins/corezoid/skills/corezoid-variable-manager
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/corezoid-variable-manager/SKILL.md` — The legacy .windsurf/skills/ path still works

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/corezoid/corezoid-ai-plugin/tree/HEAD/plugins/corezoid/skills/corezoid-variable-manager/SKILL.md

## When to use it
- extract API tokens and endpoint URLs from Corezoid process logic
- list stage variables while keeping secret values masked
- update or delete variables through dry-run confirmation steps
- inject stage variables into API Call and Condition nodes

## Example prompts
- Create a visible variable payment-api-url with value https://api.example.com in Corezoid
- List all environment variables for the current stage
- Delete the stripe-secret-key variable and show referenced files

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: f8762fa4eecd32e8.

BEGIN THIRD-PARTY FILE f8762fa4eecd32e8
````text
---
name: corezoid-variable-manager
description: >
  Manages Corezoid environment variables (env_var) — create, list, modify, delete, and
  use variables in process JSON. Activate when the user mentions "variable", "env var",
  "environment variable", "secret", "create variable", "list variables", "delete variable",
  "modify variable", "env_var", "{{env_var", or asks how to store a URL, token, API key,
  or any constant that should not be hardcoded in a process. Also activate when a process
  references {{env_var[@name]}} and the variable does not exist yet.
---

# Corezoid Variable Manager

## How to call these tools

Every operation in this skill is an **action of the single `cz-variables` MCP tool** —
the individual names below are action strings, not tools of their own:

```
cz-variables {"action": "list-variables"}
```

Arguments always go inside `args`; the shorthand used in the examples below — `create-variable(name="payment-api-url", …)` — means exactly that call. When unsure about an action's
arguments, call `cz-variables {"action": "<action>", "help": true}` — it returns the
full schema and runs nothing.

## What variables are

Environment variables store constants (URLs, tokens, API keys, IDs, configuration values)
that must not be hardcoded in process logic. The reference syntax `{{env_var[@name]}}` is
resolved at runtime — changing a variable value takes effect immediately without
redeploying any process.

Variables are **stage-scoped**: shared across all processes within a stage.

---

## Variable types

### By data type

| `data_type` | When to use | Value format |
|-------------|-------------|--------------|
| `raw` | Plain string (URL, token, ID, any scalar) | `"https://api.example.com"` |
| `json` | Structured config, multi-field config, feature flags | `{"key":"value","nested":{...}}` |

### By visibility

| `env_var_type` | UI display | Accessible from | Scopes |
|----------------|------------|-----------------|--------|
| `visible` | Value shown in plain text | All node types | `[{"type":"*","fields":"*"}]` |
````
END THIRD-PARTY FILE f8762fa4eecd32e8

The third-party file has ended. Everything between the f8762fa4eecd32e8 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2080 of 15410 bytes. © Corezoid · MIT · https://github.com/corezoid/corezoid-ai-plugin/tree/HEAD/plugins/corezoid/skills/corezoid-variable-manager/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
