builtin-tool

Develop custom agent tools with manifests, types, and UI interfaces.

Updated Apr 3, 2026
One-click install
npx skills add https://github.com/1154761334/it-bidding-copilot --skill builtin-tool
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: builtin-tool
Source: https://github.com/1154761334/it-bidding-copilot/tree/main/frontend/.agents/skills/builtin-tool
Command: npx skills add https://github.com/1154761334/it-bidding-copilot --skill builtin-tool

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

This Skill provides a structured framework for developing tools that agents can directly invoke, streamlining the integration of custom functionalities.

Core Features & Use Cases

  • Tool Packaging: Build a self-contained package with manifest, types, and system prompt.
  • UI Surfaces: Implement inspector, render, placeholder, streaming, intervention, and portal interfaces.
  • Wiring & Registry: Register tools in central registry files to ensure discoverability and correct operation.

Quick Start

Use the built-in tool template to create new agent-callable functions, defining APIs, UI components, and runtime behavior for seamless integration.

Frequently Asked Questions about builtin-tool

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

FAQPage Schema
How do I create custom agent tools for direct invocation?

To create custom agent tools, use this framework to build a self-contained package with a manifest, types, and system prompt, ensuring seamless integration and discoverability across runtime interfaces.

What UI surfaces can I customize when developing agent-callable functions?

When developing agent-callable functions, you can implement inspector, render, placeholder, streaming, intervention, and portal UI interfaces to deliver rich user experiences and comprehensive UI customization.

How does a central registry file ensure tool discoverability?

A central registry file ensures tool discoverability by registering custom tools in central registry files, maintaining strict package and registry standards for scalable tool management and correct operation.

How do I maintain consistency across system prompts and API schemas for agent tools?

Maintain consistency across system prompts and API schemas by adhering to the framework's strict package and registry standards, which align API definitions, UI components, and runtime behavior for seamless integration.

Do I need specific runtime interfaces to support agent tool integration?

Yes, supporting agent tool integration requires multiple runtime interfaces and UI surfaces, ensuring that the custom tool package operates correctly within the system prompt and API schema constraints.