Repository navigation
Conversation
|
Nice addition. The URL contract using standard book abbreviations and OSIS-style references is clean and consistent with the existing skill conventions. One thought: for offline or rate-limited scenarios, would it make sense to mention in the description how the agent should fall back (e.g., suggesting the user open the link manually or using a local lookup)? The ?qr=true integration is a nice touch for mobile sharing. |
|
Thanks for the contribution. Closing as out of scope: this repo is the Claw Code CLI/runtime itself, and it doesn't ship third-party service skills. Please publish the route.bible skill in its own repository so users can install it themselves. PRs to the Claw Code CLI, runtime, or docs are very welcome. — |
|
Agreed — this repo is the CLI/runtime, so third-party service skills belong in their own repos. Publishing route.bible separately (with the OSIS-style reference contract) will make it installable without mixing concerns here. |
This PR adds the skill definition for route.bible, enabling the agent to handle app-agnostic Bible passage routing.