RevenueCat / RevenueCat/ai-toolkit
Plugin not recognized after installation — skills not available
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 69
- Forks
- 9
- Avg merge
- 16h 49m
- Merged PRs (30d)
- 5
Description
- I have updated Purchases SDK to the latest version (N/A — this is a Claude Code plugin issue, not a Purchases SDK issue)
- I have read the Contribution Guidelines
- I have searched the Community
- I have read docs.revenuecat.com
- I have searched for existing Github issues
Describe the bug
After installing the Claude Code plugin via the recommended install script, skills like /rc:status return Unknown skill: rc:status. The plugin is not recognized by Claude Code despite successful installation.
-
Environment
- Platform: macOS (Darwin 24.6.0)
- SDK version: rc-claude-code-plugin v1.0.0
- OS version: macOS 15 (Sequoia)
- Device and/or simulator:
- Device
- Simulator
- N/A — this is a Claude Code CLI plugin issue
- Environment:
- Sandbox
- Production
- N/A — plugin installation issue, not SDK runtime
- 100% — reproduced on every attempt across all three installation methods.
-
Debug logs
$ curl -fsSL https://raw.githubusercontent.com/RevenueCat/rc-claude-code-plugin/main/install.sh | bash
RevenueCat Claude Code Plugin — Installer
==========================================
Cloning plugin into ~/.claude/plugins/rc-claude-code-plugin...
Plugin cloned to ~/.claude/plugins/rc-claude-code-plugin
Added plugin to ~/.claude/settings.json
Installation complete!
# After restart, in Claude Code:
> /rc:status
Unknown skill: rc:status
- Steps to reproduce, with a description of expected vs. actual behavior
Steps:
- Run:
curl -fsSL https://raw.githubusercontent.com/RevenueCat/rc-claude-code-plugin/main/install.sh | bash - Installation completes successfully
- Restart Claude Code (start a new session)
- Run
/rc:status
Expected: The rc:status skill loads and displays RevenueCat connection status.
Actual: Unknown skill: rc:status — Claude Code does not recognize the plugin.
- Other information
The install script adds the plugin path to a plugins array in ~/.claude/settings.json:
"plugins": [
"~/.claude/plugins/rc-claude-code-plugin"
]
Claude Code v2.1.50 (well above the documented minimum of 1.0.33).
All three installation methods from the README were tried:
- Method 1 (install script): Plugin installs,
settings.jsonupdated — skills not recognized - Method 2 (
--plugin-dirflag):claude --plugin-dir ~/.claude/plugins/rc-claude-code-plugin— skills not recognized - Method 3 (manual
settings.json): Added topluginsarray manually — skills not recognized
Additionally tried:
- Adding
"rc@rc-claude-code-plugin": truetoenabledPluginsinsettings.json - Adding an entry to
~/.claude/plugins/installed_plugins.json - Neither resolved the issue
Other marketplace-installed plugins work fine on this system.
The plugin contents look correct — .claude-plugin/plugin.json is well-formed, skills/ directory contains status, apikey, create-app, create-product with proper SKILL.md files.
- Additional context
This may be related to known Claude Code issues with plugin/skill loading:
- https://github.com/anthropics/claude-code/issues/27332 — plugin skill references resolved against wrong directory
- https://github.com/anthropics/claude-code/issues/25072 — skills not loading from
~/.claude/skills/ - https://github.com/anthropics/claude-code/issues/20661 — mismatch between
installed_plugins.jsonandenabledPlugins
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with install.sh, .claude-plugin/plugin.json, the skills/*/SKILL.md files, and the README installation methods; compare their paths and metadata with a known marketplace-installed plugin. Reproduce the failure with the documented methods and verify that a fresh Claude Code session recognizes /rc:status; done means the cause is identified and a working installation path is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- cli, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100