Sponsor Suno AI Music arrow_forward
Slash Command

Progress

Create visual progress updates - charts, before/after comparisons, metrics

Type
Slash Command
GitHub stars
2.8k
License
MIT
Repo last updated
Sep 27, 2026

What Progress is

Progress is a slash command published in the jeremylongshore/tons-of-skills-marketplace repository on GitHub, which has about 2.8k stars. The repository describes itself as: “Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.”

A slash command is a reusable prompt saved as a markdown file and run by typing its name after a slash. In Claude Code, custom commands have been merged into skills: a file in .claude/commands/ and a skill folder in .claude/skills/ both create the same kind of command, and existing command files keep working.

Progress gives you a repeatable way to run the same instructions without retyping them, optionally with arguments.

How to install Progress

Claude Code

  1. Download progress.md from the repository.
  2. Save it to ~/.claude/commands/ (all projects) or .claude/commands/ (one project). As a skill, you can instead save it as ~/.claude/skills/<name>/SKILL.md.
  3. Run it by typing / followed by its name.

Claude Cowork

  1. Turn the command into a skill: create a folder with the file saved as SKILL.md and zip it.
  2. In Customize → Skills, click +, then upload the ZIP.
  3. Run it from any task with / and the skill name.

New to extending Cowork? Our plugins guide and Customize guide explain how skills, plugins, and connectors fit together.

Inside the source file

An excerpt from plugins/packages/creator-studio-pack/plugins/project-documentation/progress-tracker-visual/commands/progress.md, shared under the repository's MIT license. Read the full file on GitHub.

Generate visual progress tracking graphics from your git history and metrics.

Usage

/progress speed              # API response time tracking
/progress users              # User growth chart
/progress commits            # Commit frequency graph
/progress coverage           # Test coverage over time
/progress [custom-metric]    # Any custom metric

Purpose

Create shareable progress visuals:

  • Before/after comparisons
  • Time-series charts
  • Metric dashboards
  • Thumbnail-ready graphics
  • Social media posts

Implementation

When user runs /progress [metric]:

  1. Analyze Git History
   # Extract commits with metric data
   git log --all --since="30 days ago" --grep="metric" --pretty=format:"%ai|%s"
  1. Parse Metrics
  • Look for numbers in commit messages
  • Track performance benchmarks
  • Find test coverage reports
  • Extract user counts, response times, etc.
  1. Generate Visualization
   API RESPONSE TIME - 30 DAY TREND

   Day 1:   2000ms ████████████████████ (100%)
   Day 7:   1500ms ███████████████      (75%)
   Day 14:  800ms  ████████             (40%)
   Day 21:  200ms  ██                   (10%)

   📊 10x IMPROVEMENT
   ⬇️  90% REDUCTION
   🚀  FROM 2000ms TO 200ms
  1. Export as Image
  • Generate PNG/SVG
  • Optimized for social media (1200x675)
  • Thumbnail-ready (1920x1080)
  • High contrast for readability

Chart Types

Speed/Performance

/progress speed

Output:
- Line graph of response times
- Before/after comparison bars
- Percentage improvement
- Key optimization milestones

User Growth

/progress users

Output:
- Cumulative user count
- Daily/weekly/monthly growth rate
- Milestone markers (100, 1K, 10K users)
- Projected growth curve

Code Quality

/progress coverage

Output:
- Test coverage percentage over time
- Lines covered vs total
- Coverage by module/component
- Trending direction (improving/declining)

Build Activity

/progress commits

Output:
- Commit frequency heatmap
- Most active days/hours
- Commit types (feat/fix/refactor)
- Contribution streaks

Visual Styles

Minimal (Default)

  • Clean lines
  • Limited color (1-2 accent colors)
  • Large text
  • High contrast

Thumbnail

  • Bold text
  • Bright colors
  • Large numbers
  • Emoji indicators

Dashboard

  • Multiple metrics
  • Grid layout
  • Consistent styling
  • Compact information density

Example Outputs

API Speed Chart

┌─────────────────────────────────────────┐
│  API RESPONSE TIME - 3 WEEK PROGRESS   │
├─────────────────────────────────────────┤
│                                         │
│  2000ms ████████████████████            │
│         ↓                               │
│  1500ms ███████████████                 │
│         ↓                               │
│  800ms  ████████                        │
│         ↓                               │
│  200ms  ██                              │
│                                         │
│  📊 10x FASTER IN 21 DAYS              │
│  🚀 90% IMPROVEMENT                    │
│                                         │
└─────────────────────────────────────────┘

Saved to: ~/project/visuals/api-speed-progress.png

User Growth

┌─────────────────────────────────────────┐
│      USER GROWTH - LAST 30 DAYS        │
├─────────────────────────────────────────┤
│                                     ┌─  │
│                                 ┌───┘   │
│                             ┌───┘       │
│                         ┌───┘           │
│                     ┌───┘               │
│                 ┌───┘                   │
│             ┌───┘                       │
│         ┌───┘                           │
│     ┌───┘                               │
│  ───┘                                   │
│                                         │
│  0 ─────────── 15d ─────────── 30d    │
│  47 users → 312 users (564% growth)   │
│                                         │
└─────────────────────────────────────────┘
…

Integration

Works with:

  • build-logger-agent: Gets metrics from build logs
  • demo-video-generator: Provides visuals for demos
  • thumbnail-designer: Supplies charts for thumbnails
  • analytics-insights: Displays performance data

Your goal: Turn progress into compelling visuals that showcase achievements and drive engagement.

Before you install

  • Read the whole file first. Skills, commands, and subagents are instructions Claude will follow, so make sure they match what you want.
  • Check which tools, scripts, or MCP servers it uses. Local servers and scripts run with your permissions.
  • Try it in a test project or a copy of your files before pointing it at real work.
  • Pin the version you tested, and review changes before updating.
  • Watch for instructions that fetch web content or run shell commands; those are where prompt injection risks start. See our prompt injection guide.

FAQ

What is Progress?

Progress is a slash command for Claude Code and Claude Cowork from the jeremylongshore/tons-of-skills-marketplace repository on GitHub. Create visual progress updates - charts, before/after comparisons, metrics

How do I install Progress in Claude Code?

Download progress.md from the repository. Save it to ~/.claude/commands/ (all projects) or .claude/commands/ (one project). As a skill, you can instead save it as ~/.claude/skills/<name>/SKILL.md. Run it by typing / followed by its name.

Can I use Progress in Claude Cowork?

Turn the command into a skill: create a folder with the file saved as SKILL.md and zip it. In Customize → Skills, click +, then upload the ZIP. Run it from any task with / and the skill name.

Is Progress safe to install?

It is a third-party community resource, not reviewed by Anthropic or this site. Read the source file first, check which tools and connectors it uses, and install only from sources you trust.

Similar resources

Browse all skills, subagents, and plugins →

Listing data comes from the public GitHub repository and was last checked in September 2026. Excerpts are © their authors and shared under MIT. This directory is independent and not affiliated with Anthropic or the resource's authors.