القائمة
Determine where a harness artifact originated — tries multiple provenance strategies in order and returns the source repo, path, and ref when found.
التثبيت باستخدام 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 | locate-artifact-source |
| description | Determine where a harness artifact originated — tries multiple provenance strategies in order and returns the source repo, path, and ref when found. |
Use this skill to trace a harness artifact back to its origin. Try strategies in order, stop at the first that yields a clear result.
Strategy 1: YNH
Run: ynh ls --format json
Look for the harness containing the artifact. Extract: installed_from.source, installed_from.path, installed_from.ref_installed.
Works when: artifact was installed via a YNH harness.
Strategy 2: Claude Code native plugin
Check: ~/.claude/plugins/ and .claude/plugins/ in the project
Look for a plugin directory matching the artifact name. Read its manifest for source repo.
Works when: artifact was installed directly via Claude Code marketplace.
Strategy 3: Cursor native plugin
Check: ~/.cursor/plugins/ and .cursor/plugins/ in the project
Look for a plugin directory matching the artifact name. Read its manifest.
Works when: artifact was installed directly via Cursor marketplace.
Strategy 4: Codex plugin cache
Check: ~/.codex/plugins/cache/
Look for a plugin directory matching the artifact name.
Works when: artifact was installed via Codex plugin system.
Strategy 5: Git provenance
Run: git log --follow -1 --format="%H %s" -- <artifact-file-path>
Get the commit that introduced the file. Then: git remote -v to find the origin remote.
If origin is on GitHub: extract owner/repo from remote URL.
Works when: artifact is in the current git repo (embedded, not installed externally).
Note: if found in current repo, check if this is a worktree — fix should go to the canonical branch, not the worktree.
Strategy 6: Manifest walk
Walk up the directory tree from the artifact's location looking for .claude-plugin/, .cursor-plugin/, .ynh-plugin/, or package.json with a name field.
Read the manifest to find source repo reference.
Works when: artifact is part of a locally cloned plugin.
Strategy 7: Ask the user All strategies failed or returned ambiguous results. Ask: "I wasn't able to automatically determine where this artifact came from. Do you know which repository it originated from?"
Output:
