Skill Claude CodeCodex
Use when a LoopX worker is operating an auto-research lane, demo pane, frontier item, evidence packet, promotion/retirement decision, or visible tmux/Codex auto-research rehearsal. Identity must come from the LoopX role profile and quota/frontier packet; this skill only provides role-specific execution checklists…
Plugin Claude Code
Bundles 1 command, 1 hook · 53 tokens together
LoopX adapter for Claude Code: the loopx control-plane MCP (shouldrun / claimtask / completetask) + the /loopx setup command + statusline. The run loop is Claude Code's native /loop, driven by a .claude/loop.md that /loopx writes; the optional shouldrun PreToolUse gate (hooks/goalpolicy.py) is added deliberately v.
Skill Codex
Use when a LoopX-managed goal runs, tracks, scores, or analyzes a benchmark experiment through benchmark-toolkit, including experiment-board rows, solver arms, integrity qualification, matched comparisons, or case insights. Do not use for casual benchmark discussion, ordinary software microbenchmarks, or eval mentions…
Skill Codex
Qualify the exact final diff for a LoopX-managed goal. Use when goal policy enables changequalityqualification, before a non-trivial delivery or merge, and when producing or repairing an exact-scope quality receipt. The workflow is language-neutral, permits at most one policy-authorized safe-fix pass, and never grants…
Skill Codex
Use when a connected LoopX project is asked to read, remember, record, index, register, or use a durable project material such as a Lark/wiki/design doc, research note, SOP, owner packet, migration report, benchmark paper, or external material source. Use even when the user does not mention LoopX or doc registry.
Skill Codex
Operate an explicitly activated LoopX Material Lifecycle for a connected project. Use for material-store inventory, lossless migration, candidate/archive transitions, exact-read-backed ranking, ranked-entry rebuilds, bounded Explore intake, owner-gated apply, rollback, and audit. Do not use for ordinary one-off…
Skill Codex
Use when LoopX must manage a multi-PR or multi-MR delivery program across one or more repositories: inventory current change requests, reconcile new/merged/closed or retargeted work, preserve requirement and dependency priorities, maintain a roadmap document, or monitor material lifecycle/check/review changes over…
Skill Codex
Use for /loopx-pr-review or evidence-backed PR queue review. Run loopx pr-review first, execute the capability-owned review plan for each selected exact head, then publish full bilingual PR reviews (complete Chinese five-block review plus one concise English verdict) that match the verified findings. Use…
Skill Codex
Use when connecting a repository or project goal document to LoopX, maintaining project-local goal state, refreshing stale dashboard status, syncing local projects into the shared global registry, or diagnosing LoopX CLI/PATH/status/history issues across multiple repos. For registering durable project materials such…
Skill Codex
Diagnose and repair LoopX control-plane drift or agent behavior drift. Use when a LoopX task makes unexpectedly small progress, follows a stale or contradictory recommendedaction, ignores a higher-priority blocked item while doing fallback work, reports vague owner/user gates, loses todo projection, misaligns…
Skill Claude CodeCodex
Migrate historical SWE-Marathon agent configurations to the shared Codex runtime.
Skill Claude CodeCodex needs its repo
A benchmark setup for comparing five ways of running a coding agent on Terminal-Bench 4.0, a fixed collection of terminal-based software tasks.
Skill Claude CodeCodex
Inspect authorized LoopX Goals, Todos and deliveries to explain progress, identify owner decisions and delegate intent to the right worker.
Skill Codex
Optional maintainer workflow for the approval, merge-readiness, or authorized self-merge decision on a LoopX pull request. Requires the exact-head review evidence from loopx pr-review. Review depth, verdicts, review comments, and the published review format belong to loopx-pr-review.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: