claude-rio

claude-rio solves the problem of inconsistent skill and command activation in Claude Code by adding explicit keyword-based matching. When you submit a prompt, it checks matcher files in your skills, agents, and commands, then suggests relevant tools to Claude using special JSON formatting. While Claude makes the final decision, this visibility significantly increases the probability that your skills, agents, and commands will be invoked when relevant. The system uses deterministic matchers—simple JavaScript functions that evaluate prompt keywords, file patterns, or conversation history—with zero dependencies and fast execution (~10-20ms when no matches). Operations teams benefit from reduced manual intervention and improved workflow efficiency by ensuring their custom tools are properly surfaced to Claude.

[{"step":"Define the workflow requirements","action":"Identify the skills, agents, and commands needed for your automation. For example, if automating a data pipeline, list the validation tools, anomaly detectors, and notification systems you want to include.","tip":"Use claude-rio's `--list-skills` and `--list-agents` flags to see available components. Match them to your workflow's needs."},{"step":"Configure the workflow","action":"Create a configuration file (e.g., `workflow_config.json`) with the required parameters. Include conditions for triggering the workflow, such as time-based schedules or event-based triggers (e.g., file uploads).","tip":"Test configurations in a staging environment first. Use `--dry-run` to validate the workflow without executing it."},{"step":"Activate the workflow","action":"Run claude-rio with the configuration file. For example: `claude-rio --activate --config workflow_config.json`. Monitor the initial execution to ensure all components are triggered correctly.","tip":"Enable logging with `--log-level debug` to capture detailed output for troubleshooting."},{"step":"Monitor and iterate","action":"Review the execution logs and adjust the workflow as needed. Use claude-rio's `--status` flag to check active workflows and their status.","tip":"Set up alerts for failures or anomalies by integrating with tools like PagerDuty or Slack. Use the `--alert-webhook` flag to configure notifications."},{"step":"Scale and optimize","action":"Once validated, deploy the workflow to production. Use claude-rio's `--schedule` flag to automate recurring runs (e.g., `--schedule \"0 2 * * *\"` for daily runs at 2 AM UTC).","tip":"Optimize performance by reviewing the execution time of each component. Replace slower components with more efficient alternatives if needed."}]