outrider-experimentationlisted
Install: claude install-skill remyxai/outrider
# Outrider experimentation — field guide
Ambient knowledge for using Outrider effectively on target repos: from dispatch to upstream. All commands here are ones I've actually used in practice; nothing speculative.
## When to use
- Setting up Outrider on a new target repo
- Dispatching a manual refinement / smoke run
- Diagnosing why a run downgraded to Issue or opened at a different outcome than expected
- Deciding whether an Outrider-drafted PR is ready to file upstream
- Cross-checking a paper against existing coordination signals on the target repo
## Set up Outrider on a target repo
Fastest path — CLI-generated workflow with the right backend selected:
```bash
remyxai outrider setup-local --repo owner/name --backend moonshot
```
Backends: `anthropic` (default, Opus), `zai` (GLM), `moonshot` (Kimi K3). Setup-local prompts only for the selected backend's secret; add others manually via `gh secret set ANTHROPIC_API_KEY --repo owner/name < token.txt` for per-dispatch switching.
Manual install (when the CLI shape doesn't quite fit): copy the workflow YAML from `remyxai/outrider`'s `.github/workflows/outrider.yml` and thread the `interest-id` you get from `remyxai interests get -f json`.
## Trigger manually
```bash
# Fresh recommend (let selection pass pick)
gh workflow run outrider.yml --repo owner/name --ref main
# Pin to a specific paper (skip selection)
gh workflow run outrider.yml --repo owner/name --ref main \
-f pin-arxiv=2509.09675v1 \
-f provider=moonsho