`compatibility` field in copilot cli generate warning

[widoz]

I've installed the skills into a project under .github/skills. Copilot CLI complain about the compatibility field being unknown and as such it is ignored.

Down below you can see the warnings generated whenever I run /skills reload or /skills list.

● ⚠ The following skills have warnings:
    • .github/skills/wordpress-router/SKILL.md: unknown field ignored: compatibility
    • .github/skills/wp-abilities-api/SKILL.md: unknown field ignored: compatibility
    • .github/skills/wp-block-development/SKILL.md: unknown field ignored: compatibility
    • .github/skills/wp-block-themes/SKILL.md: unknown field ignored: compatibility
    • .github/skills/wp-interactivity-api/SKILL.md: unknown field ignored: compatibility
    • .github/skills/wp-performance/SKILL.md: unknown field ignored: compatibility
    • .github/skills/wp-phpstan/SKILL.md: unknown field ignored: compatibility
    • .github/skills/wp-playground/SKILL.md: unknown field ignored: compatibility
    • .github/skills/wp-plugin-development/SKILL.md: unknown field ignored: compatibility
    • .github/skills/wp-project-triage/SKILL.md: unknown field ignored: compatibility
    • .github/skills/wp-rest-api/SKILL.md: unknown field ignored: compatibility
    • .github/skills/wp-wpcli-and-ops/SKILL.md: unknown field ignored: compatibility
    • .github/skills/wpds/SKILL.md: unknown field ignored: compatibility

Skills are anyhow recognized correctly, 13 skills in total

Available Skills

  Project:
    • wordpress-router
      Use when the user asks about WordPress codebases (plugins, themes, block themes, Gutenberg blocks, WP core checkouts) and you need to quickly
  classify the repo and route to the correct workflow/skill (blocks, theme.json, REST API, WP-CLI, performance, security, testing, release packaging).
    • wp-abilities-api
      Use when working with the WordPress Abilities API (wp_register_ability, wp_register_ability_category, /wp-json/wp-abilities/v1/*,
  @wordpress/abilities) including defining abilities, categories, meta, REST exposure, and permissions checks for clients.
    • wp-block-development
      Use when developing WordPress (Gutenberg) blocks: block.json metadata, register_block_type(_from_metadata), attributes/serialization, supports,
  dynamic rendering (render.php/render_callback), deprecations/migrations, viewScript vs viewScriptModule, and @wordpress/scripts/@wordpress/create-block
  build and test workflows.
    • wp-block-themes
      Use when developing WordPress block themes: theme.json (global settings/styles), templates and template parts, patterns, style variations, and Site
  Editor troubleshooting (style hierarchy, overrides, caching).
    • wp-interactivity-api
      Use when building or debugging WordPress Interactivity API features (data-wp-* directives, @wordpress/interactivity store/state/actions, block
  viewScriptModule integration, wp_interactivity_*()) including performance, hydration, and directive behavior.
    • wp-performance
      Use when investigating or improving WordPress performance (backend-only agent): profiling and measurement (WP-CLI profile/doctor, Server-Timing,
  Query Monitor via REST headers), database/query optimization, autoloaded options, object caching, cron, HTTP API calls, and safe verification.
    • wp-phpstan
      Use when configuring, running, or fixing PHPStan static analysis in WordPress projects (plugins/themes/sites): phpstan.neon setup, baselines,
  WordPress-specific typing, and handling third-party plugin classes.
    • wp-playground
      Use for WordPress Playground workflows: fast disposable WP instances in the browser or locally via @wp-playground/cli (server, run-blueprint,
  build-snapshot), auto-mounting plugins/themes, switching WP/PHP versions, blueprints, and debugging (Xdebug).
    • wp-plugin-development
      Use when developing WordPress plugins: architecture and hooks, activation/deactivation/uninstall, admin UI and Settings API, data storage,
  cron/tasks, security (nonces/capabilities/sanitization/escaping), and release packaging.
    • wp-project-triage
      Use when you need a deterministic inspection of a WordPress repository (plugin/theme/block theme/WP core/Gutenberg/full site) including
  tooling/tests/version hints, and a structured JSON report to guide workflows and guardrails.
    • wp-rest-api
      Use when building, extending, or debugging WordPress REST API endpoints/routes: register_rest_route, WP_REST_Controller/controller classes,
  schema/argument validation, permission_callback/authentication, response shaping, register_rest_field/register_meta, or exposing CPTs/taxonomies via
  show_in_rest.
    • wp-wpcli-and-ops
      Use when working with WP-CLI (wp) for WordPress operations: safe search-replace, db export/import, plugin/theme/user/content management, cron, cache
  flushing, multisite, and scripting/automation with wp-cli.yml.
    • wpds
      Use when building UIs leveraging the WordPress Design System (WPDS) and its components, tokens, patterns, etc.

  Found 13 skills. Use /skills info <name> to view details.