jr-rpc

✓ Official★ 276

by getsentry · part of getsentry/junior

Manage low-level config and plugin introspection flows via jr-rpc bash commands. Use only when the user explicitly asks to read or update provider defaults/config or list installed plugins. Do not use for PR, branch, push, or auth-order questions; load the matching provider skill instead.

🧰 Not standalone. This skill ships with getsentry/junior and only works together with that tool — install the tool first, then add this skill.

This is the playbook your agent receives when the skill activates — you don't need to read it to use the skill, but it's here to audit before installing.

jr-rpc

Manage low-level config and plugin introspection flows for the current agent turn.

Plugins

jr-rpc plugins list — list installed plugins visible to the current Junior runtime.

Command syntax:

jr-rpc plugins list

Guardrails

Use exact config keys from the loaded skill or provider catalog; do not invent them.
Do not use this skill to choose a provider for an unrelated operational task. Load the matching domain skill first, then run the real provider command.
Do not print credential values.

Copy & paste — that's it

npx skills add https://github.com/getsentry/junior --skill jr-rpc

Run this in your project — your agent picks the skill up automatically.

Configuration

jr-rpc config get|set|unset|list — read and write channel-scoped configuration values.

Command syntax:

jr-rpc config get <key>
jr-rpc config set <key> <value> [--json]
jr-rpc config unset <key>
jr-rpc config list [--prefix <value>]

Rules:

Choose config keys from the runtime <providers> catalog: <provider>.<config_key>.
For "default repo" requests, use the provider target key, for example github.repo.
Run the exact standalone command. Do not probe, install, or repair jr-rpc; the runtime handles it only when invoked directly.