Look up any arxiv paper on alphaxiv.org to get a structured AI-generated overview. This is faster and more reliable than trying to read a raw PDF.
The English summary is being prepared. Showing the original description.
Choose, configure, launch, and collect bounded subagents for research and engineering decisions. Root agents and delegation-capable subagents should read this before delegating: every task requires an explicit model tier, and high-leverage work such as research ideation, round planning, plateau pivots, large research reviews, hard optimization, disputed evidence, and expensive experiment portfolios requires frontier judgment.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Batch independent tasks in one spawn_agents call with a stable batch_key. Give each child a self-contained assignment and ask for a compact, evidence-linked result.
Every task must explicitly set model to fast, smart, or frontier; there is no implicit model tier. Choose the least expensive tier that provides the judgment the task requires:
model="fast" for mechanical, easily verified work: locating files, extracting facts, counting records, formatting results, running bounded commands, and reporting test or build failures.model="smart" for ordinary implementation and review, literature retrieval, bounded synthesis, standard failure diagnosis, and debugging code that is not already heavily optimized.model="frontier" for quality-first research judgment. This includes fresh research ideation, planning a new research round, changing direction after a plateau, reviewing a large research or experiment history, difficult debugging or optimization of code that is already highly optimized, reconciling conflicting evidence or disagreement between local and external evaluation, and selecting a portfolio that will consume substantial GPU time or external-evaluation budget.Keep frontier tasks focused. When using more than one for the same decision, give them distinct questions or perspectives. Do not spend frontier capacity on routine monitoring, simple retrieval, formatting, or other work whose answer is cheap to verify. Treat every child result as advice: inspect its evidence before acting on it.
Choose:
explore for local code, data, artifacts, or history;search_general_web for current public sources;search_research_publications for scholarly literature and primary papers;bash-runner with model=fast for tests, builds, and bounded commands; andgeneral-purpose for mixed analysis, planning, review, or implementation.Agent specialization and model tier are independent. For first-principles synthesis, critique, diagnosis, or planning, use agent="general-purpose". Use search_research_publications when the task is to find and compare primary papers, and search_general_web for current public sources. The search agent and its search skills own source selection and search mechanics.
Normally set include_context=false and provide a self-contained task with exact evidence paths. This gives the child a fresh perspective while preserving access to the merged system prompt and searchable parent history. Set include_context=true only when the complete model-visible conversation is necessary and cannot be summarized reliably. For research judgment, ask for research, critique, diagnosis, ideas, or a plan rather than edits.
Delegate before running a command or broad read that may return substantial output. A child can summarize output it produced; it cannot remove output that already entered the parent context.
agent="bash-runner", model="fast" for verbose tests, builds, bounded
logs, Git inspection, and deterministic command output.agent="explore", model="fast" for broad file, history, or PR-artifact
searches and extraction into cited facts.agent="general-purpose", model="fast" for exact mechanical edits with
explicit file targets and focused acceptance checks.model="smart" for ordinary implementation, review, synthesis, and
failure diagnosis.model="frontier" for causal scientific interpretation, disputed
evidence, direction changes, and expensive experiment portfolios.For a potentially large GitHub review, have the root call
get_prs(max_inline_prs=0), pass the returned artifact path to an Explore
child, inspect the child's cited decisive evidence, and perform any typed
GitHub transition in the root.
spawn_agents returns task IDs immediately. Continue useful work, then use bounded await_agents calls with all, first, quorum, or change and a timeout of at most 300 seconds. Use agent_status for one non-blocking snapshot and cancel_agents when work is no longer useful; do not poll.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Look up any arxiv paper on alphaxiv.org to get a structured AI-generated overview. This is faster and more reliable than trying to read a raw PDF.
The English summary is being prepared. Showing the original description.
Operator-side analysis of historical ML experiment PRs in Senpai research tracks. Use this skill whenever the user asks to: analyze experiments, categorize PRs, bucket experiments, summarize what's been tried, understand experiment history, review merged vs closed results, or asks "what experiments have we run / worked / failed". Also triggers for: "pull the latest experiments", "what's been tried so far", "category breakdown of PRs", "which experiments succeeded", "noam track analysis". When a branch name is mentioned (e.g. "noam branch", "on the noam branch"), pass it as the base branch to scope the fetch to just those PRs.
The English summary is being prepared. Showing the original description.
Create a typed assignment branch and draft PR for one student. Use when the advisor has a concrete hypothesis and the student has no open `status:wip` or `status:review` assignment.
The English summary is being prepared. Showing the original description.
Create or improve a Senpai target repository's program.md. Use this skill whenever the user wants to point Senpai at a fresh ML or research target repository, define the research objective, primary metric, benchmark contract, allowed edit boundaries, W&B reporting contract, or prepare a repo for autonomous advisor/student experiment loops.
The English summary is being prepared. Showing the original description.
Open GitHub Issues for human input and respond to the researcher team. Use this skill whenever you need to handle a human_issue event, respond to human issues, ask humans a question, or check team communications. Also triggers for: "any human messages?", "check issues", "respond to humans".
The English summary is being prepared. Showing the original description.
Search the general web or scholarly publications through Exa. Use for current public information, official documentation, source code, release notes, papers, preprints, journals, or literature research.
The English summary is being prepared. Showing the original description.