microsoft/session-debug
skills/session-debug/SKILL.md
Diagnose issues in the current Amplifier session — misconfigured tools, failing operations, unexpected behavior. Use when something isn't working right.
$ install --global
skillsauthnpx skillsauth add microsoft/amplifier-bundle-skills session-debugInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 24, 2026, 8:35 PM0.5s1 file scanned
SKILL.md
- name:
- session-debug
- description:
- Diagnose issues in the current Amplifier session — misconfigured tools, failing operations, unexpected behavior. Use when something isn't working right.
- context:
- fork
- disable-model-invocation:
- true
- user-invocable:
- true
- model_role:
- general
- allowed-tools:
- Read Grep Glob Bash
Debug: Session Diagnostics
Help the user diagnose an issue they're encountering in their current Amplifier session.
Issue Description
$ARGUMENTS
If no issue was described, read the session logs and summarize any errors, warnings, or notable issues.
Instructions
-
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:
- Bundle composition problems (missing modules, failed loads)
- Provider configuration (missing API keys, wrong endpoints)
- Tool availability (tools expected but not mounted)
- Hook failures (hooks that errored during lifecycle events)
Session and project settings are typically at:
- Project:
.amplifier/settings.yaml - User:
~/.amplifier/settings.yaml - Keys:
~/.amplifier/keys.env
-
Check for common patterns:
- Tool calls returning errors repeatedly
- Provider rejections (rate limits, auth failures, model not found)
- Module mount failures at startup
- Context overflow or compaction issues
-
Explain what you found in plain language. Avoid jargon. Tell the user:
- What went wrong
- Why it likely happened
- Concrete steps to fix it
-
If the issue can't be diagnosed from logs alone, suggest the user:
- Run
amplifier doctorfor a system health check - Check
amplifier module listto verify module availability - Try
amplifier --verboseto see detailed startup output
- Run
Related Skills
microsoft/crusty-old-engineer
tools
VerifiedTrustedCommunity
Curmudgeonly engineering advisor that provides grounded skepticism, evidence-linked judgment, and constructive progress on architectural decisions, legacy refactors, tooling choices, and broad "how should I start?" questions. Sounds like a senior systems engineer who has reviewed too many designs to be impressed, but still cares about correctness. Use when: architectural decisions, legacy replacements, new tooling evaluation, broad planning questions.
4SKILL.mdUpdated Apr 24, 2026
microsoft/verification-discipline
testing
VerifiedTrustedCommunity
Use when verifying that completed work actually works. Auto-surface during /verify mode, post-implementation review, or before claiming a task is done. Teaches the discipline of testing outcomes vs implementation, the unit/integration/smoke gradient, and what "done" actually means.
3SKILL.mdUpdated May 24, 2026
microsoft/per-repo-conventions
development
VerifiedTrustedCommunity
Use when starting work in any repository. Auto-surface when an agent is about to write code, create a PR, or verify work. Teaches the discovery pattern for finding and applying per-repo conventions (AGENTS.md, PR templates, CONTRIBUTING.md) before acting.
3SKILL.mdUpdated May 19, 2026
microsoft/one-line-installer-patterns
tools
VerifiedTrustedCommunity
Use when designing a curl-piped install script for a project that cannot use uv tool install or npm publish — multi-service stacks (Docker Compose), raw TS/React apps, tools that bootstrap system dependencies, or installs for non-technical audiences. Documents the security trade-off, the community convention used by rustup, bun, deno, fly, ollama, and supabase, and the cases where this pattern is the wrong answer.
3SKILL.mdUpdated Apr 30, 2026