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/council-here
development
VerifiedTrustedCommunity
Convene the persona panel on the CURRENT conversation / work-in-progress — the plan, design, or decision you've been building in this session. The INLINE counterpart to /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 Jun 20, 2026
microsoft/council
development
VerifiedTrustedCommunity
Convene the persona panel (six orthogonal review lenses) on a target — cold independent fan-out, debate-to-consensus, synthesized verdict with recorded dissent and a roster manifest.
10SKILL.mdUpdated Jun 19, 2026
microsoft/msgraph-integration-patterns
development
VerifiedTrustedCommunity
Hard-won patterns for probing, building, troubleshooting, and iterating against Microsoft Graph API endpoints -- especially from a browser SPA using delegated MSAL.js auth calling Graph directly with no backend (lessons generalize to any Graph integration). Covers the throwaway-probe-file methodology for de-risking before building, OData/query quirks, permission and admin-consent sequencing, recordings/transcripts access patterns (SharePoint REST, not Graph), CSP requirements for a pure-browser SPA, retry/pagination/backoff patterns, and the MSAL/EasyAuth auth-redirect-loop debugging saga. Use when integrating with Microsoft Graph, Teams APIs, MSAL.js, or EasyAuth; when hitting an unexpected Graph error (400/403/429), a silent missing-scope failure, an auth redirect loop, or a CSP violation that only appears in production; or when deciding how to validate a new Graph capability before committing it to a codebase.
9SKILL.mdUpdated Jul 9, 2026
microsoft/amplifier-tool-leverage-patterns
tools
VerifiedTrustedCommunity
Use when building an Amplifier-powered workflow or automation tool and deciding how to expose it — as standalone .dot attractor pipelines (incl. inside the Resolve dot-graph resolver), an importable Python lib, agent-callable tool modules, or a CLI. Covers the four leverage levels, the DRY rule that keeps logic in ONE home, the judgment for which levels a real consumer actually needs (and when adding a level is just ceremony), and the maximally-DRY attractor-only specialization where the .dot pipeline is the sole logic home.
9SKILL.mdUpdated Jun 25, 2026