/agent-support-matrix
Maintain Agent Sessions agent support matrix and JSON/JSONL parsing compatibility. Use when checking upstream agent releases for session format changes, updating max verified versions in docs/agent-support/agent-support-matrix.yml, or updating docs/agent-json-tracking.md and
$ npx -y skills add jazzyalex/agent-sessions --skill agent-support-matrix --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/agent-support-matrix
Context preview
The summary Claude sees to decide when to auto-load this skill.
Maintain Agent Sessions agent support matrix and JSON/JSONL parsing compatibility. Use when checking upstream agent releases for session format changes, updating max verified versions in docs/agent-support/agent-support-matrix.yml, or updating docs/agent-json-tracking.md and
SKILL.md
agent-support-matrix.SKILL.mdname: agent-support-matrix
description: Maintain Agent Sessions agent support matrix and JSON/JSONL parsing compatibility. Use when checking upstream agent releases for session format changes, updating max verified versions in docs/agent-support/agent-support-matrix.yml, or updating docs/agent-json-tracking.md and fixtures/tests.
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*.
Read more
name: agent-support-matrix description: Maintain Agent Sessions agent support matrix and JSON/JSONL parsing compatibility. Use when checking upstream agent releases for session format changes, updating max verified versions in docs/agent-support/agent-support-matrix.yml, or updating docs/agent-json-tracking.md and fixtures/tests.
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*.
Live per-session quota burn for Codex and Claude — see which session is eating your 5-hour and weekly limits, priced per model.
Other skills on agent-sessions.
- /deploy
Use when shipping a release of Agent Sessions — bumping version, updating CHANGELOG, building, signing, notarizing, publishing appcast, and creating a GitHub release.
Open skill - /release-notes
Use when writing or curating the user-facing release copy for an Agent Sessions release — README "What's New", GitHub release notes, Sparkle release notes, or website/launch copy. Not for the internal CHANGELOG, which stays a full development history.
Open skill - /add-agent-support
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;
Open skill - /agent-session-format-check
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
Open skill - /sc-skill
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.
Open skill