Agent skill

Warden Agent Builder

by LeoYeAI in LeoYeAI/openclaw-master-skills

Build original LangGraph agents for Warden Protocol and prepare them for publishing in Warden Studio.

MITAuto-check: notesAI & LLM Engineering

Install Warden Agent Builder

skills CLI
$ npx skills add LeoYeAI/openclaw-master-skills --skill warden-agent-builder -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install LeoYeAI/openclaw-master-skills warden-agent-builder --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/lex .claude/skills/warden-agent-builder && rm -rf skills-src

Use ~/.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/

Facts

Skill name
warden-agent-builder
GitHub stars
2.2k
Token cost
~4.4k tokens
SKILL.md length
1,511 words
Files
10 (incl. scripts, references, assets)
Skills in repo
1,235
Repo updated
First seen
Licence
MIT

At a glance

Build original LangGraph agents for Warden Protocol and prepare them for publishing in Warden Studio.

  • Works in 10 steps: Study Examples and Choose Your Approach → Initialize Your NEW Agent → Understand LangGraph Agent Structure → …
  • Create new Warden agents (not community examples)
  • SKILL.md covers ⚠️ IMPORTANT: About Example…, Overview, Requirements Checklist and Understanding the Example Agents, plus 6 more sections
  • Runs Python scripts from its folder; calls npm, git and python; reaches github.com; needs OPENAI_API_KEY and LANGSMITH_API_KEY

What it does

Warden Agent Builder is an agent skill from LeoYeAI/openclaw-master-skills. Build original LangGraph agents for Warden Protocol and prepare them for publishing in Warden Studio. Use this skill when users want to: (1) Create new Warden agents (not community examples), (2) Build LangGraph-based crypto/Web3 agents, (3) Deploy agents via LangSmith Deployments or custom infra, (4) Participate in the Warden Agent Builder Incentive Programme (open to OpenClaw agents), or (5) Integrate with Warden Studio for Agent Hub publishing.

Its SKILL.md is about 4.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 12 other files, including scripts, reference files and assets (for example `README.md`, `_meta.json` and `assets/example-configs.md`).

It sits in AI & LLM Engineering, covering Building AI agents. It works with LangGraph and LangSmith. The repository describes itself as: 🧠 Curated collection of 1209+ best OpenClaw skills — weekly updated by MyClaw.ai. The licence is MIT.

When your agent uses it

  • Create new Warden agents (not community examples)
  • Build LangGraph-based crypto/Web3 agents
  • Deploy agents via LangSmith Deployments
  • Participate in the Warden Agent Builder Incentive Programme (open to OpenClaw agents)

Example prompts

  • “/warden-agent-builder”

Requirements

  • Python 3
  • Node.js
  • Docker
  • A credential in OPENAI_API_KEY
  • A credential in LANGSMITH_API_KEY

Workflow steps

10 steps, taken from the step headings in SKILL.md.

  1. Study Examples and Choose Your Approach
  2. Initialize Your NEW Agent
  3. Understand LangGraph Agent Structure
  4. Implement Your Custom Agent Logic
  5. Configure Environment
  6. Test Locally
  7. Agent Design
  8. API Integration
  9. Testing
  10. Documentation

What it can do on your machine

Read from SKILL.md and the folder at commit e5199b5. 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

    Ships 2 files in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • npm
    • git
    • python
    • pip
    • curl
    • docker

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • github.com

    Also links to:

    • docs.wardenprotocol.org
    • smith.langchain.com
    • clawhub.ai

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • OPENAI_API_KEY
    • LANGSMITH_API_KEY
    • WEATHER_API_KEY
    • COINGECKO_API_KEY
    • ALCHEMY_API_KEY

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Warden Agent Builder loads about 4.4k tokens when it runs, and up to ~15k if it reads all its reference files. Until then it costs about 118 tokens; SKILL.md has 1,511 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~118
When it runs · the whole SKILL.md, loaded when a task matches
~4.4k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~15k

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:213
    Create `.env` file:
  • NoteMentions a .env fileSKILL.md:232
    4. Add to `.env` file
  • NoteMentions a .env fileSKILL.md:244
    "env": ".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); the scripts in this folder are not scanned.

SKILL.md

