Use RCH once to offload a build or collect
Scanned 9/12/2026
Install to Claude Code
npx -y skills add thedixitjain/the-mega-skill-library --skill rch --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Rch?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/thedixitjain-rch)More formats (shields.io, HTML) on the badges page.
---
name: rch
description: "Use RCH once to offload a build or collect"
category: ai-agents-and-harness
source_repo: hashgraph-online/awesome-codex-plugins
source_path: "plugins/boshu2/agentops/skills-codex/rch/SKILL.md"
source_url: https://github.com/hashgraph-online/awesome-codex-plugins/blob/HEAD/plugins/boshu2/agentops/skills-codex/rch/SKILL.md
---
# RCH — remote compilation specialist
RCH can offload one explicit compilation command or inspect the remote compiler
path. This skill reports what happened; it does not govern retries or repair.
Staged diagnosis works because the offload pipeline fails in order —
availability, configuration, hook, classification, sync, remote compile,
worker pressure — so the first failing stage localizes the fault and every
later stage is noise until it passes. Remediate in irreversibility order:
read-only probes and config inspection before daemon restarts, restarts before
cleanup, and destructive cleanup or worker mutation only with explicit caller
authority.
Named failure mode — **green-local blindness**: a passing `[RCH] local (...)`
build read as offload success; the local fallback hid that the remote claim
was never proved.
Anti-pattern: re-running the build hoping the fallback reason disappears.
Corrective: read the recorded fallback reason and fix that stage; the pipeline
fails deterministically, not moodily.
## Procedure
1. Capture `rch check`, `rch doctor --json`, worker status, and the relevant
`[RCH]` summary before mutation.
2. For diagnosis, identify the first failing stage: availability, configuration,
hook, classification, sync, remote compile, or worker pressure.
3. Run only the caller-authorized command or documented safe diagnostic once.
4. Capture the exact command, worker when known, exit code, local-fallback reason,
and post-action status.
5. Stop and return the evidence.
`[RCH] local (...)` means the requested remote-offload claim was not proved even
when the local build succeeds. Destructive cleanup, worker deployment, daemon
configuration, and remote mutation require explicit caller authority.
## Output
Return a factual packet with status (`remote`, `local_fallback`, `failed`, or
`not_proven`), commands and exit codes, worker, summary line, and checked/not
checked surfaces. Do not include a next action.
## References
- [Fail-open reasons](references/FAIL_OPEN.md)
- [Error catalog](references/ERROR_CODES.md)
- [Troubleshooting](references/TROUBLESHOOTING.md)
- [Recovery playbooks](references/RECOVERY_PLAYBOOKS.md)
- [Worker operations](references/WORKERS.md)
- [Configuration](references/CONFIGURATION.md)
- [Machine-readable surfaces](references/MACHINE_INTROSPECTION.md)
---
**Source:** [`hashgraph-online/awesome-codex-plugins`](https://github.com/hashgraph-online/awesome-codex-plugins) → `plugins/boshu2/agentops/skills-codex/rch/SKILL.md`
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!