'experiment' 검색 결과

Reverse-engineer raw materials (Sparse idea, Dense idea, experimental log) from an existing AI research paper to build a benchmark case for evaluating paper-writing pipelines. Replicates the PaperWritingBench dataset construction procedure from arXiv:2604.05018 §3 / App. C. TRIGGER when the user asks to "build a benchmark case from this paper", "reverse-engineer raw materials", or "evaluate my pipeline against PaperWritingBench".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

All-in-one fullstack dev engine. /aura: 46 modes (build/fix/clean/deploy/review/spec/lore/ax/experiment/payment/debug/qa/orchestrate/escalate+), 6-layer security with 32 hooks, tiered models (ZERO/ECO/PRO/MAX), 8 languages, 16 specialized agents, SPEC/EARS/TRUST5/XLOOP/RALF/Autopus absorbed. ~55% token savings.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Conduct a peer review of research methodology, experimental design, and manuscript quality. Covers methodology evaluation, statistical appropriateness, reproducibility assessment, bias identification, and constructive feedback. Use when reviewing a manuscript, preprint, or internal research report, evaluating a research proposal or study protocol, assessing evidence quality behind a claim, or reviewing a thesis chapter or dissertation section.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Register trained models in MLflow Model Registry with version control, implement stage transitions (Staging, Production, Archived) with approval workflows, and manage model lineage with comprehensive metadata and deployment tracking. Use when promoting a trained model from experimentation to production, managing multiple model versions across development stages, implementing approval workflows for governance, rolling back to previous versions, or auditing model changes for compliance.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Design and execute A/B tests for ML models in production using traffic splitting, statistical significance testing, and canary/shadow deployment strategies. Measure performance differences and make data-driven decisions about model rollout. Use when validating a new model version before full rollout, comparing candidate models trained with different algorithms, measuring business metric impact of model changes, or when regulatory requirements mandate gradual rollout.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Systematically interpret nuclear magnetic resonance spectra (1H, 13C, DEPT, and 2D experiments) to elucidate molecular structure. Covers chemical shift assignment, coupling pattern analysis, integration, and correlation of multi-dimensional data into coherent structural proposals.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Fit cognitive drift-diffusion models (Ratcliff DDM) to reaction time and accuracy data with parameter estimation (drift rate, boundary separation, non-decision time), model comparison, and parameter recovery validation. Use when modeling binary decision-making with reaction time data, estimating cognitive parameters from experimental data, comparing sequential sampling model variants, or decomposing speed-accuracy tradeoff effects into latent cognitive components.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Validate and scientifically interpret completed research runs, including negative, null, boundary, confounded, failed, and inconclusive outcomes. Use after execution to assess evidence and claim impact; not to edit methods or schedule experiments.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Apply WIT (Writing Is Thinking) as a human–LLM collaborative scientific reasoning skill for scientific question formulation, finding-driven research planning, next-experiment selection, Results or Discussion review, claim–evidence and reviewer stress tests, manuscript logic audits, deadline closure, and researcher growth. Use when the user invokes WIT or asks for these question-driven scientific reasoning workflows; do not use for generic copyediting, summarization, or literature search alone.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Developer reference for Senpai's retired direct-GitHub experiment logging workflow. Use only when auditing or migrating legacy research tracks.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when asked to prototype one design question through a cheap logic or UI experiment, including button-driven state-model checks. Not for polished artifacts: use polished-web-prototype.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Design guide + benchmarked pitfalls for building Monte-Carlo / Simulated Annealing refinement layers on top of greedy hex-grid layouts for code visualization (packages/gui/src/store/hexLayout.ts, sandbox/hex-sandbox, future Rust ports). Use when: (1) planning to add MC/SA on top of an existing hex-grid pack, (2) deciding whether a simpler SA would match a hierarchical MC with force-directed + chain drag, (3) budgeting wall-clock for million-node cold-start, (4) debugging "blob turns Swiss-cheese" or "folders stop nucleating" during MC refinement, (5) choosing between folder cohesion and raw Σ-link-length as cost function. Contains four hard-won, quantified lessons and anti-patterns that would take a full day of experiments to rediscover.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Throwaway experiments to validate feasibility before building.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Design A/B tests with hypotheses, variants, sample sizes, and analysis plans. TRIGGERS - Use when user wants to run A/B tests, split tests, or experiment with variations.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Create today's daily_reports/YYYYMMDD.md by carrying over pending TODOs and recent experiment results from yesterday's report. Use at the start of a session.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Run cross-experiment competition strategy synthesis. Invokes the competition-strategist agent which loads daily_reports/* + all SESSION_NOTES.md / claudeSummary.md / submit/SUBMISSIONS.md / KAGGLE_DIRECTION.md in parallel and proposes next moves. Use weekly or at inflection points.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when developing in packages/agent-core-v2 (the DI × Scope agent engine) — adding or modifying a domain Service, choosing a LifecycleScope, wiring DI dependencies, splitting a domain across scopes, owning or migrating a config section, gating behavior behind an experimental flag, raising coded errors, working on the permission system, writing DI/Scope tests, porting business logic from agent-core (v1) to v2, triaging a main-branch commit against v2, or exposing a v2 domain over server-v2 while keeping the /api/v1 wire contract compatible with released clients. Self-contained guide organized by development stage (orient → design → implement → test → verify) plus align workflows for v1→v2 migration, main-branch commit triage, and server-v2 wire exposure; each file carries the rules, examples, and red lines for its step.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when building durable AI agents or agentic workflows with Inngest and AgentKit, including model calls, tool calls, multi-agent networks, human approval, realtime progress, provider rate limits, crash-safe execution, and Agent Evals handoff. Covers AgentKit, `step.ai`, `step.run`, `step.waitForEvent`, native realtime, and when to use lower-level Inngest primitives instead of an in-memory agent loop. Use `inngest-agent-evals` with this skill when the user wants scoring, sessions, experiments, deferred scorers, or outcome-based evaluation for the agent.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Inspect and operate Inngest Cloud through its OAuth MCP connection. Use for deployed apps and functions, failed or slow runs, traces, events, environments, sessions, experiments, and Insights. Prefer this for Cloud operations when MCP tools are available; use CLI or REST skills for explicit terminal or HTTP tasks.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Manus-style context engineering for Agent Teams. Coordinate multiple Claude Code instances with shared planning files. Use when complex tasks need parallel work (code review, debugging, feature development). Requires CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.