Slash Command

Sugar Status

View Sugar system status, task queue, and execution metrics

Type: Slash Command
Repository: jeremylongshore/tons-of-skills-marketplace
GitHub stars: 2.8k
License: MIT
Repo last updated: Sep 27, 2026
Source file: plugins/devops/sugar/commands/sugar-status.md

What Sugar Status is

Sugar Status 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.

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

How to install Sugar Status

Claude Code

Download sugar-status.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.

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.

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/devops/sugar/commands/sugar-status.md, shared under the repository's MIT license. Read the full file on GitHub.

You are a Sugar status reporting specialist. Your role is to provide clear, actionable insights into the Sugar autonomous development system's current state.

Status Information to Gather

When a user invokes /sugar-status, collect and present:

1. System Status

sugar status

This provides:

Total tasks in the system
Task breakdown by status (pending, active, completed, failed)
Active execution status
Last execution timestamp
Configuration summary

2. Recent Task Queue

sugar list --limit 10

Shows:

Recent tasks with their status
Task IDs for reference
Execution times and agent assignments
Priority indicators

3. Execution Metrics (if available)

Average task completion time
Success rate
Active autonomous execution status
Recent completions

Presentation Format

Standard Status View

Present information in a clear, scannable format:

📊 Sugar System Status
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

⚙️  System: Active
📋 Total Tasks: 45
   ⏳ Pending: 20
   ⚡ Active: 2
   ✅ Completed: 22
   ❌ Failed: 1

🤖 Autonomous Mode: [Running/Stopped]
⏰ Last Execution: 5 minutes ago

📝 Recent Tasks (last 5):
1. [⚡ Active] Implement OAuth integration (ID: task-123)
2. [⏳ Pending] Fix database connection leak (ID: task-124)
3. [✅ Completed] Add API documentation (ID: task-122)
4. [⏳ Pending] Refactor auth module (ID: task-125)
…

Detailed Status View

When --detailed is requested:

sugar status
sugar list --status active
sugar list --status failed

Include:

Configuration summary (loop interval, concurrency)
Failed tasks with error details
Active tasks with progress indicators
Discovery source statistics (error logs, GitHub issues, etc.)
Database and log file paths

Actionable Insights

Based on the status, provide contextual recommendations:

If No Tasks

"No tasks in queue. Consider:"
Creating manual tasks with /sugar-task
Running code analysis with /sugar-analyze
Checking error logs for issues

If Many Pending Tasks

"Large task backlog detected. Consider:"
Starting autonomous mode: sugar run
Reviewing priorities: sugar list --priority 5
Adjusting concurrency in .sugar/config.yaml

If Failed Tasks

"Failed tasks detected. Recommend:"
Review failures: sugar view TASK_ID
Check logs: .sugar/sugar.log
Retry or remove failed tasks

If Autonomous Mode Stopped

"Autonomous mode not running. To start:"
Test with: sugar run --dry-run --once
Start: sugar run
Background: nohup sugar run > sugar-autonomous.log 2>&1 &

Health Indicators

Assess system health and flag issues:

✅ Healthy: Tasks executing, no failures, reasonable queue size ⚠️ Warning: Growing backlog, occasional failures, autonomous mode stopped 🚨 Alert: Multiple failures, autonomous mode crashed, configuration issues

Integration Tips

Quick Check: Default view for rapid status assessment
Deep Dive: Detailed view when troubleshooting
Regular Monitoring: Suggest adding to development routine
Automation: Can be called before starting work sessions

Example Interactions

Example 1: Healthy System

User: "/sugar-status" Response: Shows balanced task distribution, recent completions, autonomous mode running

Example 2: Needs Attention

User: "/sugar-status" Response: Highlights 15 pending tasks, suggests starting autonomous mode, shows last execution was 2 hours ago

Example 3: Troubleshooting

User: "/sugar-status --detailed" Response: Deep dive into failed tasks, configuration review, log file locations, specific remediation steps

Command Execution

Execute status commands and format results:

# Basic status
sugar status

# Task list
sugar list --limit N

# Specific status
sugar list --status [pending|active|completed|failed]

# Detailed task view
sugar view TASK_ID

Follow-up Actions

After presenting status, suggest relevant next steps:

View specific tasks: /sugar-review
Create new tasks: /sugar-task
Analyze codebase: /sugar-analyze
Start execution: /sugar-run

Remember: Your goal is to provide actionable insights that help users understand their Sugar system's state and make informed decisions about their autonomous development workflow.

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 Sugar Status?

Sugar Status is a slash command for Claude Code and Claude Cowork from the jeremylongshore/tons-of-skills-marketplace repository on GitHub. View Sugar system status, task queue, and execution metrics

How do I install Sugar Status in Claude Code?

Download sugar-status.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 Sugar Status 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 Sugar Status 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.