creating-tools

Scaffold API tool integrations with Typer CLIs and secret configuration.

4|2|Updated Jun 10, 2026
One-click install
npx skills add https://github.com/useatrium/atrium --skill creating-tools
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: creating-tools
Source: https://github.com/useatrium/atrium/tree/main/centaur/.agents/skills/creating-tools
Command: npx skills add https://github.com/useatrium/atrium --skill creating-tools

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the guesswork and inconsistency involved in creating API clients and tool integrations, helping you add reliable, discoverable tools that follow the repository’s conventions.

Core Features & Use Cases

  • Tool Scaffolding: Creates the required package structure, metadata, client, CLI, environment template, and initialization files for a new integration.
  • API Client Implementation: Guides class-based clients, typed public methods, authentication, secret resolution, error handling, and client lifecycle management.
  • CLI and Registration: Builds Typer-based command-line interfaces with structured output options and explains how to document, reload, test, and deploy the tool.
  • Use Case: When integrating an external service such as a project tracker or analytics platform, use this Skill to create a production-ready client and standalone CLI that can be registered and tested by the tool manager.

Quick Start

Ask the creating-tools skill to scaffold and implement a new tool integration for the external service, including its API client, CLI, secrets configuration, documentation, and verification steps.

Frequently Asked Questions about creating-tools

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

FAQPage Schema
How do I scaffold a Python API client and Typer CLI for a new external service integration?

Scaffolding a Python API client and Typer CLI involves generating the required package structure, metadata, typed client methods, and initialization files for your external service. This creates a production-ready integration with structured output support and tool-manager registration.

What is the best way to manage secrets and authentication flows for API integration tools?

Managing secrets and authentication for API integration tools requires a prescribed environment template and shared secret handling configuration. This approach ensures secure secret resolution and proper client lifecycle management across your tool integrations.

How do I structure integration testing for a Python API client?

Integration testing for a Python API client requires following the prescribed package structure to implement verification steps and reload tests. This ensures your external service clients maintain reliability and consistency with repository conventions.

Does tool registration with a tool manager require structured output support in Typer CLIs?

Tool registration with a tool manager does require structured output support in your Typer CLIs. Building command-line interfaces with structured output options ensures your external service integrations are discoverable and testable within the repository.

When should I use a standalone Typer CLI instead of just a Python client for API integration?

Use a standalone Typer CLI when you need command-line access to an external service alongside the Python client. This approach provides structured output options and tool-manager metadata, making the API integration independently executable and easier to deploy.