cli-output

Standardize Tako CLI output across normal, verbose, and CI modes.

62|2|Updated Feb 10, 2026
One-click install
npx skills add https://github.com/lilienblum/tako --skill cli-output
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cli-output
Source: https://github.com/lilienblum/tako/tree/main/.agents/skills/cli-output
Command: npx skills add https://github.com/lilienblum/tako --skill cli-output

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Tako CLI output varies by mode, causing inconsistent user experiences and debugging challenges across normal, verbose, and CI runs.

Core Features & Use Cases

  • Defines consistent patterns for messages, spinners, prompts, logs, and error lines across modes.
  • Guides adoption and review of CLI text in tako/src/output.rs and tako/src/commands/.
  • Provides a repeatable Quick Start to validate output conformance in real tasks.

Quick Start

Run a standardization pass on a given Tako CLI command output to ensure consistency across normal, verbose, and CI modes.

Frequently Asked Questions about cli-output

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

FAQPage Schema
How do I standardize CLI output across normal, verbose, and CI modes?

To standardize CLI output across modes, apply consistent patterns for spinners, prompts, logs, and errors. This ensures a predictable user experience and simplifies debugging for normal, verbose, and CI runs in the tako crate.

What is the best way to format Tako CLI user-facing text and error messages?

The best way to format Tako CLI text is to trigger standardization changes on tako/src/output.rs and tako/src/commands/, ensuring all spinners, progress indicators, and error lines follow defined conformance patterns.

How do I validate CLI output conformance for Tako commands?

You validate CLI output conformance by running a standardization pass on a given Tako CLI command. This Quick Start task checks that output remains consistent across normal, verbose, and CI execution modes.

Why does Tako CLI output vary between interactive and CI runs?

Tako CLI output varies between modes because different environments handle spinners, prompts, and log lines differently. Standardizing output.rs patterns resolves these inconsistencies to ensure predictable logs.

Do I need to update SKILL.md frontmatter to standardize Tako CLI output?

Yes, you need to update SKILL.md frontmatter to define a name and description. This frontmatter triggers on changes to tako/src/output.rs, tako/src/commands/, or CLI user-facing text to apply standardization.