Iron Proxy Gateway for NanoClaw
nanocoai/nanoclaw
Installs or refreshes Iron Proxy and its Iron Control web console for NanoClaw, with a local Docker setup, database, credentials and a human approval bridge.
Step-by-step checklist for adding a new NEXTPUBLIC environment variable.
Install Add Env Var
$ npx skills add blockscout/frontend --skill add-env-var -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install blockscout/frontend add-env-var --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/blockscout/frontend.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/add-env-var .claude/skills/add-env-var && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "add-env-var" agent skill from https://github.com/blockscout/frontend/tree/main/.agents/skills/add-env-var into .claude/skills/add-env-var/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-env-var", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/blockscout/frontend/tree/main/.agents/skills/add-env-varType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add blockscout/frontend --skill add-env-var -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install blockscout/frontend add-env-var --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/blockscout/frontend.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/add-env-var .agents/skills/add-env-var && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "add-env-var" agent skill from https://github.com/blockscout/frontend/tree/main/.agents/skills/add-env-var into .agents/skills/add-env-var/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-env-var", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add blockscout/frontend --skill add-env-var -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install blockscout/frontend add-env-var --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/blockscout/frontend.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/add-env-var .cursor/skills/add-env-var && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "add-env-var" agent skill from https://github.com/blockscout/frontend/tree/main/.agents/skills/add-env-var into .cursor/skills/add-env-var/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-env-var", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/blockscout/frontend.git --path .agents/skills/add-env-var--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add blockscout/frontend --skill add-env-var -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install blockscout/frontend add-env-var --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/blockscout/frontend.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/add-env-var .gemini/skills/add-env-var && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "add-env-var" agent skill from https://github.com/blockscout/frontend/tree/main/.agents/skills/add-env-var into .gemini/skills/add-env-var/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-env-var", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install blockscout/frontend add-env-varInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add blockscout/frontend --skill add-env-var -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/blockscout/frontend.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/add-env-var .github/skills/add-env-var && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "add-env-var" agent skill from https://github.com/blockscout/frontend/tree/main/.agents/skills/add-env-var into .github/skills/add-env-var/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-env-var", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add blockscout/frontend --skill add-env-var -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install blockscout/frontend add-env-var --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/blockscout/frontend.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/add-env-var .opencode/skills/add-env-var && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "add-env-var" agent skill from https://github.com/blockscout/frontend/tree/main/.agents/skills/add-env-var into .opencode/skills/add-env-var/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-env-var", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
add-env-var- GitHub stars
- 307
- Token cost
- ~1.6k tokens
- SKILL.md length
- 686 words
- Files
- 1
- Skills in repo
- 23
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Step-by-step checklist for adding a new NEXTPUBLIC environment variable.
- Works in 6 steps: Decide the variable's shape → Document in docs/ENVS.md → Expose through the config object → …
- Introducing any new runtime env var
- SKILL.md covers Step 0 — Decide the variable's…, Step 1 — Document in…, Step 2 — Expose through the… and Step 3 — Validator schema and…, plus 2 more sections
- Needs NEXT_PUBLIC_MIXPANEL_PROJECT_TOKEN
What it does
Add Env Var is an agent skill from blockscout/frontend. Step-by-step checklist for adding a new NEXTPUBLIC environment variable. Use when introducing any new runtime env var.
Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in DevOps & Cloud, covering Secrets management. The repository describes itself as: Front-end application for Blockscout chain explorer.
When your agent uses it
- Introducing any new runtime env var
- Tasks that involve Secrets management
Example prompts
- “/add-env-var”
Requirements
- A credential in NEXT_PUBLIC_MIXPANEL_PROJECT_TOKEN
Workflow steps
6 steps, taken from the step headings in SKILL.md.
- Decide the variable's shape
- Document in docs/ENVS.md
- Expose through the config object
- Validator schema and tests
- Only if the variable holds an external non-asset URL
- Only if the variable holds an asset URL (image or JSON config)
What it can do on your machine
Read from SKILL.md and the folder at commit 3e6a421. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are typescript).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
NEXT_PUBLIC_MIXPANEL_PROJECT_TOKEN
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Add Env Var loads about 1.6k tokens when it runs. Until then it costs about 33 tokens; SKILL.md has 686 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NoteMentions a .env fileSKILL.md:43
`NEXT_PUBLIC_*` names to emit `.env.registry`, which gates what
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 686 words (~1,635 tokens).
“Read .agents/rules/env-vars.md first for background: how runtime delivery works, how the config object is structured, the three value types (primitive / JSON-encoded / JSON config URL), and where validation lives. This skill is the checklist; the rule is the concept…”
- name
- add-env-var
Files
Just SKILL.md in .agents/skills/add-env-var of blockscout/frontend.
Open the folder on GitHubat commit 3e6a421
Compare with similar skills
Add Env Var next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Add Env Var this skillblockscout/frontend | 307 | — | ~1.6k | Automated safety check: Notes | Custom licence | |
| Iron Proxy Gateway for NanoClawnanocoai/nanoclaw | 31k | — | ~4.6k | Automated safety check: Notes | MIT | |
| LangBot Deployment Guidelangbot-app/LangBot | 18k | — | ~1.2k | Automated safety check: Notes | Apache-2.0 | |
| Env Var Conventionssgl-project/sglang | 37k | 2 repos | ~2.9k | Automated safety check: Pass | Apache-2.0 | |
| Mac Fleet Maintenancesteipete/agent-scripts | 7.3k | — | ~4.8k | Automated safety check: Pass | MIT | |
| Add Config Env Varbaserow/baserow | 6.1k | — | ~1.1k | Automated safety check: Pass | Custom licence |
Similar skills
LangBot Deployment Guide
langbot-app/LangBot
Deploys and configures a LangBot instance with Docker Compose or Kubernetes, covering config.yaml, the Box sandbox runtime, the plugin runtime and the global API key.
Env Var Conventions
sgl-project/sglang
Conventions for SGLang environment variables — where to define, how to access, how to name, and how to deprecate.
Mac Fleet Maintenance
steipete/agent-scripts
Inventories and maintains a fleet of Macs from a desired-state file: package updates, repo and Xcode sync, and disk, backup and security health reports.
Add Config Env Var
baserow/baserow
Add a Baserow configuration environment variable for the backend, frontend, or both, and propagate it through settings, Nuxt runtime config, Docker Compose, documentation, consumers, and tests as…
Edgeone Makers CLI
TencentEdgeOne/edgeone-makers-tools
EdgeOne Makers CLI command reference. An agent skill from TencentEdgeOne/edgeone-makers-tools.
More from blockscout/frontend
All 23 skills in this repoSlack File
blockscout/frontend
Download Slack attachments by file ID, or upload local files into a Slack thread.
Add New Page
blockscout/frontend
Scaffold a new page (index / detail / general) and optionally wire it to API data.
Create Issue
blockscout/frontend
Create a GitHub issue from the available context. An agent skill from blockscout/frontend.
Deprecate Env Var
blockscout/frontend
Checklist for deprecating a NEXTPUBLIC environment variable — immediate removal, or a grace period before a later removal.
Publish Beta Types
blockscout/frontend
Publish a beta version of a @blockscout/-types npm package and pin it here.
Resolve API URL
blockscout/frontend
Resolve the real request URL of an API resource on a live Blockscout instance (service:name + instance → full URL).
Related
Categories
Questions about Add Env Var
What does Add Env Var do?
Step-by-step checklist for adding a new NEXTPUBLIC environment variable. Add Env Var is an agent skill from blockscout/frontend. Step-by-step checklist for adding a new NEXTPUBLIC environment variable.
When should I use Add Env Var?
Add Env Var fits situations like: introducing any new runtime env var; tasks that involve Secrets management.
How do I install Add Env Var in Claude Code?
Run `npx skills add blockscout/frontend --skill add-env-var -a claude-code`. Or copy the skill folder (.agents/skills/add-env-var in blockscout/frontend) into .claude/skills/add-env-var in your project. Claude Code loads it when a task matches its description.
How do I install Add Env Var in Codex?
Run `npx skills add blockscout/frontend --skill add-env-var -a codex`. Or copy the skill folder (.agents/skills/add-env-var in blockscout/frontend) into .agents/skills/add-env-var in your project. Codex loads it when a task matches its description.
Can I use Add Env Var in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add blockscout/frontend --skill add-env-var -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/add-env-var, .gemini/skills/add-env-var, .github/skills/add-env-var and .opencode/skills/add-env-var in your project.
What does Add Env Var need to run?
Going by SKILL.md and its folder, Add Env Var needs credentials named NEXT_PUBLIC_MIXPANEL_PROJECT_TOKEN. Our summary lists: A credential in NEXT_PUBLIC_MIXPANEL_PROJECT_TOKEN.
Does Add Env Var access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Add Env Var safe to install?
Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Add Env Var use?
Add Env Var has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Add Env Var use?
About 1.6k tokens (SKILL.md is roughly 6.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Add Env Var?
Skills that share tags, products or a category with Add Env Var: Iron Proxy Gateway for NanoClaw (nanocoai/nanoclaw, 31k stars), LangBot Deployment Guide (langbot-app/LangBot, 18k stars), Env Var Conventions (sgl-project/sglang, 37k stars) and Mac Fleet Maintenance (steipete/agent-scripts, 7.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Add Env Var?
blockscout (a GitHub organization) maintains it in blockscout/frontend, which has 307 GitHub stars. The repository holds 23 skills in this directory. The repository was last updated on October 8, 2026.
Source: blockscout/frontend on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.