debug-off

Disable verbose trace logging for iEvo skills while preserving the debug session.

Updated May 17, 2026
One-click install
npx skills add https://github.com/ievo-ai/skills --skill debug-off
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug-off
Source: https://github.com/ievo-ai/skills/tree/main/plugins/ievo/skills/debug-off
Command: npx skills add https://github.com/ievo-ai/skills --skill debug-off

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Reduces the size and verbosity of debug logs by disabling trace-level logging, while still preserving the current debug session for future review.

Core Features & Use Cases

  • Disable Verbose Logging: Turn off extensive trace logging for iEvo skills, improving system performance and reducing disk usage.
  • Preserve Debug Session: Keep the current debug logs for auditing or troubleshooting purposes.
  • User Triggered: Initiates when the user explicitly commands "turn off debug" or similar phrases.

Quick Start

Use the debug-off skill by saying "turn off debug" or "stop verbose".

Frequently Asked Questions about debug-off

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn off verbose trace logging without losing my current debug session?

Disabling verbose trace logging preserves your current debug session for auditing. You can turn off extensive trace logs to reduce disk usage and improve performance while keeping existing logs intact for future troubleshooting.

What is the best way to reduce debug log verbosity for auditing?

The best way to reduce debug log verbosity is to disable trace-level logging while keeping the debug session active. This balances performance with debug log management by retaining logs for audit without continuing to generate verbose output.

Do I need a POSIX shell to disable trace logging?

Yes, you need a POSIX shell and the presence of a debug flag file to disable trace logging. These prerequisites ensure the command executes idempotently, safely turning off verbose logging without causing duplicate or conflicting actions.

How does disabling trace logging affect system performance?

Disabling trace logging improves system performance and reduces disk usage. By turning off extensive verbose logs, the system allocates fewer resources to logging operations, freeing up capacity for administrative workflows.

Can I run the command to stop verbose logging multiple times safely?

Yes, you can safely run the command to stop verbose logging multiple times. The execution is idempotent, meaning repeated commands produce the same result without causing errors, as long as the debug flag file is present.

When should I not use the approach of turning off debug logs?

You should not turn off debug logs when you are actively troubleshooting an issue that requires real-time trace-level data. Disabling verbose logging stops the collection of new trace data, which limits live debugging visibility.