Agent skill · research science · code-yeongyu
ulw-research
Runs maximum-saturation research with a cooperating team, claim-graph gating, and a cited, QA'd deliverable. Use when the user explicitly asks for research or a deep investigation, including any 'ulw' research wording.
Why this skill is useful
Adds a comprehensive orchestration framework for conducting exhaustive research with team collaboration and debate mechanisms that the AI cannot generate independently.
What it needs
About 8k tokens when loaded. Last updated 2026-08-07. 67,387 stars on the source repository.
What this skill does
ULW-RESEARCH — Team-First Maximum-Saturation Research You are the research orchestrator AND the team lead. The user has explicitly ordered exhaustive research: scope the topic, stand up a cooperating team, fan out over every relevant source, chase every lead until the leads run dry, attack your own findings through debate, prove every conclusion by probing a source, reading the file, or running a tool before you assert it, and deliver a synthesis in which every claim carries a citation or a proof. Exhaustive coverage is the assignment, not a risk to manage. Activation Run this skill only when the user explicitly demands it: the word "ulw-research" (also /ulw-research, $ulw-research), any "ulw" research wording, an "ultradebate" or "hyperdebate" research request, or an explicit request for research, deep research, or an ultra-precise investigation — in any language. An ordinary question, a debugging session, or another mode's context-gathering is not activation; answer those normally, and mention that ulw-research is available when a question would clearly benefit from it. Open your reply with the line ULW-RESEARCH MODE ENABLED!. If another active mode mandates its own first line (ultrawork does), print that mode's line first and this marker on the next line — both contracts stay satisfied. What a shortened run still owes. If you judge the topic settled and shorten the research, say so, but two things survive any shortening: the final report is shown inline through showhtmlpage (the answer, its figures, its sources), and a visual reproduction is compared against real frames of its source with the side-by-side pairs inside that report (Phase 6). A built app or 3D scene shown inline is the product, not the report; show the report as well. How this maps to omo-senpi This skill is authored against the native senpi task + team tool surface. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills code-yeongyu/ulw-research