Skip to content
Back to skills

Agent Support Matrix

ASecurity

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.

  • 890 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 4, 2026
ai-agentsrailsbackend

Security analysis

A100/100

Pro scans all 4 files and shows the line behind each finding

Scanned September 4, 2026

npx -y skills add jazzyalex/agent-sessions --skill agent-support-matrix --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Agent Support Matrix?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Agent Support Matrix
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/jazzyalex-agent-support-matrix/badge)](https://www.skillsdirectory.com/skills/jazzyalex-agent-support-matrix)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
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*.

Files in this skill

  • SKILL.md2.3 KB
  • references/impact-scan.md1.5 KB
  • references/matrix-schema.md1 KB
  • references/update-checklist.md404 B

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.