Feature request: support enabledPlugins in Remote Triggers (CCR) so Routines can invoke registered skills by name

Problem

When creating a Remote Trigger (Routine) at claude.ai/code/routines, there is no way to specify which plugins/skills should be loaded in the CCR session. The job_config.ccr.session_context object supports sources, allowed_tools, and model — but not enabledPlugins or extraKnownMarketplaces.

As a workaround, teams must clone the entire skills repository as a git source and have the CCR agent read the SKILL.md file manually, then follow it as plain text. This is fragile and does not benefit from the skill execution infrastructure.

Expected behavior

The Remote Trigger API should support an enabledPlugins (or equivalent) field in session_context, so a CCR session can load a registered plugin and invoke skills as slash commands — the same way interactive Claude Code sessions do.

Proposed config shape:

{
  "job_config": {
    "ccr": {
      "session_context": {
        "model": "claude-sonnet-4-6",
        "enabledPlugins": {
          "sre-incident-analysis@recarga-skills": true
        },
        "extraKnownMarketplaces": {
          "recarga-skills": {
            "source": {
              "source": "github",
              "repo": "myorg/skills"
            }
          }
        }
      },
      "events": [...]
    }
  }
}

With this, the CCR agent could invoke:

/sre-incident-analysis --squad accounts --since "7 days ago"

...instead of reading a SKILL.md file from a cloned repo.

Current workaround

Clone the skills repo as a git source, add a prompt telling the agent to read the SKILL.md and follow it manually. This works but:

• Does not use the skill execution infrastructure
• Requires cloning large repos just to access skill definitions
• The agent re-reads and re-interprets the skill instructions every run instead of having them pre-loaded
• Makes the trigger prompt brittle (needs to reference internal file paths)

Use case

We maintain a private myorg/skills GitHub repo with 30+ skills registered in .claude-plugin/marketplace.json. These skills are used interactively by engineers via /skill-name in their local Claude Code sessions. We want to schedule the same skills as automated Routines — but today we have to duplicate the skill invocation logic in the trigger prompt rather than simply referencing the registered skill.

The gap: skills exist for interactive sessions, but are not integrated with the Routines/CCR automation system.