docs(predict-rlm): refresh README developer framing#51
Open
ereinach wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Rationale
The README should quickly explain why a regular developer would reach for predict-rlm, while avoiding claims that go beyond what the current code supports. This refresh makes the opening more concrete, clarifies good-fit use cases, and tightens feature wording around files, multimodal support, skills, traces, and the SBX extra.
Summary
predict-rlm[sbx]extra before using the Docker Sandboxes backend.Test Plan
git diff --checkuv run --extra sbx python -c "from predict_rlm import File, PredictRLM, SbxConfig, SbxPool; from predict_rlm.skills import pdf, spreadsheet, docx; print('README API imports ok with sbx extra')"