[Bug] Marketplace plugin skills unreachable in scheduled cloud routines despite successful install and enabled status

Status Open
Reported on v2.1.210
Maintainer reply None cached
Activity 0 comments · opened Jul 16, 2026

Bug Description
Title: Marketplace plugin skills are unreachable (Unknown skill) in scheduled cloud routines (CCR), even after a successful plugin install

Summary: A marketplace plugin installed via claude plugin marketplace add + claude plugin install shows up as enabled: true in ListPlugins, but its skills never appear in ListSkills,
and direct invocation via the Skill tool fails with Unknown skill — every time, across three independent scheduled-routine runs. The plugin is genuinely installed and enabled; its
skills are structurally unreachable in that session regardless.

Environment: Claude Code scheduled cloud routines (CCR), created via RemoteTrigger//schedule (claude.ai/code/routines). Plugin: Anthropic's official "Marketing" plugin from the
anthropics/knowledge-work-plugins marketplace (marketing@knowledge-work-plugins v1.2.0). Model: claude-sonnet-5.

Steps to reproduce:

  1. Create a CCR routine whose prompt installs a marketplace plugin it doesn't already have.
  2. In the same session, after install reports success, invoke one of the plugin's skills (e.g. Skill({skill: "seo-audit"})).
  3. Observe ListSkills output and the invocation result.

Expected: Either the newly installed plugin's skills become invokable in the same session, or plugin install/ListSkills clearly surfaces that a restart is required.

Actual: ListPlugins shows enabled: true; ListSkills never lists the plugin's skills; direct Skill() calls for seo-audit, marketing:seo-audit, draft-content, content-creation,
marketing:draft-content, brand-review, competitive-brief, performance-report all return Unknown skill. Reproduced across 3 independent runs — including one where the plugin was
already enabled: true from a prior routine's successful install, ruling out a first-install-only race condition.

Impact: Marketplace plugins are effectively unusable in CCR automation — there's no interactive restart step available headlessly. Worth fixing the registration path, or documenting
the limitation so people don't burn routine runs discovering it.

Evidence (reproducible session links):

  • session_017LSh1UbSVFQjoCx9mMt15A — quarterly marketing-trajectory routine, first attempt
  • session_019e4cvZMpQZ6MpLswa7fbnB — one-time /seo-audit bake-off
  • session_01AguCSe4MndRtj6VSVg5UNB — /draft-content bake-off retry, run after the plugin was already confirmed installed from a prior run

Environment Info

  • Platform: darwin
  • Terminal: vscode
  • Version: 2.1.210
  • Feedback ID: 1e1249ba-a761-4db3-87d1-521504e68c07

Errors

[]

View original on GitHub ↗