platform-audit

Detect outdated AI IDE capability mappings and produce update plans for CataForge platform profiles.

133|9|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/lync-cyber/CataForge --skill platform-audit-lync-cyber
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: platform-audit
Source: https://github.com/lync-cyber/CataForge/tree/main/.cataforge/skills/platform-audit
Command: npx skills add https://github.com/lync-cyber/CataForge --skill platform-audit-lync-cyber

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps maintain CataForge's cross-platform AI IDE mappings by checking whether platform capabilities, hooks, agent formats, permissions, and model routing still match the latest official documentation.

Core Features & Use Cases

  • Platform Capability Audits: Compare current profile settings against updated tool, hook, and feature documentation for Claude Code, Cursor, Codex, and OpenCode.
  • Diff Analysis and Remediation: Identify outdated mappings, generate structured reports, and update profiles, tests, and related implementation files when platform behavior changes.
  • Compatibility Monitoring: Validate conformance for dispatch flows, hook matchers, agent frontmatter support, sandbox behavior, and other platform-specific integrations.
  • Use Case: When a platform ships a new release or renames a tool, this Skill pinpoints the affected mappings and tells you exactly what needs to change.

Quick Start

Audit the latest platform changes for the specified IDEs and tell me which profile.yaml entries, tests, and overrides need to be updated.

Frequently Asked Questions about platform-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect outdated AI IDE capability mappings after a platform release?

You can monitor cross-platform compatibility by validating conformance for dispatch flows, hook matchers, and sandbox behavior. The audit checks whether current profile settings match the latest official documentation to ensure platform-specific integrations remain stable.

How do I audit hook events and model routing across Claude Code and Cursor?

When a platform ships a new release or renames a tool, an audit pinpoints the affected mappings and generates a structured remediation report. It identifies exactly which profile entries, tests, and overrides need to be updated to restore conformance.

What is the best way to update agent profiles when platform behavior changes?

Before auditing conformance-sensitive mappings, you must gather current official documentation for Claude Code, Cursor, Codex, and OpenCode. This provides the baseline required to compare profile settings and validate platform-specific integrations.

Do I need official documentation to audit AI IDE dispatch behavior?

Yes, current official documentation is required to audit AI IDE dispatch behavior and model routing. The platform audit relies on comparing live profile configurations against these docs to validate conformance-sensitive mappings and identify outdated settings.