add-tools

Generate typed tool configurations for Sim integrations from service API documentation.

Updated Apr 16, 2026
One-click install
npx skills add https://github.com/tunacosgun/sim --skill add-tools-tunacosgun
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-tools
Source: https://github.com/tunacosgun/sim/tree/main/.agents/skills/add-tools
Command: npx skills add https://github.com/tunacosgun/sim --skill add-tools-tunacosgun

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically generate typed tool configurations for Sim integrations from service API documentation, turning docs into production-ready tooling.

Core Features & Use Cases

  • Generate a complete tools/{service}/ structure with index.ts, types.ts, and per-operation files.
  • Enforce explicit parameter types, visibility rules, and safe defaults to prevent guesswork.
  • Align tool definitions with the official ToolConfig pattern for consistent wiring into the UI.

Quick Start

Instruct the AI to generate tool definitions for a given service using its public API docs.

Frequently Asked Questions about add-tools

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

FAQPage Schema
How do I generate typed tool configurations for Sim integrations from API documentation?

Generating Sim tool configurations from API docs involves instructing the AI to create a tools/{service}/ structure with index.ts, types.ts, and per-operation files, enforcing strict output schemas and typed parameters for safe integration.

What is the ToolConfig pattern for Sim integrations and how does it handle type safety?

The ToolConfig pattern for Sim integrations enforces explicit parameter types, visibility rules, transformResponse mappings, and safe defaults to prevent guesswork, ensuring production-ready tooling and consistent UI wiring.

Do I need existing API documentation to automate Sim tool configuration?

Yes, existing service API documentation is required to automate Sim tool configuration. The process operates when documenting a new service or updating an integration, relying on official docs to avoid guesswork.

Can I update an existing Sim integration without losing my strict output schemas?

Yes, you can update existing Sim integrations while preserving strict output schemas. The automation creates per-operation files and typed parameters, avoiding guesswork and maintaining safe defaults during integration updates.

What's the best way to structure files when adding a new service to a Sim integration?

The best way to structure files for a new Sim service is the tools/{service}/ directory pattern, generating index.ts for exports, types.ts for definitions, and individual per-operation files for each API endpoint.