# Loopx Auto Research

Use when a LoopX worker is operating an auto-research lane, demo pane, frontier item...

- Repository: https://github.com/loopx-project/loopx (6526 stars)
- Category: Writing
- License: Apache-2.0
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add loopx-project/loopx --skill loopx-auto-research -g -a claude-code -y`
Codex: `npx skills add loopx-project/loopx --skill loopx-auto-research -g -a codex -y`
Cursor: `npx skills add loopx-project/loopx --skill loopx-auto-research -g -a cursor -y`
Gemini CLI: `npx skills add loopx-project/loopx --skill loopx-auto-research -g -a gemini-cli -y`

## Description

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, artifact contracts, and stop conditions.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# LoopX Auto Research

This is a worker-local role playbook for auto-research panes. It is packaged
with the auto-research capability and should be injected or referenced by the
worker launcher; it is not a global LoopX skill for ordinary project agents.

## Routing Boundary

Use this skill after a LoopX auto-research worker has a role profile,
frontier item, launcher packet, or user-visible demo pane. The skill is the
role playbook. It is not the source of truth for identity, authority, current
frontier, or merge/publication permission.

Identity comes from LoopX control-plane metadata:

- `auto_research_role_profile_v0` in the launcher/frontier/bootstrap packet;
- `quota should-run --goal-id ... --agent-id ...`;
- todo claim, capability token, write scope, and protected scope;
- repository or workspace `AGENTS.md` rules, which can only make the boundary
  stricter.

No role owns the full graph. Do not infer role from pane title, branch name,
tmux window name, or the section of this skill that happens to be visible.

## Pane Tick Contract

The generic multi-agent kernel owns the default LoopX project/doc-registry
skills and the fixed A2A wake prompt. This skill should stay role-specific:
use it after the pane-local tick has resolved identity, quota, and frontier
from LoopX.

Compact frontier command: `loopx --format json auto-research frontier --goal-id "$LOOPX_GOAL_ID" --agent-id "$LOOPX_AGENT_ID"`. Also honor `quota should-run`.

If the launcher exported `LOOPX_ROLE_ID`, `LOOPX_ROLE_PROFILE_REF`, or a profile
JSON path, compare those values with the quota and frontier packets. Stop when
they disagree. Do not guess the intended role.

The rest: https://github.com/loopx-project/loopx/blob/HEAD/demo/auto_research/worker_skill/SKILL.md