shipkit-get-skills

# shipkit-get-skills - Skill & Plugin Discovery **Purpose**: Discover and install skills and plugins via conversational interface. **Core value**: Discovery through conversation, not CLI memorization. --- ## Two Distribution Channels | Source | Best For | Install Command | |--------|----------|-----------------| | **Official Plugins** | Git workflow, PR review, security, UI design | `/plugin install X@claude-code-plugins` | | **skills.sh** | Domain-specific skills (testing, docs, APIs) | `npx skills add owner/repo` | **When user asks "what's available":** - For plugins → Read `references/official-plugins.md` - For skills → Read `references/community-skills.md` --- ## Why This Skill Exists **You don't naturally know what skills exist in the ecosystem.** | Without Skill | With Skill | |---------------|------------| | User must know about skills.sh | User says "I need help with X" | | User runs CLI commands manually | Claude searches and offers to install | | User parses terminal output | Results presented conversationally | --- ## When to Invoke **User says:** - "Find skills for X" - "Is there a skill for testing?" - "I need help with commit messages" - "Get skills", "Search skills" - "Install a skill for API docs" - "What plugins are available?" - "Show me official plugins" - "Install the frontend-design plugin" **Auto-suggest when:** - User struggles with a task that likely has a community skill - User asks "is there a better way to do X?" **For catalog questio...