Prune unverified skills

Author: Winlifes

.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "funplay-skill",
-  "version": "0.2.0",
+  "version": "0.3.0",
   "description": "Game-development skills library for coding agents.",
   "repository": "https://github.com/FunplayAI/funplay-skill",
   "homepage": "https://github.com/FunplayAI/funplay-skill",

.cursor-plugin/plugin.json

@@ -2,7 +2,7 @@
   "name": "funplay-skill",
   "displayName": "FunPlay Skill",
   "description": "Game-development skills library for coding agents.",
-  "version": "0.2.0",
+  "version": "0.3.0",
   "author": {
     "name": "FunplayAI"
   },

.gitignore

@@ -1,11 +1,12 @@
+.DS_Store
 node_modules/
+.pnpm-store/
 dist/
 .turbo/
 .cache/
 .env
 .env.local
 coverage/
 tmp/
+temp/
 *.log
-.DS_Store
-

.opencode/INSTALL.md

@@ -25,6 +25,6 @@ OpenCode updates Git plugins on restart. Pin a version by adding a tag:
 
 ```json
 {
-  "plugin": ["funplay-skill@git+https://github.com/FunplayAI/funplay-skill.git#v0.2.0"]
+  "plugin": ["funplay-skill@git+https://github.com/FunplayAI/funplay-skill.git#v0.3.0"]
 }
 ```

CHANGELOG.md

@@ -6,6 +6,17 @@ This project follows a simple changelog format inspired by Keep a Changelog, and
 
 ## [Unreleased]
 
+## [0.3.0] - 2026-05-21
+
+### Changed
+
+- Updated `unity-mcp-workflow` from the latest `FunplayAI/funplay-unity-mcp` default project skill guidance.
+- Tightened the skill validation policy so shipped skills must have tests/scripts, verified upstream provenance, or be a required meta-routing skill.
+
+### Removed
+
+- Removed unverified advisory skills and their command wrappers until they have a validation surface.
+
 ## [0.2.0] - 2026-04-30
 
 ### Added

README.md

@@ -4,7 +4,7 @@ FunPlay Skill is a game-development skills library for coding agents, inspired b
 
 ## What this repository is
 
-- A multi-agent skills library for game-development workflows
+- A verified multi-agent skills library for game-development workflows
 - A Claude Code / Cursor plugin with native skills, commands, and hooks
 - A Codex, OpenCode, and Gemini compatible repository with install guides
 - A collection of local asset-processing workflows under `skills/`
@@ -15,16 +15,8 @@ FunPlay Skill is a game-development skills library for coding agents, inspired b
 - `skills/sprite-sheet`: split one sprite sheet into numbered frame images
 - `skills/normal-map`: generate a normal map from a diffuse texture
 - `skills/audio-format-convert`: convert audio between `wav`, `ogg`, and `mp3`
-- `skills/texture-atlas`: plan atlas packing, naming, and manifest output for UI or 2D art
-- `skills/ui-slicing-checklist`: review UI sprites for slicing, nine-patch, and export readiness
-- `skills/game-audio-polish`: review game audio assets for loudness, looping, and implementation readiness
 - `skills/using-funplay-skills`: onboarding and usage guidance for the library
-- `skills/gameplay-prototyping`: turn a rough game idea into a prototype-ready spec
-- `skills/level-design-review`: review flow, readability, and encounter pacing
 - `skills/unity-mcp-workflow`: use Funplay Unity MCP as the edit, compile, Play Mode, screenshot, and readback loop
-- `skills/unity-prefab-workflow`: safely edit Unity prefabs, scenes, and serialized assets
-- `skills/godot-scene-assembly`: structure Godot scenes and resources cleanly
-- `skills/cocos-component-workflow`: organize Cocos Creator prefabs, scripts, and assets
 - `hooks/`: session-start context injection
 - `commands/`: lightweight slash-command wrappers that route users to the right skill
 - `docs/skill-spec.md`: canonical skill authoring rules
@@ -82,33 +74,21 @@ CI runs the same test and workspace validation commands.
 - `sprite-sheet`: `node skills/sprite-sheet/scripts/slice.mjs <image> <rows> <cols>`
 - `normal-map`: `node skills/normal-map/scripts/generate.mjs <image>`
 - `audio-format-convert`: `node skills/audio-format-convert/scripts/convert.mjs <input> <format>`
