agent-support-matrix
The agent-support-matrix skill maintains an Agent Sessions compatibility tracking system that documents which upstream agent versions are verified to work with the session parser. Use this skill when reviewing new agent releases to update the support matrix documentation, running compatibility checks against the agent-watch monitoring script, and ensuring all version bumps are backed by test fixtures and passing parser tests before recording them in the official support matrix.
git clone --depth 1 https://github.com/jazzyalex/agent-sessions /tmp/agent-support-matrix && cp -r /tmp/agent-support-matrix/skills/agent-support-matrix ~/.claude/skills/agent-support-matrixSKILL.md
# Agent Support Matrix ## Overview Keep the support matrix and memory bank accurate, and gate updates with evidence so parsing regressions are avoided. ## Quick Start 1. Read `docs/agent-support/workflow.md`. 2. Run the session-format check and read `results.<agent>.compatibility`. 3. Compare latest available agent versions to `docs/agent-support/agent-support-matrix.yml`. 4. If gaps exist, run an impact scan, collect evidence, and update fixtures/tests before bumping `max_verified_version`. ## Workflow - Determine the current Agent Sessions version from `AgentSessions.xcodeproj/project.pbxproj` `MARKETING_VERSION`. - Run `./scripts/agent_watch.py --mode weekly` and use `compatibility.verdict` as the support answer. `severity` and `recommendation` are legacy escalation fields, not support claims. - Use `references/impact-scan.md` to inspect upstream releases for format changes. - Follow `references/update-checklist.md` before updating docs or fixtures. ## Guardrails - Do not bump `max_verified_version` without fixtures or sample logs plus passing parser tests. - Do not bump `max_verified_version` unless `results.<agent>.compatibility.verdict` is `supports_latest`, or the update explicitly records a narrower scope such as `supports_installed_only` with a blocker and follow-up. - If an agent does not log a version, keep `max_verified_version: "unknown"` and document verification scope in `docs/agent-json-tracking.md`. ## References - `references/matrix-schema.md` for matrix fields and update rules. - `references/impact-scan.md` for format change detection heuristics. - `references/update-checklist.md` for the evidence checklist. ## Related Skills - `agent-session-format-check` — detection and evidence collection for session format drift, usage/limits tracking changes, OpenCode storage backend shifts, and discovery path contract failures. Use that skill for *monitoring and diagnosis*; use this skill for *recording and gating version bumps*.
Use when shipping a release of Agent Sessions — bumping version, updating CHANGELOG, building, signing, notarizing, publishing appcast, and creating a GitHub release.
Create and ship AgentSessions support for a new or changed local AI agent/provider. Use when adding, reviewing, testing, documenting, or marketing a provider integration, session parser, transcript source, support-matrix entry, verified-version bump, or provider UI surface; drives the full loop from pre-support research through binary install, real session capture, fixture redaction, parser/discovery/search/UI integration, QA, review/fix loops, support records, PR/release notes, and conservative marketing claims.
Verify agent session format compatibility for Agent Sessions. Use when any agent CLI updates, when monitoring flags drift, or when bumping max verified versions (fixtures + docs + tests). Covers session schema, usage/limits tracking, storage backends, and discovery path contracts for all supported agents.
Capture deterministic macOS screenshots for testing, docs, release notes, and marketing assets. Use when asked to automate app screenshots, batch-generate screenshot sets, standardize window sizing/composition, or choose between Peekaboo and native macOS screenshot tooling.