RevenueCat / RevenueCat/ai-toolkit

Plugin not recognized after installation — skills not available

Open
#3 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
JavaScript
Stars
69
Forks
9
Avg merge
16h 49m
Merged PRs (30d)
5

Description

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.

  1. Environment

    1. Platform: macOS (Darwin 24.6.0)
    2. SDK version: rc-claude-code-plugin v1.0.0
    3. OS version: macOS 15 (Sequoia)
    4. Device and/or simulator:
      • Device
      • Simulator
      • N/A — this is a Claude Code CLI plugin issue
    5. Environment:
      • Sandbox
      • Production
      • N/A — plugin installation issue, not SDK runtime
    6. 100% — reproduced on every attempt across all three installation methods.
  2. 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
  1. Steps to reproduce, with a description of expected vs. actual behavior

Steps:

  1. Run: curl -fsSL https://raw.githubusercontent.com/RevenueCat/rc-claude-code-plugin/main/install.sh | bash
  2. Installation completes successfully
  3. Restart Claude Code (start a new session)
  4. 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.

  1. 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.json updated — skills not recognized
  • Method 2 (--plugin-dir flag): claude --plugin-dir ~/.claude/plugins/rc-claude-code-plugin — skills not recognized
  • Method 3 (manual settings.json): Added to plugins array manually — skills not recognized

Additionally tried:

  • Adding "rc@rc-claude-code-plugin": true to enabledPlugins in settings.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.

  1. Additional context

This may be related to known Claude Code issues with plugin/skill loading:

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. 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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.