Addition of New Skill: wp-vip-platform (WordPress VIP / VIP Go) #93

None of the existing skills cover the WordPress VIP platform specifically. Most VIP Learn course topics (Enterprise Security, Enterprise Performance, Debugging, REST API, Block Editor) already map onto existing skills (wp-plugin-development, wp-performance, wp-rest-api, wp-block-development), but VIP Go has a set of hard platform constraints that are specific to VIP and produce wrong or broken advice if an agent applies generic WordPress patterns to a VIP repo:

• Web-tier filesystem is read-only except /tmp/ — generic "just write the file" advice breaks in production.
• A PHPCS ruleset (WordPressVIPMinimum) flags core functions that have wpcom_vip_* cached replacements (get_page_by_title, get_term_by, etc.) — an agent unaware of this will "fix" the flag incorrectly or suppress it.
• wp-cron.php is disabled — Cron Control runs scheduled events instead; debugging advice that assumes a wp-cron HTTP hit is wrong.
• Code deploys are git-based (Default Deployment via branch mapping, or Custom Deployment via VIP-CLI/external CI) — not FTP/rsync/direct edits.
• Page cache purging uses wpcom_vip_purge_edge_cache_for_{url,post,term}(), and purges are async (queued to shutdown).
• Enterprise Search is a VIP-specific ElasticPress fork, not vanilla Elasticsearch/ElasticPress.
• VIP-CLI (vip dev-env ..., vip logs, vip cache purge-url) is a distinct tool from plain WP-CLI.

Scope

In scope:

• Detecting whether a repo targets VIP (vip-config/, client-mu-plugins/, .vipignore, wpcomvip/* composer requires).
• Read-only filesystem / VIP File System constraints fo
• WordPressVIPMinimum restricted-function guidance and replacements.
• VIP's page cache + object cache behavior and purge AP
• Cron Control vs wp-cron.php.
• Default vs Custom code deployment.
• Enterprise Search (Elasticsearch) at a "how to reason about it" level.
• VIP-CLI and the VIP Local Development Environment.

Out of scope (routed elsewhere or to VIP Support):

• Generic WordPress security/performance/REST content already covered by wp-plugin-development, wp-performance, wp-rest-api.
• Activating VIP integrations (Enterprise Search, etc.)erritory, not a code change.
• Infrastructure/scaling decisions.

Let me know if i can go ahead with this, Thanks!