tab-configs

Define canonical Warp tab config TOML schemas with validation rules.

37|1|Updated Apr 28, 2026
One-click install
npx skills add https://github.com/terzigolu/warp-lite --skill tab-configs-terzigolu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tab-configs
Source: https://github.com/terzigolu/warp-lite/tree/main/resources/bundled/skills/tab-configs
Command: npx skills add https://github.com/terzigolu/warp-lite --skill tab-configs-terzigolu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The tab-configs skill provides a canonical reference for Warp tab config TOML files and clarifies the schema, validation rules, and examples needed to create or update tab configurations across builds.

Core Features & Use Cases

  • Canonical schema reference for Warp tab configs.
  • Guidance on location and naming conventions across stable and channel builds.
  • Validation rules and examples to avoid misconfigurations.

Quick Start

Create or edit a Warp tab_config TOML file using the canonical schema described in this skill.

Frequently Asked Questions about tab-configs

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

FAQPage Schema
How do I create a valid Warp tab config TOML file?

To create a Warp tab config TOML file, define a top-level name and a set of [[panes]] definitions with proper splits and leaf nodes following the canonical schema validation rules.

What schema validation rules apply to Warp tab configurations?

Warp tab configurations require a top-level name and valid [[panes]] definitions with proper splits and leaf nodes. The canonical schema enforces these validation rules to prevent misconfigurations.

Where should Warp tab config files be located for channel-specific builds?

Warp tab config files follow specific location and naming conventions across standard and channel-specific data directories to ensure builds load the correct configuration.

What are the required fields in a Warp tab configuration schema?

The required fields in a Warp tab configuration schema are a top-level name and a set of [[panes]] definitions. These panes must include proper splits and leaf nodes to pass validation.

How do I fix misconfigured Warp tab configs that fail validation?

To fix misconfigured Warp tab configs, apply the canonical schema reference to validate your top-level name and [[panes]] definitions, ensuring splits and leaf nodes meet the documented rules.

Do I need tab-configs to manage Warp pane splits and layouts?

Yes, tab-configs provides the canonical TOML schema reference needed to define pane splits, leaf nodes, and layouts correctly when creating or updating Warp tab configurations.