session-debug skillA
session-debug is agent-read markdown (skill) from microsoft/amplifier-bundle-skills: Diagnose issues in the current Amplifier session — misconfigured tools, failing operations, unexpected behavior. Use when something isn't working right..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# 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 1. **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. 2. **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` 3. **Check for common patterns:** …
Read the whole file at its exact version.
How to install
mdr add microsoft/amplifier-bundle-skills/session-debug@git:20260622.6e0f42emdr add microsoft/amplifier-bundle-skills/session-debug@sha256:0216ffae3fd17347Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_q6r5d355hgwybhrc)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260622.6e0f42e latest | 2026-06-22 | 6e0f42e | 2,062 B | A | view · diff |
| git:20260321.8a40297 | 2026-03-21 | 8a40297 | 2,097 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (2062 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
microsoft/amplifier-bundle-skills · 12 stars · license MIT · pushed 2026-09-23 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_q6r5d355hgwybhrc GET https://markdownregistry.com/api/v1/resolve?ref=microsoft/amplifier-bundle-skills/session-debug GET https://markdownregistry.com/api/v1/blob/0216ffae3fd173477e1148a3974951dd0a164acdb2243646b7ca9ace33a1e776
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
More from microsoft/amplifier-bundle-skills
Every file in microsoft/amplifier-bundle-skills