跳到主内容
智客 ZICQ

技能库 智客分类:文档办公 ai-research-reproduction

Ai Research Reproduction

Rigor Reproduce相容技能弹丸用于README-第一深层学习寄存器复制. 当用户想要一个端到端,最小可信流,首先读取寄存器,选择最小的有文件记载的推论或评价目标,协调收录,设置,可信执行,可选信任的训练,可选的寄存器分析,以及可选的纸张-gap解析,执行保守的补丁规则,记录证据假设偏差和人的决定点,并写出标准化的"reprop_outputs/"捆. 不要用于纸质摘要,通用环境设置,孤立回波扫描,独立命令执行,默默协议更改,分数追逐,或在基于寄存器的复制之外提供广泛的研究协助.

361159 安装量

官方网址:skills.sh

技能介绍

先看中文介绍;官方 description 原文单独保留,不改写 SKILL.md。

做什么

Rigor Reproduce 兼容技能弹丸用于 README- 第1个深层学习仓库复制

何时用

用户想要一个端到端的最小可信流,首先读取寄存器,选择最小的有文献记载的推论或评价目标,协调收录,设置,可信执行,可选可选可信赖的训练,可选可选的寄存器分析,以及可选可选的纸张gap re

代理如何加载

按 Agent Skills 渐进披露:启动时只加载 name 与 description(约 100 token);任务匹配后才读入整份 SKILL.md 正文;scripts/、references/、assets/ 仅在需要时再读。 本文件正文结构:ai-research-reproduction、Purpose、Fast Path、Fit、Trusted Target Selection、Workflow。 其中含规范建议的小节:分步指令。

文件分析

文件分析:除 SKILL.md 外,正文引用了 scripts/orchestrate_repro.py、references/agent-job.md、scripts/doctor.py、references/patch-policy.md、references/output-spec.md、references/agent-operating-principles.md,属于带资源的技能包,这些文件按需再读。

官方 description(原文)

Rigor Reproduce compatible skill slug for README-first deep learning repository reproduction. Use when the user wants an end-to-end, minimal-trustworthy flow that reads the repository first, selects the smallest documented inference or evaluation target, coordinates intake, setup, trusted execution, optional trusted training, optional repository analysis, and optional paper-gap resolution, enforces conservative patch rules, records evidence assumptions deviations and human decision points, and writes the standardized `repro_outputs/` bundle. Do not use for paper summary, generic environment setup, isolated repo scanning, standalone command execution, silent protocol changes, score chasing, or broad research assistance outside repository-grounded reproduction.

ai-research-reproductionPurposeFast PathFitTrusted Target SelectionWorkflowPatch BoundaryOutputsReference Loading

兼容:Requires Python 3.11+ and Git for bundled orchestration; target repositories may require additional reviewed dependencies, network access, or accelerators.

来源分类:skills.sh agent-skill

SKILL.md 与 Agent 调用

官方规范 ↗
name
ai-research-reproduction
description
Rigor Reproduce compatible skill slug for README-first deep learning repository reproduction. Use when the user wants an end-to-end, minimal-trustworthy flow that reads the repository first, selects the smallest documented inference or evaluation target, coordinates intake, setup, trusted execution, optional trusted training, optional repository analysis, and optional paper-gap resolution, enforces conservative patch rules, records evidence assumptions deviations and human decision points, and writes the standardized `repro_outputs/` bundle. Do not use for paper summary, generic environment setup, isolated repo scanning, standalone command execution, silent protocol changes, score chasing, or broad research assistance outside repository-grounded reproduction.
compatibility
Requires Python 3.11+ and Git for bundled orchestration; target repositories may require additional reviewed dependencies, network access, or accelerators.
  1. 发现技能客户端向 Agent 提供名称与描述目录。
  2. 匹配与调用用户指定或任务匹配后,载入 SKILL.md 指令。
  3. 按需加载按步骤读取参考文档、使用脚本与素材。
指令中引用的文件 · 11
  • scripts/orchestrate_repro.py
  • references/agent-job.md
  • scripts/doctor.py
  • references/patch-policy.md
  • references/output-spec.md
  • references/agent-operating-principles.md
  • references/language-policy.md
  • references/research-rigor-principles.md
  • references/deep-learning-experiment-principles.md
  • references/research-safety-principles.md
  • references/scripts

以下路径提取自原文;文件是否齐全请以来源仓库中的完整目录为准。

