rdl-team

Delegate to this agent during Claude Code setup (local `/rdl-team:cc-setup`) when you need to discover what plugins are available across the RDL marketplace and the team's extra marketplaces, and decide which ones THIS repo should enable. It locates the team's tracked marketplace list, enumerates each marketplace's plugin catalog (live), inspects the repo's languages and tooling, and returns a ranked suggestion set: the always-useful baseline (pr-review-toolkit, gh@rdl-agent-extensions, worktrunk, the applicable LSP) plus language/stack-matched picks, each with id, marketplace, and a one-line reason. It only researches and recommends — it does not install or edit settings.

Onboard a user onto the RDL team's Claude Code setup. Use when the user wants to "set up Claude Code", "set up my .claude", "onboard onto the RDL Claude Code setup", "install the forced-eval hook", or "configure Claude Code for the team". Asks whether to configure a project-local `.claude/` or the user's global `~/.claude/`, then installs the team's `forced-eval-hook.sh` (a UserPromptSubmit hook that surfaces available skills as advisory context) and wires it into the chosen scope's `settings.json` idempotently. The minimal first step of RDL Claude Code onboarding — later passes will guide the wider settings surface.

Create a new service desk issue from available templates. Use when creating GitHub issues for the RDL Service Desk repository with data request, enquiry, or ICT request templates.