Skills are addressed by name. The router is the usual entry point:
Use $rust-router to route this Rust task, then help me untangle a
borrow-checker error in this handler.
When the pressure point is already obvious, call the relevant skill directly:
Use $rust-errors to review this error enum for a publishable library
crate.
The router is cheap to load. When a task spans more than one area — say, an async handler that also needs error-type advice — load the router first and let it pick the pairing.