My AI Agent Built Its Own Tools — Here's How OpenClaw Skills Actually Work

#ai #productivity #opensource #tutorial

I spent 12 hours installing OpenClaw on Windows WSL. The setup was painful,
but what happened after was worth every minute.

The moment that changed my mind

I told my AI agent: "Create a new skill called github-trending that shows
me today's top GitHub projects."

Two minutes later, it had written the skill code, committed it to git,
and delivered a formatted report of today's trending repos — complete
with Star counts and analysis of why each project matters.

The AI didn't just use a tool. It built a tool, installed it, and used it.

The painful part: skill dependencies

OpenClaw has 55 optional skills, but 45 of them failed to install on
my first try. The error messages weren't helpful:

Install failed: github — brew not installed
Install failed: nano-pdf — uv not installed

After hours of troubleshooting, I figured out the dependency chain:

Skills need system tools (gh, poppler, ffmpeg) which need
package managers (Homebrew, uv) which need your OS to be
properly configured.

The fix was straightforward once I understood it:

# Install Homebrew
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"

# Install core packages
brew install gh uv poppler ffmpeg imagemagick

# Let OpenClaw fix the rest
openclaw doctor --fix

My eligible skills went from 10 → 14 → 16.

What skills can actually do

Once configured, the results are genuinely impressive.

I asked my agent to analyze today's OpenClaw GitHub activity and
triage it into priority levels. In 30 seconds, it delivered a
structured analysis of 20+ items — commits, issues, discussions —
categorized into "needs attention," "good to know," and "just FYI."

A human doing this manually would need 30-60 minutes.