#Installed Skills Needs Setup
1 messages ยท Page 1 of 1 (latest)
Yep, โณ needs setup usually means the skill is installed but not eligible yet, not that openclaw skills install failed.
Most likely causes are:
- a missing requirement in
metadata.openclaw.requires(bins,anyBins,env,config, oros) - the binary is on your shell PATH, but not the gateway service PATH
- the skill was installed into a different workspace/agent than the one
listis checking - the current session still has the old skill snapshot
Please paste these:
openclaw --version
openclaw skills list --verbose
openclaw skills check
openclaw skills info <skill-name>
openclaw gateway status
A few concrete checks:
openclaw skills install <slug>installs into the active workspaceskills/directoryopenclaw skills list/info/checkonly inspect skills visible to the current workspace/confignpm install -g <pkg>only helps if the required executable fromrequires.binsis actually on the gateway's PATH- after fixing it, start a new session so OpenClaw picks up the refreshed skill snapshot
If you changed profiles/workspaces and the service may be using different config, also run:
openclaw gateway install --force
from the same profile/env you want the service to use.
Docs:
- https://docs.openclaw.ai/cli/skills
- https://docs.openclaw.ai/tools/skills
- https://docs.openclaw.ai/gateway/troubleshooting
Paste the output and Iโll help narrow it down fast.
openclaw version is OpenClaw 2026.4.2 (d74a122)
openclaw skills info ddg-search:
๐ฆ ddg-search โณ Needs setup
DuckDuckGo HTML search scraper CLI with JSON, CSV, OpenSearch, markdown, and compact outputs.
Details:
Source: openclaw-workspace
Path: ~/.openclaw/workspace/skills/ddg-search-cli/SKILL.md
Homepage: https://github.com/camohiddendj/ddg-search
Requirements:
Binaries: โ ddg-search
Install options:
โ Install ddg-search (npm)
openclaw gateway status:
โ
Service: systemd (disabled)
File logs: /tmp/openclaw-998/openclaw-2026-04-23.log
Service config looks out of date or non-standard.
Service config issue: Gateway service PATH is not set; the daemon should use a minimal PATH.
Recommendation: run "openclaw doctor" (or "openclaw doctor --repair").
Config (cli): ~/.openclaw/openclaw.json
Config (service): ~/.openclaw/openclaw.json
Gateway: bind=loopback (127.0.0.1), port=18789 (env/config)
Probe target: ws://127.0.0.1:18789
Dashboard: http://127.0.0.1:18789/
Probe note: Loopback-only gateway; only local clients can connect.
Runtime: unknown (systemctl not available; systemd user services are required on Linux.)
RPC probe: ok
systemd user services unavailable.
systemd user services are unavailable; install/enable systemd or run the gateway under your supervisor.
If you're in a container, run the gateway in the foreground instead of openclaw gateway.
Listening: 127.0.0.1:18789, [::1]:18789
Troubles: run openclaw status
Troubleshooting: https://docs.openclaw.ai/troubleshooting
Nice, this narrows it down a lot.
The skill itself is installed correctly. The problem is just this line:
Requirements:
Binaries: โ ddg-search
So โณ Needs setup here means OpenClaw cannot find the ddg-search executable on PATH.
For this specific skill, the package/binary should be:
npm install -g ddg-search
Then check:
command -v ddg-search
ddg-search --help
npm prefix -g
echo "$PATH"
If command -v ddg-search is empty, your global npm bin dir is not on PATH. On Linux/macOS the usual fix is:
export PATH="$(npm prefix -g)/bin:$PATH"
Then add that to your shell startup file (~/.bashrc, ~/.zshrc, etc.), reopen the shell, and try again.
Important detail, openclaw skills info is already showing the binary as missing from the current CLI environment, so this is not only a gateway restart issue. The shell where you ran openclaw also cannot see ddg-search.
Your gateway status warning about PATH is also relevant, but secondary here:
Service: systemd (disabled)Gateway service PATH is not set
So if you are running OpenClaw manually or in a container, restart it from a shell where command -v ddg-search works.
If you want the managed service fixed too, run:
openclaw doctor
and if/when user services are available again:
openclaw gateway install --force
After that, start a new session and re-check:
openclaw skills info ddg-search
Docs:
- https://docs.openclaw.ai/tools/skills
- https://docs.openclaw.ai/install/node
- https://docs.openclaw.ai/gateway/troubleshooting
If you paste the output of command -v ddg-search, npm prefix -g, and echo "$PATH", I can tell you the exact next fix.
command -v ddg-search returns /home/alt/.nvm/versions/node/v22.22.2/bin/ddg-search
Aha, yep, that explains it.
ddg-search is installed inside nvm's Node bin dir:
/home/alt/.nvm/versions/node/v22.22.2/bin/ddg-search
So the issue is very likely PATH drift:
your interactive shell sees it, but the OpenClaw process that did the skill check / gateway startup probably did not load the nvm PATH.
Try this in the same shell where command -v ddg-search works:
openclaw skills info ddg-search
If it flips to โ Ready, then that's the whole problem.
Fix
- Start/restart OpenClaw from that same shell
- then start a new session
- re-check:
openclaw skills info ddg-search
If you want it to stick
Make sure nvm is initialized in your shell startup (~/.bashrc / ~/.zshrc) so PATH is present in new shells too.
Your gateway status also showed:
Service: systemd (disabled)systemd user services unavailable
So right now I would run the gateway in the foreground from the shell that has nvm loaded, not rely on the disabled service.
If you later get systemd user services working again, reinstall the gateway service from that same environment:
openclaw gateway install --force
Docs:
- https://docs.openclaw.ai/install/node
- https://docs.openclaw.ai/tools/skills
- https://docs.openclaw.ai/gateway/troubleshooting
If you want, paste the output of:
openclaw skills info ddg-search
echo "$PATH"
from that exact shell, and I can confirm the last step. Glad we caught it ๐ฆ
If this fixed it, please right-click the solution message โ Apps โ โ Mark Solution so Answer Overflow can index it.
Sorry I was in the wrong shell. The one i need to be in has an empty return for command -v ddg-search. After, i export PATH="$(npm prefix -g)/bin:$PATH" then what?
Yep, then do this, in that same shell:
command -v ddg-search
ddg-search --help
openclaw skills info ddg-search
What you want to see is:
command -v ddg-searchreturns a pathddg-search --helpworksopenclaw skills info ddg-searchchanges toโ Ready
If command -v ddg-search is still empty after the export, then install it in that shell's Node environment:
npm install -g ddg-search
Then re-run:
command -v ddg-search
openclaw skills info ddg-search
After it shows โ Ready:
- restart OpenClaw/gateway from that same shell/environment
- start a new session so the skill snapshot refreshes
To make it permanent, add this to your ~/.bashrc or ~/.zshrc:
export PATH="$(npm prefix -g)/bin:$PATH"
Docs: https://docs.openclaw.ai/install/node and https://docs.openclaw.ai/tools/skills
If you want, paste the output of:
npm prefix -g
command -v ddg-search
openclaw skills info ddg-search
and Iโll sanity check it.
npm prefix -g:
/tmp/npm-global
openclaw skills info ddg-search:
๐ฆ ddg-search โณ Needs setup
DuckDuckGo HTML search scraper CLI with JSON, CSV, OpenSearch, markdown, and compact outputs.
Details:
Source: openclaw-workspace
Path: ~/.openclaw/workspace/skills/ddg-search-cli/SKILL.md
Homepage: https://github.com/camohiddendj/ddg-search
Requirements:
Binaries: โ ddg-search
Install options:
โ Install ddg-search (npm)
Tip: use openclaw skills search, openclaw skills install, and openclaw skills update for ClawHub-backed skills.
๐ฆ ddg-search โณ Needs setup
DuckDuckGo HTML search scraper CLI with JSON, CSV, OpenSearch, markdown, and compact outputs.
Details:
Source: openclaw-workspace
Path: ~/.openclaw/workspace/skills/ddg-search-cli/SKILL.md
Homepage: https://github.com/camohiddendj/ddg-search
Requirements:
Binaries: โ ddg-search
Install options:
โ Install ddg-search (npm)
Tip: use openclaw skills search, openclaw skills install, and openclaw skills update for ClawHub-backed skills.
Yep, that explains it.
npm prefix -g being /tmp/npm-global means this shell is using a different Node/npm environment than the one where ddg-search already exists under ~/.nvm/....
So this line:
export PATH="$(npm prefix -g)/bin:$PATH"
only adds /tmp/npm-global/bin, it does not add the nvm binary you found earlier.
Preferred fix
Load nvm in the shell OpenClaw is actually using, then re-check:
export NVM_DIR="$HOME/.nvm"
[ -s "$NVM_DIR/nvm.sh" ] && . "$NVM_DIR/nvm.sh"
command -v ddg-search
openclaw skills info ddg-search
If command -v ddg-search is still empty after that, install it in that same shell/environment:
npm install -g ddg-search
hash -r
command -v ddg-search
openclaw skills info ddg-search