superloopy-research

Solid

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.

AI & Automation 107 stars 16 forks Updated today MIT

Install

View on GitHub

Quality Score: 87/100

Stars 20%
68
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# 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 ...

Details

Author
beefiker
Repository
beefiker/superloopy
Created
2 months ago
Last Updated
today
Language
JavaScript
License
MIT

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category