skill-host-compat

原文涵盖的主题

• Skill Host Compatibility
• When to Activate
• Core Concepts
• Code Examples
• Anti-Patterns
• Best Practices
• Related Skills

Run the same host-compat gate CI uses on skills/ before opening a skill PR. The check is for Codex and Cursor copies, not Claude-only runtime quality. Adding or editing a skill under skills/ Copying a skill into .agents/skills/ or .cursor/skills/ A review asks whether a skill is safe to install into Codex or Cursor CI reports validate-skill-host-compat.js findings Canonical skills live in skills/. Codex loads .agents/skills/. Cursor loads a smaller .cursor/skills/ subset. CONTRIBUTING documents that sync as manual. validate-skills.js only checks that SKILL.md exists and that name / description are usable YAML. tests/ci/codex-skill-surface.test.js only sees .agents/skills/. This script is the cross-tree gate: 1. Claude-only substitutions in executable bash / sh / zsh fences in Codex/Cursor projections (${CLAUDESESSIONID}, ${CLAUDESKILLDIR}, ${CLAUDEPLUGINROOT}, ${CLAUDEPROJECTDIR}, $ARGUMENTS) fail. Codex leaves those tokens as literal text. In a Codex copy, rewrite ${CLAUDEPROJECTDIR} to $(pwd) or an explicit path. 2. A Codex copy may only use name, description, metadata, license, and allowed-tools. origin: ECC may stay on the canonical skills/ copy and must be stripped on the Code

这里只展示节选，请以完整原文和当前要求为准。