How do I install the Cbdebugger skill?

Run npx skillmds@latest add coldbox/cbdebugger in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Cbdebugger safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Cbdebugger?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Cbdebugger free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Cbdebugger?

ColdBox (@coldbox) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Cbdebugger by coldbox — Agent Skill

Name: Cbdebugger
Author: ColdBox

Cbdebugger

Use this skill when installing, configuring, or using the CBDebugger visual debugging panel in a ColdBox application. Covers enabling the panel in development, performance profiling, SQL query tracking, cache monitoring, request inspection, and ensuring the debugger is disabled in production.

ColdBox 230a061 2.6 KB Updated Sep 17, 2026

File contents

CBDebugger Skill

When to Use This Skill

Load this skill when:

Installing or enabling the CBDebugger module
Diagnosing performance bottlenecks in development
Tracking SQL queries and their execution times
Inspecting RC/PRC/CGI scopes during debugging
Configuring the debugger to appear only in specific environments
Ensuring debugger is never exposed to end-users in production

Installation

box install cbdebugger

Configuration

Always gate the debugger behind an environment check:

// config/ColdBox.cfc
moduleSettings = {
    cbdebugger = {
        // Only enable in development — never expose in production
        enabled        = getSetting( "environment" ) == "development",
        renderDebugPanel = true,
        expanded       = false,         // collapse panel by default

        // Optional: restrict to specific IPs
        ipList         = "127.0.0.1",   // comma-separated list

        // Profiling options
        showTracers    = true,
        queryMonitor   = {
            enabled    = true,
            logQueries = false          // set true to log all queries
        }
    }
}

Features

Feature	Description
Performance Profiling	Request timings and execution paths
SQL Query Tracking	All DB queries with execution time and bindings
Cache Monitoring	CacheBox statistics and operations
Request Inspection	RC, PRC, CGI, form, and URL scopes
Tracer Messages	Custom `tracer()` calls inline in code
Exception Detail	Full stack traces with local variable context

Usage in Handlers / Flow

// Add a debug tracer message (only visible when debugger is enabled)
tracer( "About to call payment service", { orderId : rc.orderId } )

// Then continue your logic
paymentService.charge( rc.orderId )

Production Safety Checklist

enabled must evaluate to false in staging and production
Never deploy with ipList empty and enabled = true on a public server
Use getSetting("environment") or .env variables — not hard-coded true
Panel renders at bottom of HTML responses — harmless when disabled but wasteful at scale

Documentation

Full documentation: https://coldbox-debugger.ortusbooks.com

---name: cbdebuggerdescription: Use this skill when installing, configuring, or using the CBDebugger visual debugging panel in a ColdBox application. Covers enabling the panel in development, performance profiling, SQL query tracking, cache monitoring, request inspection, and ensuring the debugger is disabled in production.---# CBDebugger Skill## When to Use This SkillLoad this skill when:- Installing or enabling the CBDebugger module- Diagnosing performance bottlenecks in development- Tracking SQL queries and their execution times- Inspecting RC/PRC/CGI scopes during debugging- Configuring the debugger to appear only in specific environments- Ensuring debugger is never exposed to end-users in production## Installation```bashbox install cbdebugger```## Configuration**Always gate the debugger behind an environment check:**```js// config/ColdBox.cfcmoduleSettings = { cbdebugger = { // Only enable in development — never expose in production enabled = getSetting( "environment" ) == "development", renderDebugPanel = true, expanded = false, // collapse panel by default // Optional: restrict to specific IPs ipList = "127.0.0.1", // comma-separated list // Profiling options showTracers = true, queryMonitor = { enabled = true, logQueries = false // set true to log all queries } }}```## Features| Feature | Description ||---------|-------------|| **Performance Profiling** | Request timings and execution paths || **SQL Query Tracking** | All DB queries with execution time and bindings || **Cache Monitoring** | CacheBox statistics and operations || **Request Inspection** | RC, PRC, CGI, form, and URL scopes || **Tracer Messages** | Custom `tracer()` calls inline in code || **Exception Detail** | Full stack traces with local variable context |## Usage in Handlers / Flow```js// Add a debug tracer message (only visible when debugger is enabled)tracer( "About to call payment service", { orderId : rc.orderId } )// Then continue your logicpaymentService.charge( rc.orderId )```## Production Safety Checklist- `enabled` **must** evaluate to `false` in staging and production- Never deploy with `ipList` empty and `enabled = true` on a public server- Use `getSetting("environment")` or `.env` variables — not hard-coded `true`- Panel renders at bottom of HTML responses — harmless when disabled but wasteful at scale## DocumentationFull documentation: https://coldbox-debugger.ortusbooks.com

Frequently asked questions