'hypothesis' 검색 결과

Autonomous fixed-budget ML experiment loop — setup, iterative hypothesis testing, git-based keep/discard tracking, and indefinite autonomous execution. Implements the karpathy/autoresearch protocol.

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

Specialized research and analysis prompt methodology for Claude. Provides 11 tested approaches (3 identity, 4 reasoning, 4 output) for data analysis, policy research, systematic evidence review, investigative research, and research-specific deliverables. Use when building prompts for quantitative data interpretation, evidence-based policy recommendations, literature reviews, causal analysis, hypothesis-driven investigation, or briefing documents. Trigger on: "prompt for data analysis," "research prompt," "policy brief prompt," "literature review prompt," "prompt for investigating," "systematic review prompt," "build a prompt for evidence synthesis," "causal analysis prompt," "briefing document prompt." Also use when user describes a research or analytical task and needs a structured Claude prompt for it. Do NOT use for evaluating existing prompts (use rootnode-prompt-validation if available) or auditing Claude Projects (use rootnode-project-audit if available).

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

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 Arbor executor workflow: clone the repo from the git bundle your brief hands you, implement and evaluate exactly ONE hypothesis with the file tools, then report structured results via worker_complete. Preloaded automatically on arbor-executor task workers. Never touch the held-out test split.

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

Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.

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

Structured guide for setting up A/B tests with mandatory gates for hypothesis, metrics, and execution readiness.

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

Use this skill when applying VCSDD to Python projects. Provides hypothesis property testing patterns, mutmut mutation testing, and pytest integration for the VCSDD pipeline.

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

Use this skill during Phase 5 formal hardening. Provides tool selection, proof harness patterns, security/purity audit expectations, and verification result interpretation for Rust (Kani), Python (hypothesis), and TypeScript (fast-check).

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

"Apply the Efficient Market Hypothesis (Fama, 1970) to evaluate information incorporation in asset prices across weak, semi-strong, and strong forms. Use this skill when the user needs to assess market efficiency, determine if a trading strategy can generate abnormal returns, evaluate event studies, or when they ask 'can technical analysis work', 'does the market already know this', or 'is this anomaly exploitable'.".

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

Apply statistical methods including descriptive stats, trend analysis, outlier detection, and hypothesis testing. Use when analyzing distributions, testing for significance, detecting anomalies, computing correlations, or interpreting statistical results.

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

Statistical methods for biology and medicine — study design, hypothesis testing, regression, and survival analysis.

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

Design rigorous A/B test plans with hypothesis, sample size calculation, Minimum Detectable Effect (MDE), randomization strategy, and decision rules. Includes guardrail metrics and rollout playbook. Use when planning product experiments, conversion optimization, or data-driven feature decisions.

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

Use when running or wiring OpenScientist for AI Gene Review gene-function hypotheses, especially blinded comparisons against local bioinformatics analyses.

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

The investigation harness for "why is this slow?" over a Pulp Perfetto trace (.pftrace). Runs the hypothesis→query→drill-down chain-of-evidence loop autonomously and returns a plain-English root cause + evidence + a concrete fix. TRIGGER on "why is my plugin slow to open", "find the slowest frames", "why is the UI stuttering", "why is my plugin using so much CPU", "which DSP node is expensive", "the load meter looks calm but CPU is pinned", or a named `pulp trace gpu-startup|gpu-health|gpu-probe` analysis. Ships Pulp-specific hints for dsp, frame, js, gpu, and cross-platform symptoms.

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

Design and analyze engineering experiments or simulations using baseline cases, hypothesis-driven DOE, traceable data processing, defensible plots, uncertainty, and validation. Use for CFD, laboratory data, ML workflows, parameter studies, or research code.

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

Use when a task needs the judgment of an Epidemiologist — investigating a disease outbreak and identifying its source, designing a case-control or cohort study to test an exposure hypothesis, calculating attack rates/odds ratios/relative risk from surveillance data, evaluating whether a surveillance system is sensitive and timely enough to catch a real signal, or judging whether an observed case cluster is a true outbreak or expected background variation.

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

