القائمة
Audit an entire plugin directory for cross-vendor readiness — walks all artifacts (skills, agents, MCP, hooks, startup context) and reports issues by vendor and priority.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Copy processed MP3s and WAVs to NAS storage. Use after Apple Music import or when re-archiving corrected files.
Move processed ZIPs to archive and clean up extraction folders. Use after album processing is complete.
Copy finished MP3s into Apple Music via the auto-import folder and verify the album lands correctly. Use once metadata is finalized and the user wants tracks added to their library — e.g. "add this to Apple Music" or "import these tracks" — even if they don't say "auto-import" explicitly. Also use to diagnose a bad import, e.g. "it showed up as separate tracks instead of one album."
Inspect and update MP3 tags: genre, artist, album, track count, compilation flag. Use when checking or fixing music file metadata — including diagnostic questions like "why do these show up as separate tracks" or "is this folder's metadata consistent," not just explicit tag-editing requests.
End-to-end processing of downloaded music purchases: extract ZIPs, verify metadata, import to Apple Music, archive to NAS, clean up. Use when processing new music downloads.
Reclaim local disk by offloading cloud-backed Apple Music downloads. Audit iCloud status, build an offload playlist that protects your DJ crates and lossless files, then Remove Download. Use when the Mac is low on disk.
| name | plugin-audit |
| description | Audit an entire plugin directory for cross-vendor readiness — walks all artifacts (skills, agents, MCP, hooks, startup context) and reports issues by vendor and priority. |
Use this skill when you want to know: "is this plugin ready to ship to all three vendors?" It walks every artifact in a plugin directory and applies the relevant artifact skill validator to each, then produces a consolidated per-vendor report.
Manifests — check for .claude-plugin/plugin.json, .cursor-plugin/plugin.json, .ynh-plugin/plugin.json, .codex-plugin/plugin.json. Note any missing vendor manifests. Check required fields per vendor.
Skills (skills/*/SKILL.md) — invoke skill-artifact for each. Check: frontmatter, description length, metadata demotion risk, directory layout.
Agents (agents/*.md) — invoke subagent-artifact for each. Check: frontmatter fields, vendor support (Codex has none), delegation assumptions.
MCP (.mcp.json, mcp.json) — invoke mcp-artifact. Check: file location per vendor (dot vs no-dot), transport types used, vendor support.
Hooks (hooks/hooks.json) — invoke hooks-artifact. Check: event names (PascalCase vs legacy camelCase), event coverage per vendor, hook types used.
Startup context (CLAUDE.md, AGENTS.md, rules/, .cursorRules) — invoke startup-context. Check: correct files present per vendor, rules format (.md vs .mdc), @-import workaround for Claude.
Produce a table per vendor showing readiness:
Claude Code: ✓ ready | issues: [list]
Cursor: ✓ ready | issues: [list]
Codex: ✓ ready | issues: [list]
Then a prioritized issue list:
HIGH [artifact] description — affects: Claude/Cursor/Codex
MED [artifact] description — affects: Cursor
LOW [artifact] description — affects: all
Invoke directly on a plugin root:
harness-advisor will route here when a user asks about overall plugin compatibility rather than a specific artifact problem.