具体调用语法与可用工具以目标 Agent 客户端为准。 查看调用机制说明 ↗

安装这个技能

Skills CLI ↗

先选择目标 Agent 和安装范围,保留技能包的附属文件,安装后检查客户端能否发现该技能。

该技能引用了附属文件,请从来源获取完整目录;仅复制 SKILL.md 可能缺少依赖。

交给 Agent 安装

复制安装指令给支持 Agent Skills 的代理,确认其中的目标目录与客户端匹配。

把 Agent Skill「ai-research-reproduction」安装到我的项目:SKILL.md 原文与官方 description 见 https://zicq.com/zh/skills/skl-9684c9de82da7361-Ai-%E7%A0%94%E7%A9%B6%E5%A4%8D%E5%88%B6.html
请存为 .cursor/skills/ai-research-reproduction/SKILL.md 或 .claude/skills/ai-research-reproduction/SKILL.md,frontmatter 的 name 与 description 保持原样,不要改写。
该技能还带 scripts/、references/、assets/ 等文件,请从 https://github.com/lllllllama/rigorpilot-skills 取完整目录,不要只建一个 SKILL.md。

GitHub 完整包 ↗

终端安装 · Skills CLI

需要 Node.js 与 npx。先查看仓库技能列表,确认实际名称。

npx skills add 'https://github.com/lllllllama/rigorpilot-skills' --list

npx skills add 'https://github.com/lllllllama/rigorpilot-skills' --skill 'ai-research-reproduction'

CLI 会交互选择目标 Agent,默认安装到项目;用户级安装使用 -g。先通过查看命令核对仓库内容,再用 npx skills list 检查已安装技能。

