feat(plugin): Claude Code plugin marketplace install (/plugin install)

[yya007]

Summary

Makes SkillFinder installable as a Claude Code plugin in two commands, and reworks the README install accordingly.

/plugin marketplace add yya007/SkillFinder
/plugin install skill-finder@skillfinder

• .claude-plugin/marketplace.json — the repo is its own marketplace (name: skillfinder) listing one plugin (skill-finder, source: "./").
• .claude-plugin/plugin.json — the plugin manifest (name/version/description/author/license). The single root SKILL.md is auto-discovered as the plugin's skill (per the Claude Code single-skill-at-root convention).
• README — install section now leads with the Claude Code /plugin flow; Codex/OpenClaw keep the skills-directory install (npx skills add or npm i -g + copy). Finish-setup lists the pip deps explicitly (numpy faiss-cpu requests pyyaml) so it's path-independent for plugin installs (which land in the plugin cache).
• Root plugin.json (the npm / skills.sh path) refreshed: version 0.1.0 → 0.1.2, "33,000+" → "42,000+".

Schema confirmed against the official Claude Code plugin/marketplace docs.

Notes

• /plugin install copies files but does not run setup, so the README documents the post-install pip install … + ollama pull … step.
• The plugin source is the whole repo (./), so a plugin install includes the committed data/ index (~94 MB) — heavier than the trimmed npm package, but self-contained and works offline.
• .claude-plugin/ is not shipped in the npm package (files list unchanged); the two install paths (npm/skills-dir vs Claude Code plugin) coexist.

Verification

• All three manifests are valid JSON; pytest 579 passed; ruff clean.
• .claude-plugin/ is trackable (not caught by the .claude/ gitignore).
• Not end-to-end testable here (needs a Claude Code client) — manifests follow the documented schema.

Risk & rollback

Low — additive manifests + docs; no runtime/index/test change. Rollback = revert.

🤖 Generated with Claude Code