CruxExperts/LocalSetup / ls/skills/ls-kilo-visual-output
ls-kilo-visual-output
VerifiedKilo CLI visual output organization guide. Defines structured, readable response patterns for questions, options, preferred choices, rationale blocks, and execution summaries without relying on unsupported inline color control.
ls-kilo-visual-output
When to use
Use this skill when the user asks for:
- clearer or more visual Kilo CLI output,
- better readability for decision trees,
- distinction between question/options/preferred/rationale,
- response templates for planning or execution reports.
Important constraints
- Do not assume per-message or inline text color control is available in Kilo CLI.
- Do not rely on ANSI escape sequences for critical meaning.
- Use semantic structure (labels, headings, spacing) as the primary readability method.
- Mention
/themesonly as a global user-side appearance control.
Default formatting profile
- Mode:
markdown-basic - Structure: short headings + explicit labels
- Labels to use:
Question:Options:Preferred:Rationale:Your reply:
Decision tree response template
Use exactly one question per turn.
### Decision X/N - <topic>
**Question:** <single question>
A. <option A>
B. <option B>
C. <option C>
D. <option D>
**Preferred:** <A|B|C|D>
**Rationale:** <one concise paragraph>
**Your reply:** Choose A/B/C/D (or provide a custom answer).
Execution summary template
### Execution summary
- Status: <Success|Partial|Failed>
- Scope: <what was processed>
- Updated: <count or list>
- Skipped: <count or list>
- Errors: <none or short list>
### Next actions
1. <action 1>
2. <action 2>
Plain-text fallback template
[Decision X/N] <topic>
----------------------
Question: <single question>
A) <option A>
B) <option B>
C) <option C>
D) <option D>
Preferred: <A|B|C|D>
Rationale: <one concise paragraph>
Your reply: Choose A/B/C/D or provide custom input.
Practical guidance for agents
- Keep lines compact; avoid large dense paragraphs.
- Use one block per decision/question.
- Keep rationale to one concise paragraph unless user asks for detail.
- Use tables only if known renderer support is good.
- Never encode important meaning with color alone.
Embedded templates
This skill is self-contained. Use the templates above as the source examples for Kilo CLI output; if future references/ or templates/ files are added, link them here with paths relative to this skill directory.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |