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: Jun 23, 2026, 7:30 AM90.4s1 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
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/goal-batch
tools
VerifiedTrustedCommunity
Plan a batch of independent work into isolated lanes, get your approval, then run each lane as its own autonomous /goal session — one git worktree, one branch, one tmux session each — and verify and merge the results yourself. Use when work decomposes into pieces that can run at the same time: "run these in parallel", "goal-batch", "launch lanes for these", "work these N tasks simultaneously", "batch these as goals". Nothing launches until you have seen the lane split and said go. This is NOT fire-and-forget: the orchestrating session re-runs the full test suite itself after every merge and never accepts a lane's own claim that it finished. NOT for bounded edits that each end in their own PR — use mass-change for that. Requires git, tmux, the amplifier CLI on PATH, and the goalify and monitor skills.
10SKILL.mdUpdated Aug 15, 2026
microsoft/restless-old-brian
development
VerifiedTrustedCommunity
Momentum-driven engineering reviewer that holds one uncompromising gate — is it REAL, proven end-to-end as a user would — while driving work forward. Demands proof over claims, plumbing before polish, fail-loud over fallbacks, trust in the model over instructions, and protects the critical path so good-but-costly ideas don't stall the work. Warm, blunt, forward-driving — not a curmudgeon. A lens for any checkpoint — brainstorm, design, plan, implement, debug, or ship — not just the finish. Use when: pressure-testing whether an idea/design/plan is provable and on the critical path, whether you're building in the right order, whether a fix is real or a band-aid, or whether work is actually done/ready — any time the worry is "are we fooling ourselves about what's real?"
10SKILL.mdUpdated Aug 6, 2026
microsoft/product-council
development
VerifiedTrustedCommunity
Convene the Product Development Council (six orthogonal product-delivery lenses, anchored by a mandatory problem-validation gate) on a target — cold independent fan-out, debate-to-consensus, synthesized verdict with recorded dissent and a roster manifest.
10SKILL.mdUpdated Aug 6, 2026
microsoft/product-council-here
development
VerifiedTrustedCommunity
Convene the Product Development Council on the CURRENT conversation / work-in-progress — the plan, roadmap, or scope decision you've been building in this session. The INLINE counterpart to /product-council (which forks and runs isolated, so it cannot see the chat). Use when you want the council to critique what we're working on right now.
10SKILL.mdUpdated Aug 6, 2026