tml

Convert OpenAPI specs into token-efficient TML and .min formats.

8|2|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/maf404/tml --skill tml
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tml
Source: https://github.com/maf404/tml/tree/main
Command: npx skills add https://github.com/maf404/tml --skill tml

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of verbose API schemas wasting tokens and confusing AI agents. Traditional formats like OpenAPI JSON use excessive tokens and reduce tool selection accuracy, making it expensive and unreliable for agents to discover and call APIs.

Core Features & Use Cases

  • TML Source Format: Human-readable, editable tool definitions with intent descriptions, auth declarations, and structured parameters.
  • .min Index Format: Ultra-compiled, token-optimized one-line-per-tool format that agents can parse instantly.
  • OpenAPI Conversion: Automatically compile existing OpenAPI specs into TML and .min formats.
  • Use Case: A developer building an AI agent that needs to call the GitHub API can convert the OpenAPI spec to a .min file, reducing token usage from 1047 to 243 tokens while maintaining 100% tool selection accuracy.

Quick Start

Use the tml skill to convert an OpenAPI spec into a .min tool registry file for AI agents.

Frequently Asked Questions about tml

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

FAQPage Schema
How do I reduce OpenAPI token usage for LLM agents?

You can reduce OpenAPI token usage for LLM agents by compiling verbose JSON schemas into a token-efficient .min format. This conversion significantly cuts token consumption while maintaining 100% tool selection accuracy for agent registries.

Why does my AI agent fail to select the correct REST API tools?

AI agents fail to select correct REST API tools because traditional OpenAPI JSON formats use excessive tokens and confuse tool selection accuracy. Converting these verbose schemas into an ultra-compiled one-line-per-tool .min format enables instant parsing and reliable execution.

What is a token-efficient tool manifest format for AI agents?

A token-efficient tool manifest format for AI agents is a structured .min index that compiles API definitions into a one-line-per-tool representation. This allows agents to instantly parse tool intents, auth declarations, and parameters without wasting context window tokens.

Do I need Node.js to convert OpenAPI specs for AI agent consumption?

Yes, you need Node.js to convert OpenAPI specs for AI agent consumption using this tool. An Anthropic API key is also optionally required if you want to use the AI-assisted generation and benchmarking features during the schema compilation process.

Can I edit human-readable tool definitions before compiling an agent registry?

Yes, you can edit human-readable tool definitions in the TML source format before compiling an agent registry. This allows you to define intent descriptions, auth declarations, and structured parameters before generating the final ultra-compiled .min index file.

What is the best way to compile API schemas for an agent registry?

The best way to compile API schemas for an agent registry is to convert OpenAPI specs into a .min tool format. This process reduces token usage from over 1000 tokens to under 250 while preserving 100% tool selection accuracy for reliable AI agent execution.