Results for “build-tool”

Build, register, and gate AI-callable tool endpoints using the OpenSea Tool Registry (ERC-8257) on Base. Scaffold HTTPS tools with JSON Schema interfaces, register them onchain, gate access via NFT ownership or x402 pay-per-call (USDC), and call gated tools.

Vite build tool configuration, plugin API, SSR, and Vite 8 Rolldown migration. Use when working with Vite projects, vite.config.ts, Vite plugins, or building libraries/SSR apps with Vite.

Provides expert guidance for using n8n-mcp MCP server tools to build, validate, and manage n8n workflows efficiently.

Configure Vapi server URLs and webhooks to receive real-time call events, transcripts, tool calls, and end-of-call reports. Use when setting up webhook endpoints, building tool servers, or integrating Vapi events into your application.

Build production-quality Model Context Protocol (MCP) servers in C#/.NET using the official 1.x NuGet packages, covering transports, tools, prompts, resources, and common pitfalls.

Guides the creation of high-quality MCP servers that enable LLMs to interact with external services through well-designed tools, covering planning, implementation, and refinement for Python or Node/TypeScript.

Build voice AI agents with natural conversations, multiple LLM providers, custom tools, and easy web embedding.

Automate Fillout form operations including forms, submissions, workflows, and form builder via Composio's Fillout toolkit through Rube MCP.

Build, debug, and extend MCP servers and clients that connect AI systems with external tools and data sources.

This skill should be used when building token launch tools, implementing Clanker integration, or adding fee claiming functionality. Covers ERC20 deployment, metadata updates, and trading fees.

Routes n8n workflow-building tasks to the correct skill, with defaults and red-flag guidance for reliable n8n automation.

Creates durable command-line tools from API docs, OpenAPI specs, SDKs, or existing scripts, installable as system commands for future use.

Use this skill when the user asks Codex to build an app, website, bot, SaaS, dashboard, automation, MVP, integration, or production feature.

Design and ship production-ready MCP servers from OpenAPI contracts instead of hand-written tool wrappers. Supports Python and TypeScript, schema validation, and safe evolution.

Add plugin tools, connect MCP servers, or chain existing tools in one script within the LaRuche agent environment.

Build AI applications on Microsoft Foundry using the Azure AI Projects Python SDK, including agent creation, tool integration, thread management, and evaluation.

Guides developers through building Dify plugins, covering the four plugin types, Beehive architecture, runtime modes, and the full development workflow from setup to packaging.

Build a composable CLI for Codex from API docs, an OpenAPI spec, existing curl examples, an SDK, a web app, an admin tool, or a local script. Use when the user wants Codex to create a command-line tool that can run from any repo, expose composable read/write commands, return stable JSON, manage auth, and pair with a companion skill.

Query NFT and token data, trade NFTs on Seaport, swap ERC20 tokens via DEX aggregator, configure wallet signing providers, and build/register/gate AI agent tools on Base.

Query NFT and token data, trade NFTs on Seaport, swap ERC20 tokens via DEX aggregator, configure wallet signing providers, and build/register/gate AI agent tools on Base.

Build applications that programmatically interact with GitHub Copilot using the Copilot SDK, supporting session management, custom tools, streaming, hooks, MCP servers, and deployment across Node.js, Python, Go, and .NET.

Search reference implementations and code examples from Adobe's Block Collection and community Block Party for AEM Edge Delivery blocks, plugins, and build tools.

Migrate Slack bots to Microsoft Teams, build dual-platform bots, and convert between Block Kit and Adaptive Cards using a routed expert system with 100+ micro-expert files.

Build, validate, and troubleshoot deep links for Codex, Cursor, VS Code, Visual Studio, and similar tools. Use when users ask for clickable links (especially in Slack) that open threads, files, folders, or app settings.

Connects an AI agent to a FlowStudio MCP server for Power Automate, handling authentication, tool discovery, and response parsing. Load this foundation skill before using specialized workflow skills for building, debugging, monitoring, or governing flows.

USB and CAN connectivity for Zephyr RTOS. Covers USB device stack configuration (CDC ACM, HID, MSC), CAN controller integration, and professional USB-to-CAN adapter patterns including buffering and protocol packetization. Trigger when adding USB interfaces, implementing CAN bus communication, or building hardware diagnostic tools.

Build applications that programmatically interact with GitHub Copilot using an SDK that wraps the Copilot CLI via JSON-RPC, providing session management, custom tools, hooks, MCP server integration, and streaming across Node.js, Python, Go, and .NET.

Use a live Jupyter kernel for stateful, iterative Python execution via hamelnb. Load this skill when the task involves exploration, iteration, or inspecting intermediate results — data science, ML experimentation, API exploration, or building up complex code step-by-step. Uses terminal to run CLI commands against a live Jupyter kernel. No new tools required.

Greenfield development path for products, tools, and systems that do not yet exist. G Stack validates the idea before anything is planned or built. Use when starting from zero: no existing codebase, no existing schema, no existing API that this extends. AUTO-FIRE immediately when the user says any of: - "new development", "/new-development [description]" - "I have an idea for [X]", "I want to build [X] from scratch" - "new product", "new tool", "new platform", "new application" - "build [X] — it doesn't exist yet", "start a new project" Do NOT use when an existing codebase already exists for the work — use /full-development for large brownfield work. If unsure: ask "Does any part of this already exist in code?" If yes → /full-development. This is the most token-intensive command. Use it when the investment is justified by the scope of what is being built.