Debug Package
Use for debug() logging, lobe- namespaces, DEBUG/localStorage.debug configuration and log formatting.
mkdir -p ~/.claude/skills/debug-package && curl -fsSL 'https://raw.githubusercontent.com/lobehub/lobehub/canary/.agents/skills/debug-package/SKILL.md' -o ~/.claude/skills/debug-package/SKILL.md
Get the complete skill folder, including its scripts and reference files.
When to use this skill
Use Debug Package when an AI agent needs a reusable SKILL.md workflow for this job: Use for debug() logging, lobe- namespaces, DEBUG/localStorage.debug configuration and log formatting.
When not to use it
Skip Debug Package when the task is outside the coding category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/debug-package && curl -fsSL 'https://raw.githubusercontent.com/lobehub/lobehub/canary/.agents/skills/debug-package/SKILL.md' -o ~/.claude/skills/debug-package/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/debug-package/SKILL.md. For a shared project, commit the folder at .claude/skills/debug-package/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Debug Package skill for this task: Use Debug Package when this documented workflow matches the task. Confirm any required inputs or files before making changes.
What supports this recommendation?
68/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 70/100
- Practical detail
- 68/100
- Source evidence
- 63/100
- Source signals
- 72/100
Model compatibility evidence
- claudeuntested
No model-specific signal or recorded compatibility test was found.
- chatgptuntested
No model-specific signal or recorded compatibility test was found.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
# Debug Package Usage Guide
## Basic Usage
```typescript 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); ```
## Namespace Conventions
- Desktop: `lobe-desktop:[module]` - Server: `lobe-server:[module]` - Client: `lobe-client:[module]` - Router: `lobe-[type]-router:[module]`
## Format Specifiers
- `%O` - Object expanded (recommended for complex objects) - `%o` - Object - `%s` - String - `%d` - Number
## Enable Debug Output
### Browser
```javascript localStorage.debug = 'lobe-*'; ```
### Node.js
```bash DEBUG=lobe-* bun run dev DEBUG=lobe-* pnpm dev ```
### Electron
```typescript process.env.DEBUG = 'lobe-*'; ```
## Example
```typescript // apps/server/src/routers/lambda/agentEval.ts import debug from 'debug';
const log = debug('lobe-lambda-router:agent-eval');
log('getAgent input: %O', input); ```
Intended uses
- Use Debug Package when this documented workflow matches the task.
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.