SuperAPI AI Directory
Partner with us中文AI newsFavorites
Skillsascii-mini-charts

ascii-mini-charts

General & other

View repository

Updated 10-15 21:47

About this skill

When to use this skill

CRITICAL TRIGGER RULE

  • Use this skill ONLY when the user explicitly mentions the exact skill name: ascii-mini-charts.

Trigger phrases include:

  • "ascii-mini-charts"
  • "use ascii-mini-charts"
  • "Generate sparkline / sparkline with ascii-mini-charts"
  • "Use ascii-mini-charts to label min/max/current"

Boundary

  • No statistical inference. Visualization only.
  • Default output is ASCII-only. Unicode blocks are optional and MUST include an ASCII-only fallback.
  • Default output width should stay <= 60 columns. For longer series, provide a compression strategy (sampling/bucketing).

How to use this skill

Inputs

  • series (required numeric list)
  • type (sparkline | bar | line, default sparkline)
  • width (default min(len(series), 30))
  • height (default 10 for bar/line)
  • normalize (linear | log, default linear)
  • showLabels (default true)

Outputs (required)

  • chartMinimal
  • chartAnnotated (with min/max/current)
  • scaleNotes (normalization + outlier strategy)

Script

  • scripts/mini_charts.py: generate ASCII mini charts from JSON stdin

Examples

  • examples/sparkline.md

Quality checklist

  1. Trend is clear; labels are short and non-spammy
  2. ASCII-only output copy/pastes cleanly
  3. Provide a compression strategy for long series

Keywords

English: ascii-mini-charts, sparkline, ascii chart, bar chart, line chart, trend, normalize Chinese: ascii-mini-charts, sparkline, ASCII chart, bar chart, line chart, trend, normalization

Common Gotchas (Gotchas)

  1. Version compatibility: Pay attention to compatibility between framework versions and dependency libraries; APIs may differ across versions
  2. Configuration file format: Configuration file format errors are the most common issue; it is recommended to use the editor's syntax checking
  3. Environment variables: Ensure all necessary environment variables are set correctly; do not hardcode sensitive information
  4. Dependency conflicts: When multiple versions coexist, pay attention to dependency conflicts; use a lock file to pin versions
  5. Performance pitfalls: Pay attention to performance optimization in large-data scenarios and avoid common issues such as N+1 queries

Usage workflow

Step 1: Environment preparation

Ensure the necessary dependencies and tools are installed in the development environment.

Step 2: Configuration initialization

Perform basic configuration according to project requirements.

Step 3: Core functionality usage

Implement the core functionality according to the example code.

Step 4: Test verification

Run tests to ensure the functionality works properly.

Step 5: Deployment and release

After development is complete, proceed with deployment and monitoring.