coral-toml-format

Documents the coral-agent.toml Edition 3 schema for Coral Marketplace agent manifests.

1|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/Coral-Protocol/coral-skills --skill coral-toml-format
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coral-toml-format
Source: https://github.com/Coral-Protocol/coral-skills/tree/main/skills/coral-toml-format
Command: npx skills add https://github.com/Coral-Protocol/coral-skills --skill coral-toml-format

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a comprehensive guide and template for creating and validating coral-agent.toml files, ensuring agents are correctly formatted for the Coral Marketplace.

Core Features & Use Cases

  • TOML Schema Reference: Details all required and optional fields for coral-agent.toml (Edition 3).
  • Validation Rules: Explains specific requirements for slugs and versioning.
  • Use Case: When developing a new agent for the Coral Marketplace, use this Skill to ensure your coral-agent.toml file includes all necessary fields and adheres to the correct format before publishing.

Quick Start

Refer to the coral-toml-format skill for the complete template of a coral-agent.toml file.

Frequently Asked Questions about coral-toml-format

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

FAQPage Schema
What is a coral-agent.toml file and when do I need it?

A coral-agent.toml file is the manifest configuration required for publishing agents to the Coral Marketplace. You need it to define agent execution parameters, display settings, and metadata before submission.

How do I format a valid agent manifest for the Coral Marketplace?

To format a valid agent manifest, use the coral-agent.toml Edition 3 schema, including all mandatory fields, valid slugs, and correct versioning standards to pass marketplace validation before publishing.

What validation rules apply to slugs and versioning in TOML agent manifests?

Slug and versioning validation rules require specific formatting standards for the coral-agent.toml file. Slugs must meet naming constraints and versions must adhere to established standards to ensure marketplace compatibility.

What are the mandatory and optional fields in a coral-agent.toml configuration?

The coral-agent.toml configuration includes mandatory fields required for marketplace publishing and optional parameters for agent execution and display settings. The schema reference details all available configuration options.

Can I use custom configuration options for agent execution in the TOML manifest?

Yes, the coral-agent.toml format supports optional configuration options for agent execution and display. These parameters allow customization of agent behavior while maintaining marketplace submission compliance.

Why does my agent manifest fail validation before Coral Marketplace publishing?

Agent manifest validation fails when the coral-agent.toml file is missing mandatory fields, contains invalid slugs, or uses incorrect versioning. Ensure all fields adhere to the Edition 3 schema reference.