-- `texture-atlas`: ask the agent to plan how sprites should be grouped, padded, and named in an atlas
-- `ui-slicing-checklist`: ask the agent to review UI exports before engine import
-- `game-audio-polish`: ask the agent to review SFX or music for loudness, loop quality, and implementation concerns
-- `gameplay-prototyping`: ask the agent to turn a game idea into a shippable prototype plan
-- `level-design-review`: ask the agent to critique level goals, player guidance, and combat/readability loops
 - `unity-mcp-workflow`: use when a Unity project is connected to Funplay MCP and needs compile, Play Mode, screenshot, hierarchy, console, or prefab/scene readback verification
-- `unity-prefab-workflow`: use when touching Unity YAML assets, prefabs, or scenes
-- `godot-scene-assembly`: use when organizing Godot `.tscn`, nodes, and exported resources
-- `cocos-component-workflow`: use when editing Cocos Creator prefabs, components, and asset references
 
 ## Commands
 
-- `/brainstorm-game`: route a rough idea into `gameplay-prototyping`
-- `/write-game-plan`: turn an approved concept into implementation tasks
-- `/review-level`: route a level layout or encounter review into `level-design-review`
 - `/engine-workflow`: choose the right engine-facing skill before editing project files
-- `/prototype-loop`: tighten a gameplay loop into a prototype slice
-- `/review-encounter`: critique a combat, puzzle, or traversal encounter
 - `/engine-safe-edit`: choose the safest engine-facing workflow before asset or scene edits
 
 `audio-format-convert` requires `ffmpeg` in `PATH`. The image skills require the `sharp` dependency installed from this repo.
 
 ## Philosophy
 
-- Skills should be deterministic and easy for an agent to compose
+- Skills should be deterministic or backed by a verified upstream workflow
 - Metadata should tell the agent exactly when and how to use a skill
 - Local asset workflows are preferred over remote-service coupling in this repo
+- Pure advisory skills without tests, scripts, or upstream verification should stay out until they have a validation surface
 
 ## Git remote
 

commands/README.md

@@ -2,12 +2,7 @@
 
 This repository follows a skills-first approach similar to `superpowers`. Commands are thin wrappers that help users discover the right skill quickly.
 
-- `brainstorm-game.md`: start prototype discovery before implementation
-- `write-game-plan.md`: turn a validated game idea into a concrete task list
-- `review-level.md`: review pacing, readability, and player guidance
 - `engine-workflow.md`: choose the correct engine-facing skill, including Unity MCP when live editor verification is available
-- `prototype-loop.md`: tighten a core gameplay loop for the first playable
-- `review-encounter.md`: evaluate encounter pacing, readability, and pressure
 - `engine-safe-edit.md`: route file edits through the safest engine-specific workflow and validation loop
 
 Keep commands short. Put the actual workflow rules in `skills/`.

commands/brainstorm-game.md

@@ -8,6 +8,6 @@ Then:
 
 1. Determine whether the project is Unity, Godot, or Cocos Creator.
 2. Route Unity projects connected to Funplay MCP to `unity-mcp-workflow` when live editor readback, compilation, Play Mode, screenshots, or console logs are needed.
-3. Route Unity serialized file-only work to `unity-prefab-workflow`, Godot work to `godot-scene-assembly`, and Cocos Creator work to `cocos-component-workflow`.
+3. For Unity without MCP, Godot, or Cocos Creator, say there is no verified FunPlay skill currently available and continue with normal cautious repository inspection.
 4. Ask the user to confirm high-risk editor-generated files before broad edits.
 5. End with a short verification checklist for the chosen engine.

commands/engine-safe-edit.md

@@ -8,6 +8,4 @@ Then:
 
 1. Ask which engine or project type is in scope if it is not already obvious.
 2. Use `unity-mcp-workflow` when a Unity project is connected to Funplay MCP and live editor verification is needed.
-3. Use `unity-prefab-workflow` for Unity scenes, prefabs, materials, and serialized assets when MCP is not the main loop.
-4. Use `godot-scene-assembly` for Godot scenes, nodes, resources, and exported properties.
-5. Use `cocos-component-workflow` for Cocos Creator prefabs, components, and asset references.
+3. For non-Unity-MCP engine work, say there is no verified FunPlay skill currently available and continue with normal project-specific inspection.