builtin-tool

Automate creation and integration of builtin tool packages for the agent runtime.

Updated May 11, 2026

Search Tags:#manifest #i18n #builtin-tool #execution-runtime #tool-authoring #frontend-executor #registry-wiring

Ready to run

npx skills add https://github.com/zmh13928433602-sys/lobe-chat --skill builtin-tool-zmh13928433602-sys

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: builtin-tool
Source: https://github.com/zmh13928433602-sys/lobe-chat/tree/main/.agents/skills/builtin-tool
Command: npx skills add https://github.com/zmh13928433602-sys/lobe-chat --skill builtin-tool-zmh13928433602-sys

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a standardized workflow for creating, describing, and wiring a new builtin tool package for the agent runtime. It ensures a consistent structure across manifest, API surface, runtime, UI surfaces, and registry integration, reducing duplication and onboarding time.

Core Features & Use Cases

API surface design: define manifest.ts, types.ts, and system prompt to govern tool behavior and safety.
Runtime and wiring: implement an ExecutionRuntime and an Executor that connects to frontend surfaces and registries.
UI surfaces: build or wire Inspector, Render, Placeholder, Streaming, Intervention, and Portal components for rich tool experiences.
Registry integration: register tool components with central registries to enable discovery and usage in agents.

Quick Start

Create a new builtin-tool package under packages/builtin-tool-<name>, implement its manifest, types, ExecutionRuntime, Executor, and client surfaces, then wire it into the registries.

Frequently Asked Questions about builtin-tool

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

FAQPage Schema

How do I create a new builtin tool package for an agent runtime?▼

To create a builtin tool package, define its manifest and types, implement the ExecutionRuntime and Executor, build UI surfaces like Inspector and Render, then wire the tool components into central registries.

What is the required folder structure for agent builtin tool authoring?▼

Builtin tool authoring enforces a specific folder structure under packages/builtin-tool-<name>, applying required JSON schemas, i18n hooks, and registry wiring patterns to ensure production-grade tool integration.

How do I design the API surface and manifest for an agent tool?▼

Design the API surface by defining manifest.ts, types.ts, and the system prompt to govern tool behavior and safety, specifying ApiName, Params, and State for the execution runtime.

What UI components do I need to build for a builtin tool execution runtime?▼

You need to build or wire Inspector, Render, Placeholder, Streaming, Intervention, and Portal UI components to connect the frontend executor and deliver rich tool experiences.

How do I wire a custom tool into central registries for agent discovery?▼

Wire a custom tool into central registries by registering its tool components during the integration phase, enabling the tool's discovery and usage by agents within the execution runtime.

Does builtin tool authoring support i18n hooks for system prompts?▼

Yes, builtin tool authoring enforces i18n hooks within the required folder structure and JSON schemas, ensuring the manifest and system prompt support internationalization across the agent runtime.