Ora: Terminal Spinners

VerifiedSafe

Add terminal spinners with Ora. Use when showing loading indicators in CLI tools, displaying progress during async operations, or building polished command-line interfaces with status feedback.

Sby Skills Guide Bot
DevelopmentBeginner
7/28/2026
Claude CodeCursorWindsurfCopilotCodex
#ora#cli-spinner#terminal-ui#nodejs#progress-feedback

Recommended for

Automated summary

This skill documents how to use Ora, a Node.js library that renders terminal spinners and status indicators during asynchronous operations.

Strengths

  • Very small API: start(), succeed() and fail() cover most cases
  • Demonstrates multi-step operations by reusing a single spinner instance
  • Shows how to update spinner.text and use stopAndPersist() for custom symbols
  • Calls out real pitfalls: ESM-only since v6 and static fallback output in CI

Limitations

  • Covers display only: no guidance on cancellation, timeouts or conditional verbosity
  • Examples rely on helper functions (exec, build, deployToCloud) that are not provided
  • No advice on integrating with test frameworks or structured loggers
When to use it

Use it when adding polished loading or progress indicators to a Node.js command-line tool.

When not to use it

Avoid it when the tool must emit machine-readable output (JSON, structured logs) or when the project is not Node.js.

Security analysis

Safe
Quality score90/100

The skill only documents usage patterns for the Ora terminal spinner library with benign TypeScript examples. It declares no tools, executes no commands, and contains no destructive, exfiltration, obfuscation, or safety-disabling behavior.

No concerns found

How this analysis is made

Examples

Add a spinner to an install step
Wrap my `npm install` call in a CLI script with an ora spinner that shows succeed on completion and fail plus exit code 1 on error.
Multi-step deploy feedback
Refactor my deploy script so each phase (build, tests, deploy, health check) reuses one ora spinner and ends with a clear succeed or fail message.
Custom persisted summary line
Use ora's stopAndPersist with a custom green checkmark and chalk colours to print a final 'Processed 42 files in 3.2s' summary line.

name: ora description: >- Add terminal spinners with Ora. Use when showing loading indicators in CLI tools, displaying progress during async operations, or building polished command-line interfaces with status feedback. license: Apache-2.0 compatibility: 'Node.js 16+' metadata: author: terminal-skills version: 1.0.0 category: development tags: [ora, cli, spinner, loading, terminal]

Ora

Overview

Ora creates elegant terminal spinners. Show progress during async operations (API calls, file processing, builds), then succeed/fail with a final status. Used by create-next-app, Vercel CLI, Angular CLI.

Instructions

Step 1: Basic Spinner

import ora from 'ora'

const spinner = ora('Installing dependencies...').start()

try {
  await exec('npm install')
  spinner.succeed('Dependencies installed')
} catch (err) {
  spinner.fail('Installation failed')
  process.exit(1)
}

Step 2: Multi-Step Operations

async function deploy(env: string) {
  const spinner = ora()

  spinner.start('Building project...')
  await build()
  spinner.succeed('Build complete')

  spinner.start('Running tests...')
  const results = await runTests()
  spinner.succeed(`${results.passed} tests passed`)

  spinner.start(`Deploying to ${env}...`)
  const url = await deployToCloud(env)
  spinner.succeed(`Deployed to ${url}`)

  spinner.start('Verifying deployment...')
  await healthCheck(url)
  spinner.succeed('Deployment verified ✓')
}

Step 3: With Other Libraries

import ora from 'ora'
import chalk from 'chalk'

const spinner = ora({
  text: 'Processing files...',
  color: 'cyan',
  spinner: 'dots',       // or 'line', 'arc', 'bouncingBar'
})

spinner.start()
spinner.text = `Processing ${chalk.bold('image-001.png')}...`
// ... after processing
spinner.text = `Processing ${chalk.bold('image-002.png')}...`

spinner.stopAndPersist({
  symbol: chalk.green('✓'),
  text: `Processed ${chalk.bold('42')} files in ${chalk.gray('3.2s')}`,
})

Guidelines

  • succeed() / fail() / warn() / info() stop the spinner with a status icon.
  • stopAndPersist() for custom symbols/text when the built-in statuses don't fit.
  • Update spinner.text during long operations to show progress.
  • Ora is ESM-only since v6. Use import ora from 'ora'.
  • In CI environments, ora falls back to static text (no animation).

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/ora-terminal-spinners-ms47vp7r/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/ora-terminal-spinners-ms47vp7r' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/ora-terminal-spinners-ms47vp7r/download' --output '.skill-downloads/ora-terminal-spinners-ms47vp7r/SKILL.md.part' && mv '.skill-downloads/ora-terminal-spinners-ms47vp7r/SKILL.md.part' '.skill-downloads/ora-terminal-spinners-ms47vp7r/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

Environment declared by the author: Node.js 16+

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/ora-terminal-spinners-ms47vp7r/SKILL.md' && test -s '.skill-downloads/ora-terminal-spinners-ms47vp7r/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/ora' && cp -R '.skill-downloads/ora-terminal-spinners-ms47vp7r' '.claude/skills/ora'

Cursor
test -f '.skill-downloads/ora-terminal-spinners-ms47vp7r/SKILL.md' && test -s '.skill-downloads/ora-terminal-spinners-ms47vp7r/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/ora' && cp -R '.skill-downloads/ora-terminal-spinners-ms47vp7r' '.cursor/skills/ora'

Codex
test -f '.skill-downloads/ora-terminal-spinners-ms47vp7r/SKILL.md' && test -s '.skill-downloads/ora-terminal-spinners-ms47vp7r/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/ora' && cp -R '.skill-downloads/ora-terminal-spinners-ms47vp7r' '.agents/skills/ora'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/ora-terminal-spinners-ms47vp7r'

openskills read 'ora-terminal-spinners-ms47vp7r'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/ora-terminal-spinners-ms47vp7r/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills