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.
Setup and launch GenLayer Studio with Docker Compose. An agent skill from genlayerlabs/genlayer-studio.
Install Setup
$ npx skills add genlayerlabs/genlayer-studio --skill setup -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install genlayerlabs/genlayer-studio setup --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/genlayerlabs/genlayer-studio.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/setup .claude/skills/setup && 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 "setup" agent skill from https://github.com/genlayerlabs/genlayer-studio/tree/main/.claude/skills/setup into .claude/skills/setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "setup", 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/genlayerlabs/genlayer-studio/tree/main/.claude/skills/setupType 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 genlayerlabs/genlayer-studio --skill setup -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install genlayerlabs/genlayer-studio setup --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/genlayerlabs/genlayer-studio.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/setup .agents/skills/setup && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "setup" agent skill from https://github.com/genlayerlabs/genlayer-studio/tree/main/.claude/skills/setup into .agents/skills/setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "setup", 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 genlayerlabs/genlayer-studio --skill setup -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install genlayerlabs/genlayer-studio setup --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/genlayerlabs/genlayer-studio.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/setup .cursor/skills/setup && 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 "setup" agent skill from https://github.com/genlayerlabs/genlayer-studio/tree/main/.claude/skills/setup into .cursor/skills/setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "setup", 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/genlayerlabs/genlayer-studio.git --path .claude/skills/setup--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 genlayerlabs/genlayer-studio --skill setup -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install genlayerlabs/genlayer-studio setup --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/genlayerlabs/genlayer-studio.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/setup .gemini/skills/setup && 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 "setup" agent skill from https://github.com/genlayerlabs/genlayer-studio/tree/main/.claude/skills/setup into .gemini/skills/setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "setup", 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 genlayerlabs/genlayer-studio setupInstalls 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 genlayerlabs/genlayer-studio --skill setup -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/genlayerlabs/genlayer-studio.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/setup .github/skills/setup && 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 "setup" agent skill from https://github.com/genlayerlabs/genlayer-studio/tree/main/.claude/skills/setup into .github/skills/setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "setup", 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 genlayerlabs/genlayer-studio --skill setup -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install genlayerlabs/genlayer-studio setup --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/genlayerlabs/genlayer-studio.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/setup .opencode/skills/setup && 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 "setup" agent skill from https://github.com/genlayerlabs/genlayer-studio/tree/main/.claude/skills/setup into .opencode/skills/setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "setup", 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
setup- GitHub stars
- 180
- Token cost
- ~524 tokens
- SKILL.md length
- 134 words
- Files
- 1
- Skills in repo
- 10
- Repo updated
- First seen
- Licence
- MIT
At a glance
Setup and launch GenLayer Studio with Docker Compose. An agent skill from genlayerlabs/genlayer-studio.
- Works in 4 steps: Verify Docker is Running → Start All Services → Initialize Database (first time only) → …
- Tasks that involve Containers
- SKILL.md covers Prerequisites, Setup Steps, Common Commands and Alternative: GenLayer CLI, plus 1 more section
- Calls docker, curl and jq
What it does
Setup is an agent skill from genlayerlabs/genlayer-studio. Setup and launch GenLayer Studio with Docker Compose
Its SKILL.md is about 520 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 Containers. It works with Docker. The repository describes itself as: An interactive sandbox to explore the GenLayer Protocol. The licence is MIT.
When your agent uses it
- Tasks that involve Containers
Example prompts
- “/setup”
Requirements
- Docker
Workflow steps
4 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit c940729. 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
Shell commands in SKILL.md call:
dockercurljq
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use docker and curl, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Setup loads about 524 tokens when it runs. Until then it costs about 15 tokens; SKILL.md has 134 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:86
# Or use different ports in .env
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
The full file from genlayerlabs/genlayer-studio at commit c940729, republished under its MIT licence (© genlayerlabs). 134 words, ~524 tokens.
Download SKILL.mdSave it as
.claude/skills/setup/SKILL.md (or your agent's skills folder).- name
- setup
- description
- Setup and launch GenLayer Studio with Docker Compose
Setup GenLayer Studio
Setup and launch the entire GenLayer Studio development environment.
Prerequisites
- Docker installed and running
Setup Steps
1. Verify Docker is Running
docker info > /dev/null 2>&1 && echo "Docker is running" || echo "Docker is not running"2. Start All Services
docker compose up -dThis starts:
- Frontend: Vue 3 app on http://localhost:8080
- Backend: Flask JSON-RPC API on http://localhost:4000
- PostgreSQL: Database on port 5432
- WebDriver: Selenium service for contract sandboxing
3. Initialize Database (first time only)
genlayer initOr manually:
docker exec -it genlayer-studio-backend-1 alembic upgrade head4. Verify Services
# Check all containers are running
docker compose ps
# Test backend health
curl -s http://localhost:4000/health | jq .
# Open frontend
open http://localhost:8080Common Commands
| Command | Description |
|---|---|
docker compose up -d | Start all services (detached) |
docker compose down | Stop all services |
docker compose down -v | Stop and clear all data |
docker compose logs -f | Tail all logs |
docker compose logs -f backend | Tail backend logs |
docker compose restart backend | Restart specific service |
Alternative: GenLayer CLI
If you have the GenLayer CLI installed:
genlayer up # Start all services
genlayer init # Initialize database
genlayer down # Stop all servicesTroubleshooting
Port Already in Use
# Find what's using port 8080
lsof -i :8080
# Or use different ports in .envDatabase Connection Issues
# Check database is ready
docker compose logs db
# Reset database
docker compose down -v && docker compose up -dContainer Won't Start
# Check logs for specific service
docker compose logs backend
# Rebuild containers
docker compose build --no-cache
docker compose up -d© genlayerlabs, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .claude/skills/setup of genlayerlabs/genlayer-studio.
Open the folder on GitHubat commit c940729
Compare with similar skills
Setup 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 |
|---|---|---|---|---|---|---|
| Setup this skillgenlayerlabs/genlayer-studio | 180 | — | ~524 | Automated safety check: Notes | MIT | |
| Iron Proxy Gateway for NanoClawnanocoai/nanoclaw | 31k | — | ~4.6k | Automated safety check: Notes | MIT | |
| GreptimeDB Dev Docker ImageGreptimeTeam/greptimedb | 6.7k | — | ~4k | Automated safety check: Notes | Apache-2.0 | |
| Senior DevOps Toolkitmaslennikov-ig/claude-code-orchestrator-kit | 260 | 6 repos | ~1.1k | Automated safety check: Notes | Custom licence | |
| LangBot Deployment Guidelangbot-app/LangBot | 18k | — | ~1.2k | Automated safety check: Notes | Apache-2.0 | |
| Build Openshell Mxc WindowsNVIDIA/OpenShell | 15k | — | ~4.9k | Automated safety check: Pass | Apache-2.0 |
Similar skills
GreptimeDB Dev Docker Image
GreptimeTeam/greptimedb
Packages a locally built GreptimeDB debug binary into a development-only Docker image for local-cluster testing, with an optional push to a dev registry.
Senior DevOps Toolkit
maslennikov-ig/claude-code-orchestrator-kit
Comprehensive DevOps skill for CI/CD, infrastructure automation, containerization, and cloud platforms (AWS, GCP, Azure). Includes pipeline setup…
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.
- Official
Build Openshell Mxc Windows
NVIDIA/OpenShell
Maintain and validate OpenShell's build-only Windows MSVC lane for x64 and ARM64.
Omnigent Docker Compose Deploy
omnigent-ai/omnigent
Brings up the Omnigent server and Postgres as a Docker compose stack on any Docker host, and covers the Dockerfile's runtime and host build targets for extending it to a new platform.
More from genlayerlabs/genlayer-studio
All 10 skills in this repoCloudflare CLI
genlayerlabs/genlayer-studio
Debug and manage Cloudflare DNS, cache, and proxy settings using flarectl
Create PR
genlayerlabs/genlayer-studio
Create GitHub pull requests by analyzing branch diff and following the project template
Discord Community Feedback
genlayerlabs/genlayer-studio
Monitor Discord community channel for user-reported bugs and issues
Hosted Studio Debug
genlayerlabs/genlayer-studio
Debug GenLayer Studio deployments via ArgoCD CLI. An agent skill from genlayerlabs/genlayer-studio.
Integration Tests
genlayerlabs/genlayer-studio
Setup Python virtual environment and run integration tests with gltest
Linear Issue Fixer
genlayerlabs/genlayer-studio
Fetch the most urgent Linear issue with tag "studio" and size XS, then fix it
Related
Works with
Categories
Questions about Setup
What does Setup do?
Setup and launch GenLayer Studio with Docker Compose. An agent skill from genlayerlabs/genlayer-studio. Setup is an agent skill from genlayerlabs/genlayer-studio.
When should I use Setup?
Setup fits situations like: tasks that involve Containers.
How do I install Setup in Claude Code?
Run `npx skills add genlayerlabs/genlayer-studio --skill setup -a claude-code`. Or copy the skill folder (.claude/skills/setup in genlayerlabs/genlayer-studio) into .claude/skills/setup in your project. Claude Code loads it when a task matches its description.
How do I install Setup in Codex?
Run `npx skills add genlayerlabs/genlayer-studio --skill setup -a codex`. Or copy the skill folder (.claude/skills/setup in genlayerlabs/genlayer-studio) into .agents/skills/setup in your project. Codex loads it when a task matches its description.
Can I use Setup 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 genlayerlabs/genlayer-studio --skill setup -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/setup, .gemini/skills/setup, .github/skills/setup and .opencode/skills/setup in your project.
What does Setup need to run?
Going by SKILL.md and its folder, Setup needs the command-line tools its instructions call (docker, curl and jq). Our summary lists: Docker.
Does Setup access the network?
SKILL.md contains no URLs. Its commands use docker and curl, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Setup 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 Setup use?
Setup is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Setup use?
About 524 tokens (SKILL.md is roughly 2.1k 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 Setup?
Skills that share tags, products or a category with Setup: Iron Proxy Gateway for NanoClaw (nanocoai/nanoclaw, 31k stars), GreptimeDB Dev Docker Image (GreptimeTeam/greptimedb, 6.7k stars), Senior DevOps Toolkit (maslennikov-ig/claude-code-orchestrator-kit, 260 stars) and LangBot Deployment Guide (langbot-app/LangBot, 18k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Setup?
genlayerlabs (a GitHub organization) maintains it in genlayerlabs/genlayer-studio, which has 180 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on October 7, 2026.
Source: genlayerlabs/genlayer-studio on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.