阅读排版
--- name: ai-research-reproduction description: Rigor Reproduce compatible skill slug for README-first deep learning repository reproduction. Use when the user wants an end-to-end, minimal-trustworthy flow that reads the repository first, selects the smallest documented inference or evaluation target, coordinates intake, setup, trusted execution, optional trusted training, optional repository analysis, and optional paper-gap resolution, enforces conservative patch rules, records evidence assumptions deviations and human decision points, and writes the standardized `repro_outputs/` bundle. Do not use for paper summary, generic environment setup, isolated repo scanning, standalone command execution, silent protocol changes, score chasing, or broad research assistance outside repository-grounded reproduction. compatibility: Requires Python 3.11+ and Git for bundled orchestration; target repositories may require additional reviewed dependencies, network access, or accelerators. --- # ai-research-reproduction ## Purpose Guide README-first deep learning reproduction toward the smallest trustworthy run with auditable evidence. Preserve documented meaning; record assumptions, deviations and blockers instead of changing semantics to manufacture success. Load specialized references only for a concrete uncertainty. ## Fast Path For a routine bounded run, keep the control path short: 1. Read the target README and only the target test/config/source needed to understand the documented command. 2. Run `scripts/orchestrate_repro.py --repo --plan-only --agent-output` with any explicit user timeout bound (`--timeout` or `--train-timeout`) already supplied; review `command_candidates`, the selected `cmd-XX`, side-effect contract, selection fingerprint, and returned `reviewed_run_args`. With no `--output-dir`, later evidence goes to `/repro_outputs` regardless of caller cwd. 3. Run the selected candidate, or another reviewed candidate, with `--run-selected --command-id --plan-fingerprint --agent-output` plus requested timeout/metric/source-adjacent options. Preserve an explicit user command-timeout bound instead of silently making it stricter on a routine trusted run. `--timeout` limits the target command; do **not** wrap the whole orchestrator in an equal or shorter external timeout, because it still needs time to terminate children and write terminal evidence. A changed command set fails closed; setup/download commands are never target candidates. 4. Run `--verify-output --agent-output`; inspect detailed evidence files only when verification fails or the result is partial/blocked. 5. Deliver the bounded result and stop. For a host with short tool-call deadlines, rerun planning with `--include-agent-handoff` and follow `references/agent-job.md`; otherwise keep the direct path above. Job completion is not task acceptance, and uncertain state is never a reason for automatic replay. Do **not** inspect `orchestrate_repro.py`, `annotate_readme.py`, `_bundled/`, writers, or runtime internals on a normal success path. Inspect implementation only for a concrete blocker, unexpected side effect, bundle-integrity failure, or unresolved safety question. Use `scripts/doctor.py` for first-use environment/install diagnostics. Executed commands keep full lifecycle/log evidence under `repro_outputs/_runtime//`. ## Fit Use this skill for repository-grounded, multi-phase trusted reproduction where the goal is a small reproducible target. Do not use it for paper summaries, generic setup, isolated scanning, standalone commands, open-ended research design, or explicitly authorized candidate exploration. ## Trusted Target Selection Choose the smallest target that can honestly demonstrate repository-grounded reproduction: 1. documented inference 2. documented evaluation 3. documented training startup or partial verification 4. full training only after explicit user confirmation Treat README guidance as the primary reproduction intent. Use repository files to clarify the README, not to silently replace it. When the README and paper conflict, record the conflict and use `paper-context-resolver` only for the narrow reproduction-critical gap. ## Workflow 1. Treat README guidance as primary; extract and select the minimum trustworthy target. 2. Use setup/assets only for target-specific prerequisites and `analyze-project` only when structural clarification is needed. 3. Use `minimal-run-and-audit` for inference/evaluation/smoke and `run-train` for training startup, kickoff, or resume; direct execution is the default. 4. Pause before fuller training or changes to dataset, split, checkpoint, preprocessing, metric, loss, model semantics, or interpretation. 5. Award `result-match` only against explicit expected metrics and tolerance; process success alone is not reproduction success. 6. Write the evidence bundle, return the requested bounded result, and stop; optional stages are not automatic follow-up work. ## Patch Boundary Prefer no repository edits. If edits are needed, keep them conservative and auditable: - Try command-line arguments, environment variables, path fixes, dependency version fixes, or dependency-file fixes before code changes. - Reproduction fixes are allowed when needed, but they must not be hidden. State what changed, why it was necessary, whether it changes scientific meaning, and whether it affects comparability with the paper, README, or baseline. - Avoid changing model architecture, core inference semantics, training logic, loss functions, or experiment meaning. - If repository files must change, create a branch named `repro/YYYY-MM-DD-short-task`, keep verified patch commits sparse, and record README-fidelity impact in `PATCHES.md`. See `references/patch-policy.md`. ## Outputs Always target `repro_outputs/`: ```text SUMMARY.md COMMANDS.md LOG.md SCIENTIFIC_CHANGELOG.md COMPARABILITY_REPORT.md status.json ANNOTATED_README.md # original README + colored per-section agent-action annotations PATCHES.md # only if patches were applied ``` Use the templates under `assets/` and `references/output-spec.md`. Keep summaries short, commands copyable, machine state stable, and scientific/comparability changes explicit. `ANNOTATED_README.md` must preserve the source README byte-for-byte outside inserted evidence blocks and pass its strip/check round trip. Use `--source-adjacent-readme` only for an owned `RIGORPILOT_README.md`; never replace an unrelated file. Distinguish verified facts from inference. ## Reference Loading - Workflow judgment: `references/agent-operating-principles.md`. - Human-readable output: `references/language-policy.md`. - Scientific/comparability judgment: `references/research-rigor-principles.md` and, when experiment details matter, `references/deep-learning-experiment-principles.md`. - Protocol-sensitive changes: `references/research-safety-principles.md` and `references/patch-policy.md`. - Personal rigor and lessons are advisory only; keep specialized detail in references/scripts rather than expanding this entrypoint.

相关技能

文档办公

Ontology

为结构化的代理内存和可堆肥技能所打入的知识图. 在创建/征服实体(Person, project, Task, Evention, Document)时使用,链接相关对象,强制约束,规划多步动作作为图变,或技能需要共享状态时使用. 触发到"记住","我知道什么","链接X到Y",…

文档办公

Nano Pdf

使用纳米-pdf CLI编辑带有自然语言指令的PDF.

文档办公

Word / DOCX

创建,检查,并编辑有可靠样式的Microsoft Word文档和DOCX文件,编号,跟踪更改,表格,章节,并进行相容性检查. 当 (1) 任务涉及 Word 或 ".docx " 时使用; (2) 文件包括跟踪的更改,评论,字段,表格,模板,或页面布局限制; (3) 文档必须在不…

文档办公

Api Gateway

通过 Maton 网关调用第三方 API, 它为用户已经连接的应用程序注入证书 。 当用户命名一个连接的应用程序和其中的具体行动时使用此技能——读取一个邮箱,查询一个CMM,归档一个问题,更新一个电子表格,通过一个连接的搜索或刮取提供者运行一个查询. 每一次通话都到用户连接的应用…