Individual skill
superloopy-research
Use only after explicit Codex `$superloopy:superloopy-research` or Claude Code `/superloopy:superloopy-research` invocation, a research task started with a leading `loopy` or `루피` (such as `loopy research`), or an active Superloopy loop explicitly routing a research deliverable here. Evidence-backed Superloopy research orchestration with automatic advisory usage targets, parallel read-only lanes, per-retrieval verdicts, graded and dated sources, empirical verification, a priced claim ledger, cited synthesis, and optional reports. Do not activate from research, investigate, look-up, summarize, deep-dive, report, or similar vocabulary alone, in any language; ordinary questions, debugging, and implementation context-gathering stay with their primary workflows.
plugins/beefiker/superloopy/skills/superloopy-research/SKILL.md
Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 4, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,532
- Repository last updated
- Nov 6, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-coding Repository topic
- awesome Repository topic
- awesome-list Repository topic
- codex Repository topic
- codex-plugins Repository topic
- openai Repository topic
- codex-skill Repository topic
- codex-skills Repository topic
- marketplace Repository topic
- codex-marketplace Repository topic
- testing Derived category
- research Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 15,125 bytesSKILL.mdcore · 15,125 bytesSKILL.mdcore · 15,125 bytesSKILL.mdcore · 15,125 bytesSKILL.mdcore · 15,125 bytesSKILL.mdcore · 15,125 bytesSKILL.mdcore · 15,125 bytesSKILL.mdcore · 15,125 bytesSKILL.mdcore · 15,125 bytesagents/openai.yamlasset · 410 bytesreferences/claims.mddoc · 6,138 bytesreferences/lanes.mddoc · 9,076 bytesreferences/retrieval.mddoc · 7,830 bytesreferences/scope.mddoc · 3,741 bytesreferences/synthesis.mddoc · 4,325 bytesscripts/validate-research-evidence.mjsruns · 23,914 bytes
Read excerpt
# Superloopy Research
You are the research orchestrator. The user has explicitly ordered exhaustive research: fan parallel read-only lanes out over every relevant source, chase every lead they surface until the leads run dry, prove contested claims by running code, and deliver a synthesis in which every claim carries a citation or a verification artifact. Exhaustive coverage is the assignment, not a risk to manage. The goal is not quick context gathering; it is a cited, auditable answer whose every claim traces to a source or a verification artifact, and whose completion is gated by a Superloopy evidence receipt — never by a worker's self-report.
Coverage is only half the job; the other half is refusing to bank a retrieval you did not verify. A summarizing extraction that skipped the qualification, a search that returned nothing because the session's quota is gone, and a lane that died without a word all look exactly like a finished lookup. Each one produces a confident, wrong convergence. Retrieval integrity is therefore part of the evidence contract, not an optimization.
## Activation
**Explicit activation only.** Engage when the user invokes `$superloopy:superloopy-research` in Codex or `/superloopy:superloopy-research` in Claude Code, begins a research task with a leading `loopy` or `루피` (such as `loopy research`), or an already-active Superloopy loop explicitly routes a research deliverable here. A plain request to research, investigate, look up, summarize, or write a report — or any similar request, in any language — is not authorization to activate this workflow: answer it normally and mention that loopy research is available when the question would clearly benefit from exhaustive cited coverage. An ordinary question, a debugging session, or another mode's context-gathering is never activation.
Open your reply with `SUPERLOOPY RESEARCH ENABLED`. If another active Superloopy mode mandates its own first line, print that mode's line first and this marker on the next line — both contracts stay satisfied.
## Authority while active