skill-documenter-compatibilite

To document environment constraints and dependencies for agent skills, you record portable compatibility notes that validate required runtimes, CLIs, and local assumptions without altering the central frontmatter. This standardizes environment metadata while preserving skill portability across runtimes.

The best way to track compatibility notes across Codex, Claude, and OpenCode runtimes is to maintain a portable metadata trail that clearly separates platform-specific notes. This captures tool compatibility and optional integrations without polluting the core skill definition.

Yes, you can add platform-specific documentation without modifying a skill's central frontmatter by recording a portable compatibility note externally. This approach provides a shareable metadata trail across runtimes while keeping the core skill definition clean and unaltered.

You validate required runtimes and CLI assumptions for a skill by applying standardized compatibility documentation that checks environment hypotheses. This process records any experimental metadata when present and confirms the necessary local environment setup.

Skill portability breaks across different agent runtimes when environment assumptions, dependencies, and compatibility notes are undocumented or pollute the central frontmatter. Standardizing these records separately ensures skills remain portable across Codex, Claude, and OpenCode.