$ loading_
Diagnose misconfigurations, failures, and unexpected behavior in the current Amplifier session.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "session-debug" skill from askskill: 1. Download https://raw.githubusercontent.com/microsoft/amplifier-bundle-skills/main/skills/session-debug/SKILL.md 2. Save it as ~/.claude/skills/session-debug/SKILL.md 3. Reload skills and tell me it's ready
Please inspect why tools cannot be invoked correctly in the current Amplifier session. Focus on tool configuration, permissions, parameter definitions, and dependencies, then provide fixes.
A diagnosis identifying likely configuration issues, plus actionable steps to fix them.
Some operations are failing in the current session. Analyze the context, determine whether the issue comes from input, tool errors, or workflow logic, and suggest next steps.
A structured failure analysis with a recommended troubleshooting order and remediation path.
This Amplifier session is behaving unexpectedly. Help diagnose the likely root cause, identify where the issue occurs, and suggest how to verify and correct it.
Likely root-cause hypotheses, the stage where the issue occurs, and a checklist to verify and fix it.
Help the user diagnose an issue they're encountering in their current Amplifier session.
$ARGUMENTS
If no issue was described, read the session logs and summarize any errors, warnings, or notable issues.
Delegate to the session-analyst agent to investigate the current session. The session-analyst has specialized knowledge for safely analyzing large event logs (events.jsonl files can contain lines with 100k+ tokens that will crash other tools). Use the delegate tool to dispatch it with the issue description and any relevant context.
Check session configuration. Review the current session's configuration for common issues:
Session and project settings are typically at:
.amplifier/settings.yaml~/.amplifier/settings.yaml~/.amplifier/keys.envCheck for common patterns:
Explain what you found in plain language. Avoid jargon. Tell the user:
If the issue can't be diagnosed from logs alone, suggest the user:
amplifier doctor for a system health checkamplifier module list to verify module availabilityamplifier --verbose to see detailed startup outputResearch, plan, and execute large code changes with parallel PR-producing agents.
Analyze images, extract text, and answer visual questions with LLM vision models.
Design robust config and state file handling with safe defaults and crash recovery.
Get skeptical, practical guidance on architecture, legacy refactors, and tooling decisions.
Design auth and TLS patterns for smooth local use and secure remote access.
Design CLI tools with simple installs, command routing, and layered config.
Manage device session states, pause and resume flows, and availability monitoring.
Systematically reproduce, isolate, diagnose, and fix tricky software or environment issues.
Manage session and stream state with pause, resume, and device monitoring.
Diagnose common issues, compatibility problems, and session or stream debugging cases.
Search and analyze past session logs with jq for context and insights.
Analyze Copilot session history for summaries, search, reindexing, and usage guidance.