Package completed data analysis and ML work so an independent recipient can reproduce the claimed results, verify artifact lineage, and operate the handoff within its stated scope. Use when finalizing a project, study, model package, or review bundle; not for deploying to a live system.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
실행 점수 미검증
설치 방법 보기설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
Ship an evidence-bearing result, not merely code that once ran. The package must connect the approved question to immutable inputs, an executable workflow, generated outputs, validation evidence, and an explicit handoff boundary.
Before packaging, record:
Do not silently expand a validated result from a sample to a population, from retrospective analysis to prospective use, or from one environment to another.
Make each authoritative output traceable through:
source identity -> immutable snapshot or query -> transformation -> configuration
-> code revision -> environment -> model artifact -> evaluation -> published output
Record content hashes for immutable local artifacts and durable identifiers for remote sources. Preserve raw inputs when permitted; otherwise preserve the exact query, retrieval time, schema, row counts, access requirements, and a safe fixture sufficient to test the pipeline.
Separate source data, intermediate artifacts, final outputs, caches, and human edits. Never require a recipient to guess which file is canonical.
Provide one documented entry point from a clean state. Pin direct dependencies and runtime versions; record relevant system libraries and hardware. Seed every controllable source of randomness and document remaining nondeterminism rather than promising bitwise equality when the stack cannot provide it.
Packaging does not authorize restricted-data access, material compute, credential use, external transfer, or publication. Verify the relevant authority before those actions. When execution is not authorized or available, prepare the reproducible contract and label the unexecuted stages instead of running them.
Define acceptable reproduction precisely:
Fail loudly on missing inputs, schema drift, stale caches, or incompatible artifacts.
Run from the documented clean entry point without relying on notebook state, shell history, undeclared credentials, or files outside the package. Verify every material claim with evidence of matching scope.
A green unit test is not proof of complete reproduction. The completion matrix must distinguish:
If a full rerun is impossible because data, compute, or credentials are unavailable, ship the maximum verifiable subset and mark the unexecuted stages as unproven. Do not call the package fully reproducible.
Document how to run, verify, interpret, update, and safely retire the result. Include known limitations, prohibited uses, external dependencies, expected costs, credential ownership, failure signals, and escalation contacts. Preserve rejected hypotheses and failed experiments when they affect future maintenance or interpretation.
Use assets/reproduction-handoff.md as the release document and assets/run-manifest.yaml as a machine-readable starting point. For verification levels, lineage requirements, and clean-room acceptance rules, read references/reproduction-contract.md.
Release only when the package contains no secrets, unintended or unauthorized private data, machine-specific absolute paths, undeclared dependencies, or ambiguous canonical artifacts. Keep approved restricted artifacts in their authorized secure location and publish only permitted references or sanitized fixtures. External sharing and public release require separate authority. The final status must be one of:
State the status prominently. Never upgrade it based on intent or partial checks.
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
Audit datasets, joins, labels, and ground truth before analysis or modeling. Use when data meaning, row grain, time semantics, source-of-truth reliability, or label construction may invalidate conclusions; not for general model evaluation after the evidence base is already trusted.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design leakage-safe machine learning experiments that mirror real deployment and support fair model comparisons. Use when defining prediction timing, feature eligibility, train-validation-test splits, baselines, metrics, or controlled model iterations; not for auditing whether raw labels are trustworthy.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Isolate the root cause of ML performance drops, inconsistent evaluations, prediction errors, and training-serving mismatches across data, labels, splits, pipelines, models, metrics, and runtime behavior. Use when investigating a reproducible failure or regression, not routine model selection or general performance validation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Orchestrate an end-to-end data analysis or machine learning project from decision framing through reproducible handoff. Use when a request spans multiple lifecycle stages or an ambiguous modeling request must become a decision-ready result; use narrower audit or experiment-design skills for isolated reviews.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Route data analysis and machine learning work to the right skill in this suite. Use when starting any analysis, modeling, validation, or reproducibility task and the matching specialized skill is not yet clear; not needed when one specific skill already clearly applies.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Validate trained models and analytical claims against their intended decision, independent evidence, and human-reviewed ground truth. Use when reviewing model performance, analysis conclusions, launch claims, or evaluation reports; use failure diagnosis instead when the main task is locating a known defect.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.