agent-builder

Orchestrate OpenClaw agent chat sessions and tool invocations for DenchClaw apps.

1|1|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/putrawitama/DenchClaw --skill agent-builder-putrawitama
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-builder
Source: https://github.com/putrawitama/DenchClaw/tree/main/skills/app-builder/agent-builder
Command: npx skills add https://github.com/putrawitama/DenchClaw --skill agent-builder-putrawitama

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables developers to build AI-powered DenchClaw apps that can interface with the OpenClaw agent, manage chat sessions, invoke tools, and access agent memory within a cohesive app workflow.

Core Features & Use Cases

  • Chat-enabled apps: create and manage conversations with the agent, stream responses, and handle tool calls in real time.
  • App-as-Tool: expose your application's tools to the agent for dynamic, in-context automation.
  • Memory and gateway support: read memory, interact with gateway protocols, and maintain state across sessions.

Quick Start

Create an agent-enabled app and start a chat session with the OpenClaw agent.

Frequently Asked Questions about agent-builder

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build AI-powered apps that chat with an agent and stream responses?

You can build chat-enabled apps by interfacing with the OpenClaw agent to create chat sessions, stream responses in real time, and handle tool calls dynamically within your application workflow.

How does tool invocation work when exposing my app's tools to an AI agent?

Tool invocation works by exposing your application's tools to the OpenClaw agent, allowing it to execute those tools dynamically for in-context automation during an active chat session.

Can I access and maintain agent memory across multiple interactive chat sessions?

Yes, you can read agent memory and maintain state across interactive sessions by using the app API surface and gateway compatibility to access and preserve memory data.

Do I need gateway compatibility to orchestrate chat sessions and tool execution?

Yes, gateway compatibility is required to support streaming responses, tool execution, and memory access when interfacing with the OpenClaw agent to orchestrate chat sessions.

What is the best way to integrate app API surfaces for chat, tools, and memory access?

The best way is to use the app API surface to interface directly with the OpenClaw agent, enabling your app to orchestrate chat sessions, expose tools, and access memory within a cohesive workflow.

Why does my app need to expose tools to the agent for in-context automation?

Exposing tools to the agent allows your application to function as a dynamic tool, enabling the OpenClaw agent to perform in-context automation and execute tasks based on real-time chat interactions.