Design statistically rigorous experiments to test data science hypotheses. Use when the user says "design an A/B test", "run an experiment", "test this hypothesis", "is this difference significant", "how many samples do I need", "randomized controlled trial", "causal inference", "uplift test", "holdout group", "significance test", "power calculation", "avoid p-hacking", or needs to determine whether an observed effect is real before making a product or model decision. For lean build-measure-learn product experiments without the statistics, use experiment-design instead.

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

Expert guidance for deep security incident and entity investigations in Google SecOps. Use when investigating cases, analyzing entities (hosts, IPs, domains, hashes, users), extracting and searching UDM events, performing asset and user timeline analysis, and detecting lateral movement across enterprise networks. Don't use for detection rule authoring or YARA-L tuning (use secops-detection-engineering), proactive hypothesis-driven hunting (use secops-hunt), initial alert triage (use secops-triage), or basic case status updates (use secops-cases).

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

Design product experiments to test hypotheses. Use when the user says "run an experiment", "A/B test this", "build-measure-learn", "validate this assumption", "test this hypothesis", "we don't know if this will work", "minimum viable test", "lean experiment", or wants to reduce risk before fully building a feature - even if they don't explicitly say "experiment". For sample sizes, power calculations and significance testing, use ab-test-design instead.

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

Generate A/B copy variants grounded in Eugene Schwartz's awareness and market-sophistication stages and John Caples' tested-headline discipline. Every variant declares its angle, the awareness stage it targets, and a falsifiable hypothesis, and the skill recommends which pair to test first and what delta counts as signal. Use when the user says "A/B test this", "write variants", "give me options", "test different angles", "copy variants", "ab copy", "test this headline", "multiple versions", "which version is better", or wants to test copy before publishing. For reviewing copy that already exists, see copy-review. For sample size and stopping rules, see growth-experiment. For diagnosing a page rather than its words, see page-cro. For full paid ad sets by platform, see ad-campaign-writer.

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

Product Discovery through an 18-task methodology in 6 blocks — from market analysis to an investor-ready financial plan. Use when someone wants to run Product Discovery, validate a startup, assess a market hypothesis, prepare for an investment round, or raises an adjacent topic — idea validation, niche sizing, competitor teardown, product-market fit, pitch preparation, startup unit economics, geographic expansion into a new country, go-to-market for SEA / Asia / MENA. People rarely name PD explicitly; they say 'is there a market for this', 'assess my idea', 'I need a deck for an angel', 'we are entering Thailand/Singapore/UAE, how do we size it'. Use the skill in those cases too. Three modes: Light (~45 min, idea stage), Full (~2-3 h, MVP with customers), Geographic Expansion (~2 h, product entering a new geography). Produces 3-4 artifacts in /mnt/user-data/outputs/: one-pager.pptx, financial-plan.xlsx, presentation.pptx, optionally interview-guide.docx.

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

Comprehensive statistics expert covering probability theory, distributions, hypothesis testing, regression, and Bayesian methods

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

Design and evaluate paid-ad experiments with hypotheses, randomization units, sample-size and duration assumptions, guardrails, platform experiment tools, analysis, and decision rules. Use for A/B test, split test, experiment design, hypothesis, statistical significance, sample size, test duration, or experiment readout.

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

MUST USE for any real runtime debugging across ANY language or binary — crashes, silent failures, wrong responses, stuck processes, memory leaks, async misbehavior, unexplained timing, reverse engineering. Runs a hypothesis-driven loop: form ≥3 hypotheses, investigate in parallel, after 2 failed rounds spawn Oracles from orthogonal angles, confirm root cause, lock with a failing test, fix minimally, QA by actually USING the system, scrub artifacts. The actual HOW lives in `references/` — READ THEM. Triggers: 'debug this', 'why is X not working', 'hanging', 'attach a debugger', 'reverse engineer', 'pwndbg', 'gdb', 'lldb', 'node inspect', 'tsx debug', 'pdb', 'dlv', 'delve', 'rust-gdb', 'set a breakpoint', 'context window exploded', 'why is the response empty', 'attach the debugger', 'debug it', 'why is this happening', 'trace this bug', 'reproduce and fix', 'silent failure', 'HTTP 200 but empty', 'why did it stop', 'inspect the binary', 'reverse engineering', 'playwright'.

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