On this page
Runbook
Separate failures by where they originate: form validation, executable resolution/process launch, CLI exit, or successful-output decoding.
Run is disabled
Paste the text to score.Paste the text to rewrite.Enter a RentAHuman humanization id.
Fill the required field with non-whitespace content. Rewrite numeric controls cannot leave their UI ranges.
CLI is not installed
skryba is not installed…
Run cargo install --path . in the CLI repository or place an executable skryba in a searched directory. For a Finder launch, remember its PATH can differ from Terminal; well-known Cargo, local, Stado, Homebrew, and /usr/local paths are searched independently.
If an executable moved after one run, the cached URL is rechecked and a new search occurs automatically.
skryba refused the workflow
The detail is CLI stderr verbatim. Follow the Skryba CLI runbook, not a desktop-specific translation. Common examples:
- no detector key: configure a detector variable;
- missing
BRAMA_TOKEN: required for Rewrite; - missing
RENTAHUMAN_API_KEY: required for Status; - bad detector or policy path: correct the UI field;
- network/provider failure after retries: inspect the nested CLI cause.
For Finder launches, put missing keys in ~/.config/skryba/env and relaunch. A launch-environment key wins over the file, so remove or correct stale exported values rather than expecting the file to override them.
skryba exited with status <n>.
The process returned nonzero without stderr. Reproduce the exact command from the Command panel in Terminal and supply the displayed workflow input on stdin for Score/Rewrite. This sentence is only the empty-stderr fallback.
JSON decoding failure after status 0
Score expects ai_probability and detectors[]; Rewrite expects text, chunks[], and all required nested candidate and quality fields. A zero-status CLI that emits another shape is incompatible with this desktop build.
Confirm which skryba executable resolves first on the app's search path. Install a matching CLI build. The app intentionally does not guess at changed fields.
RentAHuman Status cannot have this decoding failure because its stdout is displayed as a document string.
Long-running workflow
The loading panel says detector calls are rate-limited and cached and a long text can take minutes. The app drains stdout and stderr concurrently, so large output should not deadlock. There is no cancel button or app-level timeout; wait for the CLI's own bounded HTTP operations to finish.
Command panel differs from expectation
The panel shows argv only; pasted input is on stdin and never printed into the command. Detector options appear before the subcommand. Rewrite always includes --json and formatted numeric values. The executable is displayed by last path component, not absolute resolved path.
Maintained as part of the website-owned Skryba documentation corpus.