Supercov Security
supercorp-ai/supercov
Scans a repository's source for security vulnerabilities with the supercov CLI, pointing to the line of each finding and mapping it to CWE classes.
Troubleshooting Golem build failures and debugging manifest file (golem.yaml) configuration.
Install Golem Troubleshoot Build
$ npx skills add golemcloud/golem --skill golem-troubleshoot-build -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install golemcloud/golem golem-troubleshoot-build --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-troubleshoot-build .claude/skills/golem-troubleshoot-build && 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-troubleshoot-build" agent skill from https://github.com/golemcloud/golem/tree/main/golem-skills/skills/common/golem-troubleshoot-build into .claude/skills/golem-troubleshoot-build/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "golem-troubleshoot-build", 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-troubleshoot-buildType 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-troubleshoot-build -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install golemcloud/golem golem-troubleshoot-build --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-troubleshoot-build .agents/skills/golem-troubleshoot-build && 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-troubleshoot-build" agent skill from https://github.com/golemcloud/golem/tree/main/golem-skills/skills/common/golem-troubleshoot-build into .agents/skills/golem-troubleshoot-build/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "golem-troubleshoot-build", 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-troubleshoot-build -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install golemcloud/golem golem-troubleshoot-build --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-troubleshoot-build .cursor/skills/golem-troubleshoot-build && 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-troubleshoot-build" agent skill from https://github.com/golemcloud/golem/tree/main/golem-skills/skills/common/golem-troubleshoot-build into .cursor/skills/golem-troubleshoot-build/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "golem-troubleshoot-build", 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-troubleshoot-build--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-troubleshoot-build -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install golemcloud/golem golem-troubleshoot-build --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-troubleshoot-build .gemini/skills/golem-troubleshoot-build && 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-troubleshoot-build" agent skill from https://github.com/golemcloud/golem/tree/main/golem-skills/skills/common/golem-troubleshoot-build into .gemini/skills/golem-troubleshoot-build/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "golem-troubleshoot-build", 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-troubleshoot-buildInstalls 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-troubleshoot-build -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-troubleshoot-build .github/skills/golem-troubleshoot-build && 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-troubleshoot-build" agent skill from https://github.com/golemcloud/golem/tree/main/golem-skills/skills/common/golem-troubleshoot-build into .github/skills/golem-troubleshoot-build/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "golem-troubleshoot-build", 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-troubleshoot-build -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-troubleshoot-build --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-troubleshoot-build .opencode/skills/golem-troubleshoot-build && 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-troubleshoot-build" agent skill from https://github.com/golemcloud/golem/tree/main/golem-skills/skills/common/golem-troubleshoot-build into .opencode/skills/golem-troubleshoot-build/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "golem-troubleshoot-build", 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-troubleshoot-build- GitHub stars
- 1.5k
- Token cost
- ~2.1k tokens
- SKILL.md length
- 940 words
- Files
- 1
- Skills in repo
- 289
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Troubleshooting Golem build failures and debugging manifest file (golem.yaml) configuration.
- Works in 2 steps: Build Tool Requirement Checks → Dependency Validation and Auto-Fix
- Environment variables
- SKILL.md covers Build Pipeline Overview, Step 1: Build Tool Requirement…, Step 2: Dependency Validation… and Common Build Errors and…, plus 2 more sections
- Calls cargo, rustc and node
What it does
Golem Troubleshoot Build is an agent skill from golemcloud/golem. Troubleshooting Golem build failures and debugging manifest file (golem.yaml) configuration. Use when a build fails, when environment variables or config values are not applied as expected, when diagnosing why a manifest property has the wrong value, or when using golem component manifest-trace to inspect how golem.yaml layers are resolved.
Its SKILL.md is about 2.1k 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 Development, covering Secrets management. It works with Rust and TypeScript. 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
- Environment variables
- Config values are not applied as expected
- Diagnosing why a manifest property has the wrong value
- Using golem component manifest-trace to inspect how golem.yaml layers are resolved
Example prompts
- “/golem-troubleshoot-build”
Requirements
- Node.js
Workflow steps
2 steps, taken from the step headings in SKILL.md.
- Build Tool Requirement Checks
- Dependency Validation and Auto-Fix
What it can do on your machine
Read from SKILL.md and the folder at commit 8bed66c. 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:
cargorustcnodenpm
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
rust-lang.orgnodejs.orgdocs.moonbitlang.com
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 Troubleshoot Build loads about 2.1k tokens when it runs. Until then it costs about 92 tokens; SKILL.md has 940 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 940 words (~2,056 tokens).
“Both golem and golem-cli can be used — all commands below work with either binary.”
- name
- golem-troubleshoot-build
Files
Just SKILL.md in golem-skills/skills/common/golem-troubleshoot-build of golemcloud/golem.
Open the folder on GitHubat commit 8bed66c
Compare with similar skills
Golem Troubleshoot Build 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 Troubleshoot Build this skillgolemcloud/golem | 1.5k | — | ~2.1k | Automated safety check: Pass | Custom licence | |
| Supercov Securitysupercorp-ai/supercov | 152 | 1 repos | ~236 | Automated safety check: Pass | MIT | |
| Git HooksProrise-cool/Claude-Code-Multi-Agent | 306 | — | ~3.6k | Automated safety check: Notes | None | |
| Project Initathola/claude-night-market | 341 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Pnpm Engineteambit/bit | 18k | — | ~1.9k | Automated safety check: Pass | Custom licence | |
| Testing Changespnpm/pnpm | 37k | — | ~1.1k | Automated safety check: Pass | MIT |
Similar skills
Git Hooks
Prorise-cool/Claude-Code-Multi-Agent
Central authority on git hook implementations, modern best practices, and tooling for .NET/C, JavaScript/TypeScript, Python, and polyglot repositories.
Project Init
athola/claude-night-market
Scaffolds new projects with git, CI/CD workflows, pre-commit hooks, and build config.
Pnpm Engine
teambit/bit
Work on the pnpm Rust engine (@pnpm/napi, the pacquet crates) that bit install runs through.
Testing Changes
pnpm/pnpm
Run the tests that cover a change in the pnpm repository, in the Rust workspace (pnpm/, pnpr/) or the TypeScript CLI (pnpm11/), and recognize the cases where a scoped run passes without testing…
jscpd Code Migration Tracker
kucherenko/jscpd
Measures a code port between languages or frameworks with jscpd's function-level comparison, porting tests before code and tracking what is left unmatched.
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
Works with
Categories
Questions about Golem Troubleshoot Build
What does Golem Troubleshoot Build do?
Troubleshooting Golem build failures and debugging manifest file (golem.yaml) configuration. Golem Troubleshoot Build is an agent skill from golemcloud/golem.yaml) configuration.
When should I use Golem Troubleshoot Build?
Golem Troubleshoot Build fits situations like: environment variables; config values are not applied as expected; diagnosing why a manifest property has the wrong value; using golem component manifest-trace to inspect how golem.yaml layers are resolved.
How do I install Golem Troubleshoot Build in Claude Code?
Run `npx skills add golemcloud/golem --skill golem-troubleshoot-build -a claude-code`. Or copy the skill folder (golem-skills/skills/common/golem-troubleshoot-build in golemcloud/golem) into .claude/skills/golem-troubleshoot-build in your project. Claude Code loads it when a task matches its description.
How do I install Golem Troubleshoot Build in Codex?
Run `npx skills add golemcloud/golem --skill golem-troubleshoot-build -a codex`. Or copy the skill folder (golem-skills/skills/common/golem-troubleshoot-build in golemcloud/golem) into .agents/skills/golem-troubleshoot-build in your project. Codex loads it when a task matches its description.
Can I use Golem Troubleshoot Build 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-troubleshoot-build -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-troubleshoot-build, .gemini/skills/golem-troubleshoot-build, .github/skills/golem-troubleshoot-build and .opencode/skills/golem-troubleshoot-build in your project.
What does Golem Troubleshoot Build need to run?
Going by SKILL.md and its folder, Golem Troubleshoot Build needs the command-line tools its instructions call (cargo, rustc, node and npm). Our summary lists: Node.js.
Does Golem Troubleshoot Build access the network?
SKILL.md names 3 domains. As links in the text: rust-lang.org, nodejs.org and docs.moonbitlang.com. This is read from the text; nothing was executed.
Is Golem Troubleshoot Build 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 Troubleshoot Build use?
Golem Troubleshoot Build 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 Troubleshoot Build use?
About 2.1k tokens (SKILL.md is roughly 8.2k 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 Troubleshoot Build?
Skills that share tags, products or a category with Golem Troubleshoot Build: Supercov Security (supercorp-ai/supercov, 152 stars), Git Hooks (Prorise-cool/Claude-Code-Multi-Agent, 306 stars), Project Init (athola/claude-night-market, 341 stars) and Pnpm Engine (teambit/bit, 18k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Golem Troubleshoot Build?
golemcloud (a GitHub organization) maintains it in golemcloud/golem, which has 1,508 GitHub stars. The repository holds 289 skills in this directory. The repository was last updated on October 10, 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.