Use this guide to add or inspect `debug` logging with consistent `lobe-*` namespaces and format specifiers. It shows how to enable output in a browser, Node.js, or Electron, so developers can see diagnostic messages while running an application.
Use for debug() logging, lobe-* namespaces, DEBUG/localStorage.debug configuration and log formatting.
Run score Not tested
See how to installThis guide shows the basic form for logging with the debug library and how to name namespaces for different modules. It demonstrates creating a logger such as lobe-server:market and writing strings, numbers, and objects with format specifiers. It also explains how to enable lobe-* output in a browser with localStorage.debug, in Node.js with the DEBUG environment variable, and in Electron with process.env.DEBUG.
Use it when adding logs to follow application activity, checking the naming convention for existing logs, or viewing output for a specific namespace during development. It also gives different naming patterns for server, client, desktop, and router logs.
debug logging to this module.”lobe-* logs in the browser.”The examples use the debug library. The method for enabling output differs between browsers, Node.js, and Electron.
This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.
AI checked the SKILL.md for operations that need care and for setup requirements. The score comes only from actually running the skill (hands-on test).
Not counted in the score. Rated by AI (OpenAI Codex) as of Oct 26, 2026. Treat it as a guide and read the original before installing.
Review the instructions the agent will receive before you install.
import debug from 'debug';
// Format: lobe-[module]:[submodule]
const log = debug('lobe-server:market');
log('Simple message');
log('With variable: %O', object);
log('Formatted number: %d', number);
lobe-desktop:[module]lobe-server:[module]lobe-client:[module]lobe-[type]-router:[module]%O - Object expanded (recommended for complex objects)%o - Object%s - String%d - NumberlocalStorage.debug = 'lobe-*';
DEBUG=lobe-* bun run dev
DEBUG=lobe-* pnpm dev
process.env.DEBUG = 'lobe-*';
// apps/server/src/routers/lambda/agentEval.ts
import debug from 'debug';
const log = debug('lobe-lambda-router:agent-eval');
log('getAgent input: %O', input);
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Use this skill to verify a delivery by exercising the real product through a suitable surface such as a CLI, web app, desktop app, or iOS Simulator. It helps create or find a verification plan, capture evidence, and publish an acceptance report.
Use this skill to add an AI model provider to LobeHub across runtime integration, model cards, settings, branding, documentation, and acceptance checks. It also covers provider documentation updates and distinguishes new providers from models added to an existing provider.
Use this skill to add a server-side environment variable that sets a default for a user setting. It walks through validation, server configuration and store merging, plus updating the example environment file and self-hosting documentation.
Provides guidance for registering hooks around an agent’s execution steps, tool calls, human approvals, context compression, and sub-agent calls. Hooks can observe events, supply local mock tool results, or use webhooks to allow or deny tool results under configured policies.
Build event-driven background workflows for agents by defining sources, interpreting them as signals, and running actions through policies. It also guides asynchronous handoffs, deduplication, scoped execution, completion receipts, and observability.
Use this skill to run end-to-end acceptance checks for bot channels in real desktop chat apps. It drives apps such as Discord, Slack, Telegram, WeChat, Lark, and QQ to send a message, wait for a response, and capture the result.