Skill Detail

Format and lint TOML configuration with Tombi

Run Tombi as a TOML formatter, linter, and language server so agents can clean and validate pyproject, Cargo, and other TOML config files before committing changes.

Code Quality & ReviewMulti-Framework
Code Quality & Review Multi-Framework Security Reviewed
⭐ 937 GitHub stars ⬇ 4.5k/wk npm
COPY SKILL INSTRUCTIONS (OPTIONAL)
npx skills add agentskillexchange/skills --skill format-and-lint-toml-configuration-with-tombi Copy
Uses the third-party skills CLI, not an ASE-owned installer. Check your agent’s compatibility. This copies instructions; complete the upstream tool setup below separately.
At a glance
Tools required
Tombi CLI or language server, TOML files, optional npm, PyPI, uvx, Homebrew, VS Code, JetBrains, Zed, or Open VSX integration
Install & setup
For a quick CLI run, use uvx tombi format as shown in the upstream README, or install the tombi package through npm, PyPI, Homebrew, or the documented editor extensions.
Author
tombi-toml
Publisher
Open Source Project
Last updated
May 21, 2026
Quick brief

Use Tombi when an agent edits TOML configuration and needs syntax-aware formatting, linting, or language-server feedback before handing changes back. The operator runs Tombi through uvx, npm, Homebrew, PyPI, or editor integration to format and validate TOML files, then reviews the resulting diff or diagnostics. Keep the scope to TOML quality gates and config maintenance, not a broad developer tooling listing.

How it works

What this skill actually does

Inputs and prerequisites: Tombi CLI or language server, TOML files, optional npm, PyPI, uvx, Homebrew, VS Code, JetBrains, Zed, or Open VSX integration.

Setup notes: For a quick CLI run, use uvx tombi format as shown in the upstream README, or install the tombi package through npm, PyPI, Homebrew, or the documented editor extensions.

Source and verification boundary: use http://tombi-toml.github.io/tombi/ as the canonical reference before running the workflow; keep commands, API calls, CLI usage, and generated outputs reviewable against that upstream source.

Framework fit: publish this as a Multi-Framework workflow only when the operator can invoke the documented toolchain directly, rather than treating the upstream project as a generic product listing.