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.
Checking agent metadata and status. An agent skill from golemcloud/golem.
Install Golem Get Agent Metadata
$ npx skills add golemcloud/golem --skill golem-get-agent-metadata -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install golemcloud/golem golem-get-agent-metadata --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/golemcloud/golem.git skills-src && mkdir -p .claude/skills && cp -r skills-src/golem-skills/skills/common/golem-get-agent-metadata .claude/skills/golem-get-agent-metadata && 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 "golem-get-agent-metadata" agent skill from https://github.com/golemcloud/golem/tree/main/golem-skills/skills/common/golem-get-agent-metadata into .claude/skills/golem-get-agent-metadata/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "golem-get-agent-metadata", 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/golemcloud/golem/tree/main/golem-skills/skills/common/golem-get-agent-metadataType 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 golemcloud/golem --skill golem-get-agent-metadata -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install golemcloud/golem golem-get-agent-metadata --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/golemcloud/golem.git skills-src && mkdir -p .agents/skills && cp -r skills-src/golem-skills/skills/common/golem-get-agent-metadata .agents/skills/golem-get-agent-metadata && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "golem-get-agent-metadata" agent skill from https://github.com/golemcloud/golem/tree/main/golem-skills/skills/common/golem-get-agent-metadata into .agents/skills/golem-get-agent-metadata/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "golem-get-agent-metadata", 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 golemcloud/golem --skill golem-get-agent-metadata -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install golemcloud/golem golem-get-agent-metadata --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/golemcloud/golem.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/golem-skills/skills/common/golem-get-agent-metadata .cursor/skills/golem-get-agent-metadata && 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 "golem-get-agent-metadata" agent skill from https://github.com/golemcloud/golem/tree/main/golem-skills/skills/common/golem-get-agent-metadata into .cursor/skills/golem-get-agent-metadata/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "golem-get-agent-metadata", 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/golemcloud/golem.git --path golem-skills/skills/common/golem-get-agent-metadata--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 golemcloud/golem --skill golem-get-agent-metadata -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install golemcloud/golem golem-get-agent-metadata --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/golemcloud/golem.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/golem-skills/skills/common/golem-get-agent-metadata .gemini/skills/golem-get-agent-metadata && 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 "golem-get-agent-metadata" agent skill from https://github.com/golemcloud/golem/tree/main/golem-skills/skills/common/golem-get-agent-metadata into .gemini/skills/golem-get-agent-metadata/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "golem-get-agent-metadata", 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 golemcloud/golem golem-get-agent-metadataInstalls 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 golemcloud/golem --skill golem-get-agent-metadata -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/golemcloud/golem.git skills-src && mkdir -p .github/skills && cp -r skills-src/golem-skills/skills/common/golem-get-agent-metadata .github/skills/golem-get-agent-metadata && 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 "golem-get-agent-metadata" agent skill from https://github.com/golemcloud/golem/tree/main/golem-skills/skills/common/golem-get-agent-metadata into .github/skills/golem-get-agent-metadata/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "golem-get-agent-metadata", 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 golemcloud/golem --skill golem-get-agent-metadata -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install golemcloud/golem golem-get-agent-metadata --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/golemcloud/golem.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/golem-skills/skills/common/golem-get-agent-metadata .opencode/skills/golem-get-agent-metadata && 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 "golem-get-agent-metadata" agent skill from https://github.com/golemcloud/golem/tree/main/golem-skills/skills/common/golem-get-agent-metadata into .opencode/skills/golem-get-agent-metadata/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "golem-get-agent-metadata", 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
golem-get-agent-metadata- GitHub stars
- 1.5k
- Token cost
- ~234 tokens
- SKILL.md length
- 89 words
- Files
- 1
- Skills in repo
- 289
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Checking agent metadata and status. An agent skill from golemcloud/golem.
- Inspecting an agents state
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Component revision
- Environment variables
What it does
Golem Get Agent Metadata is an agent skill from golemcloud/golem. Checking agent metadata and status. Use when inspecting an agent's state, component revision, environment variables, update history, or current status.
Its SKILL.md is about 230 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: Golem Cloud is the agent-native platform for building AI agents and distributed applications that never lose state, never duplicate work, and never require you to build…
When your agent uses it
- Inspecting an agents state
- Component revision
- Environment variables
Example prompts
- “/golem-get-agent-metadata”
What it can do on your machine
Read from SKILL.md and the folder at commit c6a3029. 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 bash).
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 no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Golem Get Agent Metadata loads about 234 tokens when it runs. Until then it costs about 44 tokens; SKILL.md has 89 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 passed
The automated check found no risky patterns in SKILL.md.
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 89 words (~234 tokens).
“Both golem and golem-cli can be used — all commands below work with either binary.”
- name
- golem-get-agent-metadata
Files
Just SKILL.md in golem-skills/skills/common/golem-get-agent-metadata of golemcloud/golem.
Open the folder on GitHubat commit c6a3029
Compare with similar skills
Golem Get Agent Metadata 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 |
|---|---|---|---|---|---|---|
| Golem Get Agent Metadata this skillgolemcloud/golem | 1.5k | — | ~234 | Automated safety check: Pass | 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 golemcloud/golem
All 289 skills in this repoMoonbit C Binding
golemcloud/golem
Guide for writing MoonBit bindings to C libraries using native FFI.
Adding Dependencies
golemcloud/golem
Adding or updating crate dependencies in the Golem workspace.
Analysing CI Failures
golemcloud/golem
Analysing GitHub Actions CI failures from a run URL. An agent skill from golemcloud/golem.
Creating New Builtin Plugins
golemcloud/golem
Adds a built-in WASM plugin that is externally released and provisioned by the registry service.
DB Migration Scripts
golemcloud/golem
Writing database migration SQL scripts. An agent skill from golemcloud/golem.
Debugging Hanging Tests
golemcloud/golem
Diagnosing and fixing hanging worker executor or integration tests.
Related
Categories
Questions about Golem Get Agent Metadata
What does Golem Get Agent Metadata do?
Checking agent metadata and status. An agent skill from golemcloud/golem. Golem Get Agent Metadata is an agent skill from golemcloud/golem. Checking agent metadata and status.
When should I use Golem Get Agent Metadata?
Golem Get Agent Metadata fits situations like: inspecting an agents state; component revision; environment variables.
How do I install Golem Get Agent Metadata in Claude Code?
Run `npx skills add golemcloud/golem --skill golem-get-agent-metadata -a claude-code`. Or copy the skill folder (golem-skills/skills/common/golem-get-agent-metadata in golemcloud/golem) into .claude/skills/golem-get-agent-metadata in your project. Claude Code loads it when a task matches its description.
How do I install Golem Get Agent Metadata in Codex?
Run `npx skills add golemcloud/golem --skill golem-get-agent-metadata -a codex`. Or copy the skill folder (golem-skills/skills/common/golem-get-agent-metadata in golemcloud/golem) into .agents/skills/golem-get-agent-metadata in your project. Codex loads it when a task matches its description.
Can I use Golem Get Agent Metadata 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 golemcloud/golem --skill golem-get-agent-metadata -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/golem-get-agent-metadata, .gemini/skills/golem-get-agent-metadata, .github/skills/golem-get-agent-metadata and .opencode/skills/golem-get-agent-metadata in your project.
What does Golem Get Agent Metadata need to run?
SKILL.md names no scripts, command-line tools or credentials: Golem Get Agent Metadata is instructions for the agent only.
Does Golem Get Agent Metadata 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 Golem Get Agent Metadata safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Golem Get Agent Metadata use?
Golem Get Agent Metadata 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 Golem Get Agent Metadata use?
About 234 tokens (SKILL.md is roughly 936 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 Golem Get Agent Metadata?
Skills that share tags, products or a category with Golem Get Agent Metadata: 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 Golem Get Agent Metadata?
golemcloud (a GitHub organization) maintains it in golemcloud/golem, which has 1,507 GitHub stars. The repository holds 289 skills in this directory. The repository was last updated on October 8, 2026.
Source: golemcloud/golem on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.