agent-format_skill

This skill formats agent messages for chat apps using status indicators, progress bars, and sparklines to maximize scannability.
  • Python

2.5k

GitHub Stars

2

Bundled Files

2 months ago

Catalog Refreshed

3 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill agent-format

  • _meta.json276 B
  • SKILL.md1.5 KB

Overview

This skill defines a standard formatting system for agent messages intended to be scannable across chat apps like Telegram, Discord, Slack, and WhatsApp. It provides status indicators, progress bars, sparklines, and monospace table patterns to create a consistent visual hierarchy. The baseline improves readability and speeds up decision-making in threaded or fast-moving conversations.

How this skill works

The skill prescribes a set of symbols and micro-patterns agents use when reporting status, progress, and trends. Agents prepend concise signals (emoji) for immediate context, include compact progress bars or sparklines for quantitative cues, and use monospace tables or simple dividers for structured details. Messages are intentionally short and ordered from most important to least important so they are easy to scan on mobile and desktop chat clients.

When to use it

  • Status updates where recipients need a fast, at-a-glance understanding
  • Progress reporting for tasks, sprints, or deployment steps
  • Incident triage to surface severity and next steps quickly
  • Standups or weekly summaries to compress information into compact blocks
  • Automated agent replies that must be readable on multiple chat platforms

Best practices

  • Lead with the highest signal first (status emoji or headline) before details
  • Keep each bullet or line short; assume scanning rather than deep reading
  • Use the defined emoji set for consistency: ๐ŸŸข ๐ŸŸก ๐Ÿ”ด ๐Ÿ”ฅ โšก
  • Prefer monospace blocks for tables and progress bars so alignment holds
  • Reserve detailed explanations for linked resources, not the main message

Example use cases

  • A CI bot posts build status: ๐Ÿ”ด Blocked โ€ข Tests failing โ€ข Owner: CI
  • Daily standup summary with progress bars and sparkline of weekly velocity
  • Incident alert showing severity emoji, short impact note, and next step
  • Release announcement listing features as Done with checkmarks and owners
  • Backup or archive report showing completion percentage with a progress bar

FAQ

Use โ–ˆ for filled and โ–‘ for empty in progress bars; use โ–โ–‚โ–ƒโ–„โ–…โ–†โ–‡โ–ˆ for sparklines.

How many status levels should I use?

Stick to five compact signals: green (done), yellow (in progress/warning), red (blocked/error), fire (urgent), and lightning (quick).

Built by
VeilStrat
AI signals for GTM teams
ยฉ 2026 VeilStrat. All rights reserved.All systems operational
agent-format skill by openclaw/skills | VeilStrat