Get the FREE Ultimate OpenClaw Setup Guide →

ascii-cli-logo-banner

Scanned
npx machina-cli add skill partme-ai/full-stack-skills/ascii-cli-logo-banner --openclaw
Files (1)
SKILL.md
3.3 KB

When to use this skill

CRITICAL TRIGGER RULE

  • Use this skill ONLY when the user explicitly mentions the exact skill name: ascii-cli-logo-banner.

Use this skill when the user says they want:

  • A startup banner / logo / welcome screen for a CLI or service

Trigger phrases include:

  • "ascii-cli-logo-banner"
  • "use ascii-cli-logo-banner"
  • "用 ascii-cli-logo-banner"
  • "使用 ascii-cli-logo-banner 生成启动 Banner"
  • "用 ascii-cli-logo-banner 做一个 ASCII Logo"

Boundary

  • This skill is a routing/selection entry point. It does not provide its own generator implementation.
  • For built-in (no external font engine): use ascii-cli-logo-banner-python.
  • For TAAG/FIGlet style (FIGfont spec, smushing layouts): use ascii-cli-logo-banner-figletjs.

How to use this skill

Inputs (recommended)

  • brandName (required)
  • version (optional)
  • author (optional)
  • repoUrl / docsUrl (optional)
  • width (default 80)
  • slogan (optional, centered line under the logo)
  • hint (optional, centered line under the slogan)
  • glyph (ascii | block, default ascii)
  • center (default true)
  • rule (default true; set false for logo-only hero output)
  • style (block | outline | thin, default block)
  • colorMode (none | ansi256, default none; logo only in scripts)
  • includeCta (default true)

Outputs (required)

  • bannerPlain: ASCII-only full banner (logo area + info block + horizontal rule)
  • compactPlain: compact banner for width < 60 (single-line title + rule + 1-2 info lines)
  • plainTextFallback: no-color fallback when ANSI is enabled (same structure as bannerPlain)
  • embedNotes: 3-5 embedding notes (CLI start / service start / README / tickets)

Steps

  1. Decide width and fallback:
    • Default width=80
    • If width < 60, output compactPlain and skip the big-letter logo
  2. Generate an ASCII-only logo:
    • Avoid full-width characters and ambiguous-width Unicode
    • Ensure each line is <= width
  3. Compose the banner structure (recommended order):
    • Logo area (or a single-line title in compact mode)
    • Horizontal rule: exactly width characters (- or =)
    • Info block: Name / Version / Repo / Docs / Author (only include fields provided)
    • Optional CTA: e.g. Run: <command> or Docs: <url>
  4. Optional ANSI coloring (must not break alignment):
    • Colorize visible characters only; do not colorize spaces
    • Always provide plainTextFallback

Script (optional)

  • Use ascii-cli-logo-banner-python for the Python implementation.
  • Use ascii-cli-logo-banner-figletjs for the figlet.js/FIGfont implementation.

Examples

  • See examples in the two implementation skills:
    • ascii-cli-logo-banner-python/examples/*
    • ascii-cli-logo-banner-figletjs/examples/*

Quality checklist

  1. Does not wrap or misalign at 80 columns; no trailing spaces
  2. Copy-pastes cleanly into logs/email/tickets
  3. Never prints secrets (tokens, internal URLs, personal data)

Keywords

English: ascii, banner, logo, cli, terminal, startup, welcome, plain text, ansi, no-color 中文: ASCII, 启动横幅, 终端 Banner, CLI Logo, 欢迎页, 纯文本, ANSI 上色, 无色回退

Source

git clone https://github.com/partme-ai/full-stack-skills/blob/main/skills/ascii-cli-logo-banner/SKILL.mdView on GitHub

Overview

This skill acts as the entry point for ASCII CLI banners, routing to the appropriate generator based on needs. It does not render banners itself but selects either the Python builtin font implementation or the FIGlet/TAAG style implementation. Outputs defined include bannerPlain, compactPlain, plainTextFallback, and embedNotes to standardize integration.

How This Skill Works

When invoked, it determines which sub-skill to call: ascii-cli-logo-banner-python for built-in fonts or ascii-cli-logo-banner-figletjs for FIGlet/TAAG styles. It enforces inputs like brandName, width (default 80), and optional fields, producing bannerPlain, compactPlain (for width < 60), plainTextFallback, and embedNotes. It also outlines the width-driven behavior and ensures a non-colored fallback is available.

When to Use It

  • When you want a startup banner / logo / welcome screen for a CLI or service
  • When the user explicitly mentions the exact skill name: ascii-cli-logo-banner
  • When you need to choose between Python built-in font and FIGlet/TAAG styles
  • When you require outputs: bannerPlain, compactPlain, plainTextFallback, and embedNotes
  • When you want a width-based flow that can skip the big-logo in compact mode

Quick Start

  1. Step 1: Decide width (default 80); if width < 60, plan for compactPlain
  2. Step 2: Choose the generator: ascii-cli-logo-banner-python or ascii-cli-logo-banner-figletjs
  3. Step 3: Provide brandName (and optional fields); review bannerPlain, then use embedNotes

Best Practices

  • Capture brandName, width, slogan, and optional fields early to drive the banner content
  • Prefer the appropriate sub-skill: ascii-cli-logo-banner-python for built-in fonts, ascii-cli-logo-banner-figletjs for FIGlet/FIGfont
  • Validate width and ensure each logo line fits within the width (<= width) without trailing spaces
  • Provide plainTextFallback to guarantee a color-free version if ANSI coloring is unavailable
  • Include embedNotes to document how to start the service or link to docs

Example Use Cases

  • A CLI startup banner for a Node.js service using FIGlet for a retro logo via ascii-cli-logo-banner-figletjs
  • A Python-based CLI tool that uses the built-in font path ascii-cli-logo-banner-python for a clean sans logo
  • A serverless CLI with width 80 and centered slogan, producing bannerPlain and embedNotes for README
  • Documentation page showcasing how to integrate the banner in a README with embedNotes
  • A ticket describing a banner generation workflow across multiple services using this routing skill

Frequently Asked Questions

Add this skill to your agents
Sponsor this space

Reach thousands of developers