The full file from LeoYeAI/openclaw-master-skills at commit e5199b5, republished under its MIT licence (© LeoYeAI). 1,511 words, ~4,375 tokens.

Download SKILL.mdSave it as .claude/skills/warden-agent-builder/SKILL.md (or your agent's skills folder). This skill also uses 9 other files; get the full folder from GitHub.
name
warden-agent-builder
description
Build original LangGraph agents for Warden Protocol and prepare them for publishing in Warden Studio. Use this skill when users want to: (1) Create new Warden agents (not community examples), (2) Build LangGraph-based crypto/Web3 agents, (3) Deploy agents via LangSmith Deployments or custom infra, (4) Participate in the Warden Agent Builder Incentive Programme (open to OpenClaw agents), or (5) Integrate with Warden Studio for Agent Hub publishing.

Warden Agent Builder

Build and deploy LangGraph agents for Warden Protocol's Agentic Wallet ecosystem.

⚠️ IMPORTANT: About Example Agents

The Warden community repository contains example agents for learning, not templates to recreate:

  • Weather Agent - Study this to learn simple data fetching patterns
  • CoinGecko Agent - Study this to learn Schema-Guided Reasoning (SGR)
  • Portfolio Agent - Study this to learn complex multi-source integration

DO NOT BUILD THESE AGENTS - they already exist. Instead:

  1. Study their code to understand patterns
  2. Learn from their architecture and workflows
  3. Build something NEW and original for the incentive programme

Your agent must be unique and solve a different problem to be eligible for the incentive programme.

Overview

Warden Protocol is an "Agentic Wallet for the Do-It-For-Me economy" with an active Agent Builder Incentive Programme open to OpenClaw agents that deploy to Warden. All agents must be LangGraph-based and API-accessible.

Key Resources:

Requirements Checklist

Before building, ensure your agent meets these mandatory requirements:

✓ Framework: Built with LangGraph (TypeScript or Python) ✓ Deployment: LangSmith Deployments OR custom infrastructure ✓ Access: API-accessible (no UI required - Warden provides UI) ✓ Isolation: One agent per LangGraph instance ✓ Security Limitations (Phase 1):

  • Cannot access user wallets
  • Cannot store data on Warden infrastructure

✓ Functionality: Can implement any workflow:

  • Web3/Web2 automation
  • API integrations
  • Database connections
  • External tool interactions

Understanding the Example Agents

The community-agents repository contains reference examples to learn from, NOT templates to recreate:

Example Agent 1: LangGraph Quick Start (Study for Basics)

Location: agents/langgraph-quick-start (TypeScript) or agents/langgraph-quick-start-py (Python) Learn: LangGraph fundamentals, minimal agent structure Study: Single-node chatbot with OpenAI integration

bash
git clone https://github.com/warden-protocol/community-agents.git
cd community-agents/agents/langgraph-quick-start
Example Agent 2: Weather Agent (Study for Structure)

Location: agents/weather-agent Learn: Simple data fetching, API integration, user-friendly responses Study:

  • How to fetch data from external APIs (WeatherAPI)
  • Processing and formatting results
  • Clear scope and structure ⚠️ DO NOT BUILD: This already exists. Study it, then build something NEW.
Example Agent 3: CoinGecko Agent (Study for SGR Pattern)

Location: agents/coingecko-agent Learn: Schema-Guided Reasoning, complex workflows Study:

  • 5-step SGR workflow: Validate → Extract → Fetch → Validate → Analyze
  • Comparative analysis patterns
  • Error handling and data validation ⚠️ DO NOT BUILD: This already exists. Study the pattern, apply to new use cases.
Example Agent 4: Portfolio Analysis Agent (Study for Advanced Patterns)

Location: agents/portfolio-agent Learn: Multi-source data synthesis, production architecture Study:

  • Integrating multiple APIs (CoinGecko + Alchemy)
  • Multi-chain support (EVM and Solana)
  • Complex SGR workflows
  • Comprehensive reporting ⚠️ DO NOT BUILD: This already exists. Study the architecture for your own complex agent.

IMPORTANT: Build Something NEW

These examples exist to teach patterns and best practices. For the incentive programme, you MUST create an original, unique agent that solves a different problem. Do NOT simply recreate the Weather Agent, CoinGecko Agent, or Portfolio Agent.

Building Your Original Agent

Step 1: Study Examples and Choose Your Approach

DO NOT clone an example to modify it. Instead:

  1. Study the examples to understand patterns:

    • Simple data fetching → Study Weather Agent
    • Complex analysis → Study CoinGecko Agent
    • Multi-source synthesis → Study Portfolio Agent
  2. Identify YOUR unique use case:

    • What problem will your agent solve?
    • What APIs or data sources will it use?
    • What makes it different from existing agents?
  3. Plan your agent's workflow:

    • Simple request-response?
    • Schema-Guided Reasoning (SGR)?
    • Multi-step analysis?
Step 2: Initialize Your NEW Agent

Use the initialization script to create a fresh project:

bash
# Create your unique agent
python scripts/init-agent.py my-unique-agent \
  --template typescript \
  --description "Description of what YOUR agent does"

# Navigate to project
cd my-unique-agent

# Install dependencies
npm install  # TypeScript
# OR
pip install -r requirements.txt  # Python

This creates a clean starting point, not a copy of existing agents.

Step 3: Understand LangGraph Agent Structure

Every LangGraph agent follows this basic structure:

your-agent/
├── src/
│   ├── agent.ts/py          # Main agent logic (YOUR CODE)
│   ├── graph.ts/py          # LangGraph workflow definition (YOUR CODE)
│   └── tools.ts/py          # Tool implementations (YOUR CODE)
├── package.json / requirements.txt
├── langgraph.json           # LangGraph configuration
└── README.md

Key files to implement:

  • graph.ts/py - Define your workflow (validate → process → respond)
  • agent.ts/py - Implement your core logic
  • tools.ts/py - Integrate external APIs specific to YOUR agent's purpose
Step 4: Implement Your Custom Agent Logic

Study patterns from examples, apply to YOUR use case:

If building a simple data fetcher (like Weather Agent pattern):

typescript
// Define workflow
const workflow = new StateGraph({
  channels: agentState
})
  .addNode("fetch", fetchYourData)      // YOUR API
  .addNode("process", processYourData)  // YOUR logic
  .addNode("respond", generateResponse);

workflow
  .addEdge(START, "fetch")
  .addEdge("fetch", "process")
  .addEdge("process", "respond")
  .addEdge("respond", END);

If building complex analysis (like CoinGecko Agent pattern - SGR):

typescript
// Define 5-step SGR workflow
const workflow = new StateGraph({
  channels: agentState
})
  .addNode("validate", validateYourInput)     // YOUR validation
  .addNode("extract", extractYourParams)      // YOUR extraction
  .addNode("fetch", fetchYourData)            // YOUR APIs
  .addNode("analyze", analyzeYourData)        // YOUR analysis
  .addNode("generate", generateYourResponse); // YOUR formatting

workflow
  .addEdge(START, "validate")
  .addEdge("validate", "extract")
  .addEdge("extract", "fetch")
  .addEdge("fetch", "analyze")
  .addEdge("analyze", "generate")
  .addEdge("generate", END);

Key Principles:

  1. Keep workflows linear and predictable
  2. Validate inputs at each stage
  3. Handle errors gracefully
  4. Use OpenAI for natural language generation
  5. Structure responses consistently

CRITICAL: This should be YOUR implementation solving YOUR problem, not a copy of the example agents.

Step 5: Configure Environment

Create .env file:

bash
# Required
OPENAI_API_KEY=your_openai_key

# Required for LangSmith Deployments (cloud)
LANGSMITH_API_KEY=your_langsmith_key

# Optional - based on your tools
WEATHER_API_KEY=your_weather_key
COINGECKO_API_KEY=your_coingecko_key
ALCHEMY_API_KEY=your_alchemy_key

Getting LangSmith API Key:

  1. Create account at https://smith.langchain.com
  2. Navigate to Settings → API Keys
  3. Create new API key
  4. Add to .env file

Update langgraph.json:

json
{
  "agent_id": "[YOUR-AGENT-NAME]",
  "python_version": "3.11",  // or omit for TypeScript
  "dependencies": ["."],
  "graphs": {
    "agent": "./src/graph.ts"  // or .py
  },
  "env": ".env"
}
Step 6: Test Locally
bash
# TypeScript
npm run dev

# Python
langgraph dev

Test your agent's API:

bash
curl -X POST http://localhost:8000/invoke \
  -H "Content-Type: application/json" \
  -d '{"input": "test query"}'

Deployment Options

Pros: Fastest, simplest, managed infrastructure Requirements: LangSmith API key

Steps:

bash
1. Push your agent repository to GitHub.
2. Create a new deployment in LangSmith Deployments.
3. Connect the repo, set environment variables, and deploy.

Your agent receives:

  • API endpoint URL
  • Automatic authentication (uses your LangSmith API key)
  • Automatic scaling and monitoring

Authentication for API calls: When calling your deployed agent, include your LangSmith API key:

bash
curl AGENT_URL/runs/wait \
  --request POST \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: [YOUR-LANGSMITH-API-KEY]' \
  --data '{
    "assistant_id": "[YOUR-AGENT-ID]",
    "input": {
      "messages": [{"role": "user", "content": "test query"}]
    }
  }'
Option 2: Self-Hosted Infrastructure

Pros: Full control over runtime Requirements:

  • Docker container hosting
  • Exposed API endpoint
  • SSL certificate (HTTPS)
  • Monitoring and logging

Basic Docker Setup:

dockerfile
FROM node:18
WORKDIR /app
COPY package*.json ./
RUN npm install
COPY . .
EXPOSE 8000
CMD ["npm", "start"]

Deploy and note your:

  • API URL: https://your-domain.com/agent
  • API Key: Generated for authentication

Register with Warden Studio

Once your agent is deployed and reachable via HTTPS, register it in Warden Studio:

  1. Provide API Details:

    • API URL
    • API key
  2. Add Metadata:

    • Agent name
    • Description
    • Skills/capabilities list
    • Avatar image
  3. Publish: Agent appears in Warden's Agent Hub for millions of users

No additional setup required - your API-accessible agent is ready!

Next step (separate skill): If the user asks to publish in Warden Studio or needs guided UI steps, switch to the OpenClaw skill "Deploy Agent on Warden Studio": https://www.clawhub.ai/Kryptopaid/warden-studio-deploy

Best Practices

1. Agent Design
  • Study the Weather Agent structure to learn patterns
  • Use Schema-Guided Reasoning for complex workflows
  • Keep responses concise and actionable
  • Handle API failures gracefully
  • Validate all inputs
Show full SKILL.md (591 more words)Show less
2. API Integration
  • Use environment variables for API keys
  • Implement rate limiting
  • Cache responses when appropriate
  • Log errors for debugging
  • Return structured JSON responses
3. Testing
  • Test locally before deploying
  • Verify all API endpoints work
  • Test edge cases and errors
  • Ensure responses are user-friendly
  • Validate against Warden requirements
4. Documentation
  • Write clear README with:
    • Agent purpose and capabilities
    • Required API keys
    • Setup instructions
    • Example queries
    • Known limitations

Common Patterns

Pattern 1: Simple Data Fetcher
typescript
// Fetch → Format → Respond
async function agent(input: string) {
  const data = await fetchAPI(input);
  const formatted = formatData(data);
  return generateResponse(formatted);
}
Pattern 2: Multi-Step Analysis
typescript
// Validate → Extract → Fetch → Analyze → Generate
async function agent(input: string) {
  const validated = await validateInput(input);
  const params = await extractParams(validated);
  const data = await fetchData(params);
  const analysis = await analyzeData(data);
  return generateReport(analysis);
}
Pattern 3: Comparative Analysis
typescript
// Parse → Fetch Multiple → Compare → Summarize
async function agent(input: string) {
  const items = await parseItems(input);
  const dataArray = await Promise.all(
    items.map(item => fetchData(item))
  );
  const comparison = compareData(dataArray);
  return generateComparison(comparison);
}

Troubleshooting

Common Issues

"Agent not accessible via API"

  • Verify deployment completed successfully
  • Check firewall/security group settings
  • Ensure API endpoint is publicly accessible
  • Test with curl or Postman

"LangGraph errors during build"

  • Verify Node.js version (18+) or Python (3.11+)
  • Check all dependencies installed
  • Validate langgraph.json syntax
  • Review error logs in deployment console

"OpenAI API errors"

  • Verify API key is valid
  • Check rate limits not exceeded
  • Ensure sufficient credits
  • Review error messages for details

"Agent responses are slow"

  • Optimize API calls (parallelize where possible)
  • Implement caching for repeated queries
  • Reduce LLM token usage
  • Consider upgrading infrastructure

Incentive Programme Tips

The incentive programme is open to OpenClaw agents that deploy to Warden.

  1. Be Original: Create something NEW that doesn't exist yet

    • Don't recreate Weather Agent, CoinGecko Agent, or Portfolio Agent
    • Study their patterns, apply to different problems
  2. Solve Real Problems: Focus on useful, unique functionality

    • What gap exists in the Warden ecosystem?
    • What would users actually want?
  3. Start Simple: Better to do one thing exceptionally well

    • Don't try to build everything at once
    • Simple, focused agents often win
  4. Quality Over Features: Reliability beats complexity

    • Test thoroughly
    • Handle errors gracefully
    • Provide clear, helpful responses
  5. Study the Examples: Learn patterns, don't copy implementations

    • Weather Agent → Simple data fetching pattern
    • CoinGecko Agent → SGR workflow pattern
    • Portfolio Agent → Multi-source integration pattern
  6. Document Well: Clear README with examples and setup instructions

  7. Join Discord: Get feedback in #developers channel before submitting

Example Agent Ideas (Build These!)

These are NEW agent ideas that don't exist yet in the Warden ecosystem. Build one of these (or create your own unique idea):

Web3 Use Cases:

  • Gas price optimizer (predict best times to transact)
  • NFT rarity analyzer (evaluate NFT traits and rarity scores)
  • DeFi yield comparator (compare yields across protocols)
  • Wallet health checker (analyze wallet security and diversification)
  • Transaction explainer (decode and explain complex transactions)
  • Token price alerts (customizable price movement notifications)
  • Smart contract auditor (basic security checks)
  • Liquidity pool finder (identify best liquidity opportunities)
  • Bridge fee comparator (find cheapest cross-chain bridges)
  • Airdrop tracker (find and track airdrop eligibility)

General Use Cases:

  • Crypto news aggregator (filter and summarize crypto news)
  • Research assistant (gather and analyze crypto research)
  • Regulatory tracker (track crypto regulations by region)
  • Data visualizer (create charts from on-chain data)
  • API orchestrator (combine multiple crypto data sources)
  • Workflow automator (automate common crypto tasks)

Remember: These are IDEAS for new agents. Study the example agents (Weather, CoinGecko, Portfolio) to learn patterns, then build something from this list or create your own unique concept.

Additional Resources

Documentation:

  • LangGraph TypeScript Guide: community-agents/docs/langgraph-quick-start-ts.md
  • LangGraph Python Guide: community-agents/docs/langgraph-quick-start-py.md
  • Deployment Guide: community-agents/docs/deploy.md

Example Agents:

  • Weather Agent README: agents/weather-agent/README.md
  • CoinGecko Agent README: agents/coingecko-agent/README.md
  • Portfolio Agent README: agents/portfolio-agent/README.md

Support:

Quick Reference Commands

bash
# Study example agents (DON'T BUILD THESE)
git clone https://github.com/warden-protocol/community-agents.git
cd community-agents/agents/weather-agent  # Study the code
cd community-agents/agents/coingecko-agent  # Study the patterns

# Create YOUR new agent
python scripts/init-agent.py my-unique-agent \
  --template typescript \
  --description "YOUR unique agent description"

# Install dependencies (TypeScript)
npm install

# Install dependencies (Python)
pip install -r requirements.txt

# Test locally
npm run dev  # or: langgraph dev

# Deploy (LangSmith Deployments)
# Use the LangSmith Deployments UI after pushing to GitHub

# Build Docker image (for self-hosting)
docker build -t my-warden-agent .

# Run Docker container
docker run -p 8000:8000 my-warden-agent

Success Checklist

Before submitting to incentive programme:

  • Agent built with LangGraph
  • API accessible and tested
  • One agent per LangGraph instance
  • No wallet access or data storage (Phase 1)
  • Clear documentation in README
  • Environment variables properly configured
  • Error handling implemented
  • Tested with various inputs
  • Unique and useful functionality
  • Ready for Warden Studio registration

© LeoYeAI, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 9 other files (scripts, references, assets) in skills/lex of LeoYeAI/openclaw-master-skills.

  • SKILL.md
  • README.md
  • _meta.json
  • assets/example-configs.md
  • references/deployment-guide.md
  • references/installation-guide.md
  • references/langgraph-patterns.md
  • references/quick-reference.md
  • scripts/init-agent.py
  • scripts/test-agent.py

Open the folder on GitHubat commit e5199b5

Compare with similar skills

Warden Agent Builder 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.

Warden Agent Builder compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Warden Agent Builder this skillLeoYeAI/openclaw-master-skills2.2k—~4.4kAutomated safety check: NotesMIT
LangSmith Trace DebuggingComposioHQ/awesome-claude-skills77k8 repos~2.7kAutomated safety check: PassNone
LangGraph Decision Modelslangchain-ai/langchain-skills1.3k—~2.3kAutomated safety check: PassMIT
Docs Code Sampleslangchain-ai/docs426—~4.6kAutomated safety check: PassMIT
Deepagents Setup Configurationsoba-labs/langchain-agent-skills107—~1.9kAutomated safety check: PassMIT
Agentsop Observability Setupagentsope/SkillAlchemy466—~4.4kAutomated safety check: PassMIT

Similar skills

  • LangSmith Trace Debugging

    ComposioHQ/awesome-claude-skills

    Debugs LangChain and LangGraph agents by pulling recent execution traces with the langsmith-fetch CLI and reporting errors, tool calls, timings and token use.

    77k GitHub starsUsed in 8 repos~2.7k tokens
    AI & LLM EngineeringAuto-check passed
  • LangGraph Decision Models

    langchain-ai/langchain-skills

    Official

    Routes LangGraph agents with typed decision models that return probabilities, and finds LLM calls that only exist to produce a routing decision.

    1.3k GitHub stars~2.3k tokensUpdated yesterday
    AI & LLM EngineeringAuto-check passed
  • Docs Code Samples

    langchain-ai/docs

    Official

    A skill your agent uses when migrating inline code samples from LangChain docs (MDX files) into external, testable code files that are extracted by this repo’s snippet scripts and used as Mintlify…

    426 GitHub stars~4.6k tokensUpdated today
    AI & LLM EngineeringAuto-check passed
  • Deepagents Setup Configuration

    soba-labs/langchain-agent-skills

    Initialize, validate, and troubleshoot Deep Agents projects in Python or JavaScript using the deepagents package.

    107 GitHub stars~1.9k tokensUpdated 1 mo ago
    AI & LLM EngineeringAuto-check passed
  • Agentsop Observability Setup

    agentsope/SkillAlchemy

    Enhancement-overlay skill — the DECISION + WIRING layer for LM observability that the single-backend skills [[langsmith]], [[phoenix]], [[mlflow]] do NOT cover.

    466 GitHub stars~4.4k tokensUpdated today
    AI & LLM EngineeringAuto-check passed
  • LangChain Ecosystem Primer

    langchain-ai/langchain-skills

    Official

    Starting point for LangChain, LangGraph and Deep Agents projects: picks the right layer for the task, then points to install steps, setup and the next skill to load.

    1.3k GitHub stars~2k tokensUpdated yesterday
    AI & LLM EngineeringAuto-check passed

More from LeoYeAI/openclaw-master-skills

All 1,235 skills in this repo
  • DevOps Pipeline Management

    LeoYeAI/openclaw-master-skills

    Manages pipelines on a DevOps quality and efficiency platform through its OpenAPI: list workspaces and templates, create, update, run and cancel pipelines, and read run records.

    2.2k GitHub stars~4.2k tokensUpdated 2 mo ago
    Auto-check: notes
  • Feishu Document Collaboration

    LeoYeAI/openclaw-master-skills

    Patches OpenClaw's Feishu extension so an edited document triggers an isolated agent session that reads the doc and replies inline, turning it into a live chat space.

    2.2k GitHub stars~2k tokensUpdated 2 mo ago
    Auto-check passed
  • Files Memory System

    LeoYeAI/openclaw-master-skills

    Multi-context memory management system for OpenClaw agents with group-isolated storage, global shared memory, workspace organization, and group-specific skills isolation.

    2.2k GitHub stars~3.8k tokensUpdated 2 mo ago
    Auto-check passed
  • GEO-Claw AI Visibility Agent

    LeoYeAI/openclaw-master-skills

    Runs a brand's AI-search visibility work end to end: diagnosing how AI platforms represent it, repositioning it, producing AI-optimized content and monitoring ongoing mentions.

    2.2k GitHub stars~4.7k tokensUpdated 2 mo ago
    Auto-check passed
  • Google Workspace CLI

    LeoYeAI/openclaw-master-skills

    Installs and authenticates the gws CLI, then automates Gmail, Drive, Sheets, Calendar, Docs, Chat and Tasks with ready-made recipes, persona bundles and security audits.

    2.2k GitHub stars~2.6k tokensUpdated 2 mo ago
    Auto-check: notes
  • HealthFit Health Advisors

    LeoYeAI/openclaw-master-skills

    Runs four advisor roles, a fitness coach, nutritionist, data analyst and TCM practitioner, to build a health profile and track workouts, diet and wellness over time.

    2.2k GitHub stars~4.4k tokensUpdated 2 mo ago
    Auto-check passed

Questions about Warden Agent Builder

What does Warden Agent Builder do?

Build original LangGraph agents for Warden Protocol and prepare them for publishing in Warden Studio. Warden Agent Builder is an agent skill from LeoYeAI/openclaw-master-skills. Build original LangGraph agents for Warden Protocol and prepare them for publishing in Warden Studio.

When should I use Warden Agent Builder?

Warden Agent Builder fits situations like: create new Warden agents (not community examples); build LangGraph-based crypto/Web3 agents; deploy agents via LangSmith Deployments; participate in the Warden Agent Builder Incentive Programme (open to OpenClaw agents).

How do I install Warden Agent Builder in Claude Code?

Run `npx skills add LeoYeAI/openclaw-master-skills --skill warden-agent-builder -a claude-code`. Or copy the skill folder (skills/lex in LeoYeAI/openclaw-master-skills) into .claude/skills/warden-agent-builder in your project. Claude Code loads it when a task matches its description.

How do I install Warden Agent Builder in Codex?

Run `npx skills add LeoYeAI/openclaw-master-skills --skill warden-agent-builder -a codex`. Or copy the skill folder (skills/lex in LeoYeAI/openclaw-master-skills) into .agents/skills/warden-agent-builder in your project. Codex loads it when a task matches its description.

Can I use Warden Agent Builder 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 LeoYeAI/openclaw-master-skills --skill warden-agent-builder -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/warden-agent-builder, .gemini/skills/warden-agent-builder, .github/skills/warden-agent-builder and .opencode/skills/warden-agent-builder in your project.

What does Warden Agent Builder need to run?

Going by SKILL.md and its folder, Warden Agent Builder needs Python for the scripts in its folder, the command-line tools its instructions call (npm, git, python, pip, curl and docker) and credentials named OPENAI_API_KEY, LANGSMITH_API_KEY, WEATHER_API_KEY and COINGECKO_API_KEY. Our summary lists: Python 3; Node.js; Docker; A credential in OPENAI_API_KEY; A credential in LANGSMITH_API_KEY.

Does Warden Agent Builder access the network?

SKILL.md names 4 domains. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. As links in the text: docs.wardenprotocol.org, smith.langchain.com and clawhub.ai. This is read from the text; nothing was executed.

Is Warden Agent Builder 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Warden Agent Builder use?

Warden Agent Builder 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 Warden Agent Builder use?

About 4.4k tokens (SKILL.md is roughly 18k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 11k tokens, read only when the agent opens those files.

What are the alternatives to Warden Agent Builder?

Skills that share tags, products or a category with Warden Agent Builder: LangSmith Trace Debugging (ComposioHQ/awesome-claude-skills, 77k stars), LangGraph Decision Models (langchain-ai/langchain-skills, 1.3k stars), Docs Code Samples (langchain-ai/docs, 426 stars) and Deepagents Setup Configuration (soba-labs/langchain-agent-skills, 107 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Warden Agent Builder?

LeoYeAI (a GitHub user) maintains it in LeoYeAI/openclaw-master-skills, which has 2,160 GitHub stars. The repository holds 1,235 skills in this directory. The repository was last updated on July 20, 2026.

Source: LeoYeAI/openclaw-master-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.