원클릭으로
agent-debug-panel
Debug skill/hook/agent loading issues using VS Code's Agent Debug Panel
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Debug skill/hook/agent loading issues using VS Code's Agent Debug Panel
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Create and maintain ASCII visual dashboards for project tracking with parallel lane progress bars
Store and manage voice samples for TTS cloning — portable, version-controlled audio references
Clear documentation through visual excellence
AI music generation via Replicate — 5 models for background tracks, lyrics, and sound design
Practitioner methodology for longitudinal case study research, evidence-based documentation, and publication-ready academic writing in AI-assisted development.
First impressions matter. Set projects up for success.
| name | agent-debug-panel |
| description | Debug skill/hook/agent loading issues using VS Code's Agent Debug Panel |
| tier | standard |
| applyTo | **/*debug*,**/*agent*,**/*skill*,**/*hook*,**/*instruction* |
When a skill doesn't load or a hook doesn't fire, stop guessing — open the panel.
Ctrl+Shift+P)Developer: Open Agent Debug Panel@alex or any agent| Tab / Section | What You See | Debug Use |
|---|---|---|
| System Prompt Assembly | Full prompt sent to LLM including instructions, skills, context | Verify your instruction/skill was included |
| Tool Calls | Every tool invocation with arguments and results | Trace why a tool wasn't called or failed |
| Participant Resolution | Which chat participant handled the request | Confirm @alex routed correctly |
| Skill Loading | Which SKILL.md files were loaded and why | Debug "why didn't my skill activate?" |
| Instruction Matching | Which .instructions.md files matched via applyTo | Verify glob patterns work for your files |
| Hook Execution | Pre/post tool-use hook firing order and results | Debug hook failures or ordering issues |
| Agent Selection | Which .agent.md was selected and why | Verify agent routing logic |
applyTo glob in SKILL.md frontmatterCommon causes:
applyTo glob doesn't match the active filechat.agentSkillsLocations setting.instructions.md file appears in matched listapplyTo pattern in YAML frontmatterCommon causes:
applyTo glob doesn't match current file type.github/instructions/)--- delimiters)chat.instructionsFilesLocations not set to {".github/instructions": true}preToolUse, postToolUse)Common causes:
chat.hooks.enabled not set to truenode --check script.js)events array doesn't include the trigger event.agent.md file is in .github/agents/chat.useAgentsMdFile is trueCommon causes:
*.agent.md.github/agents/ directorychat.useAgentsMdFile or chat.useNestedAgentsMdFiles not enabledUseful: Copy the full system prompt to verify exactly what the LLM sees. Compare against what you expected.
Run these checks before opening the debug panel:
| Setting | Required Value | Purpose |
|---|---|---|
chat.agentSkillsLocations | [".github/skills"] | Skills discovery |
chat.instructionsFilesLocations | {".github/instructions": true} | Instructions loading |
chat.useAgentsMdFile | true | Agent file detection |
chat.hooks.enabled | true | Hook execution |
chat.plugins.enabled | true | Plugin loading |
chat.useSkillAdherencePrompt | true | Forces LLM to read SKILL.md |
Add these to .vscode/settings.json:
{
"chat.agentSkillsLocations": [".github/skills"],
"chat.instructionsFilesLocations": {
".github/instructions": true
},
"chat.useAgentsMdFile": true,
"chat.useNestedAgentsMdFiles": true,
"chat.hooks.enabled": true,
"chat.useSkillAdherencePrompt": true
}
1. Reproduce the issue in chat
2. Open Debug Panel (Developer: Open Agent Debug Panel)
3. Check loading → matching → execution → output
4. Identify the break point
5. Fix the root cause (glob, setting, syntax)
6. Reproduce again to verify