Lllllllama技能

rigorpilot-skills/skills/ai-research-explore

Rigor Explore compatible skill slug for meaningful and potentially novel deep learning research candidates. Use when the researcher has chosen the task family, dataset, benchmark, evaluation method, provided SOTA references, and wants candidate-only exploration on top of `current_research` with auditable repo understanding, idea gating, fair comparison, and governed experiments written to `explore_outputs/`. Do not use for README-first trusted reproduction, open-ended direction finding,...

rigorpilot-skills/skills/ai-research-reproduction

RigorPilot 复现模式编排器，用于README优先的深度学习仓库复现。当用户需要端到端、最小可信流程时使用，该流程先读取仓库，选择最小的文档化推理或评估目标，协调输入、设置、可信执行、可选的可信训练、可选的仓库分析以及可选的论文差距解决，强制执行保守补丁规则，记录证据、假设偏差和人工决策点……

rigorpilot-skills/skills/analyze-project

针对深度学习研究仓库的Rigor Analyze / Rigor Audit只读技能。当用户希望阅读和理解仓库、检查模型结构与训练或推理入口点、审查配置与插入点，或在无需修改代码或运行繁重任务的情况下标记可疑实现模式时使用。不适用于主动命令执行、大规模重构、推测性代码适配或自动修复错误。

rigorpilot-skills/skills/env-and-assets-bootstrap

用于README优先的深度学习仓库复现的Rigor Setup技能。当任务明确需要为README文档化的仓库在运行前准备保守的conda优先环境、检查点和数据集路径假设、缓存位置提示以及设置说明时使用。不用于仓库扫描、完整编排、论文解读、最终运行报告或与特定复现目标无关的通用环境设置。

rigorpilot-skills/skills/explore-code

We need to translate the given text from English to Simplified Chinese. The instruction says: preserve product names, protocol names, URLs, numbers, and technical terms. Do not add claims, explanations, Markdown, bullets, links, labels, prefixes, or extra commentary. Also, do not include the name "explore-code" unless it appears in the source text. The source text does not contain "explore-code" explicitly, so we don't include it. The text is a description of a skill. We need to translate it accurately, keeping technical terms like "LoRA", "adapter layers", "backbone", "head", "rollback-aware records", "explore_outputs/", "current_research". Also note "Rigor Improve implementation leaf skill" - likely a proper name or technical term? Possibly "Rigor Improve" is part of a skill name? But instruction says preserve product names, so we keep "Rigor Improve" as is? Or translate? The instruction says "preserve product names, protocol names, URLs, numbers, and technical terms

rigorpilot-skills/skills/explore-run

We need to translate the given text from English to Simplified Chinese. The text describes a skill called "explore-run" (name to preserve). The instruction says to translate only the text inside <text>, and not include the name unless it appears in the source text. The name "explore-run" does appear in the source text? Actually, the source text starts with "Rigor Improve / Rigor Explore run leaf skill..." - here "run" is part of the phrase, but the name to preserve is "explore-run". The source text does not contain "explore-run" as a standalone term; it has "Rigor Explore run leaf skill". However, the instruction says "Name to preserve: explore-run". I think we should not add the name if it's not in the source. The source has "Rigor Explore run" which might be a compound. But the instruction says "Do not include the name unless it appears in the source text." So we only translate what's there. The name "explore-run" is not literally in the source as a

rigorpilot-skills/skills/minimal-run-and-audit

We need to translate the given English text into Simplified Chinese. The instruction says: "Translate only the text inside <text>. Do not include the name unless it appears in the source text." The name "minimal-run-and-audit" is not inside the <text> tags, so we should not include it. The text is a description of a skill. We need to preserve product names, protocol names, URLs, numbers, technical terms. The text includes "Rigor Run", "README-first", "repro_outputs/", "patch notes". These should be preserved as is or translated appropriately? "Rigor Run" might be a product name? It says "Rigor Run skill" - likely a proper name. "README-first" is a phrase. "repro_outputs/" is a directory path. "patch notes" is a common term. We should keep technical terms like "smoke test", "inference", "evaluation", "repository", "training execution", "repo intake", "paper lookup", "target selection", "end-to-end orche

rigorpilot-skills/skills/paper-context-resolver

严格论文上下文助手，用于README优先的深度学习仓库复现。仅在README和仓库文件存在狭窄的复现关键缺口，且任务是从原始论文来源解析特定论文细节（如数据集划分、预处理、评估协议、检查点映射或运行时假设）并记录冲突时使用。不适用于通用论文摘要、仓库扫描、环境配置、命令执行、仅标题论文检索或...

rigorpilot-skills/skills/repo-intake-and-plan

用于README优先的深度学习仓库复现的严格输入助手。当任务明确为扫描仓库、读取README及常见项目文件、提取文档化命令、分类推理、评估和训练候选方案，并向主协调器返回最小可信复现计划时使用。不用于环境设置、资源下载、命令执行、最终报告、论文查阅或端到端协调。

rigorpilot-skills/skills/run-train

我们要求翻译一段英文文本到简体中文。需要保留产品名、协议名、URL、数字、技术术语。不要添加声明、解释、Markdown、项目符号、链接、标签、前缀或额外评论。目标语言是简体中文。目录项类型是agent skill，名称run-train要保留，但只翻译<text>内的内容，除非名称出现在源文本中。源文本中出现了"Rigor Train skill"，但名称是"run-train"，注意区分。源文本中"Rigor Train skill"可能是一个技能名称，但指令说"Name to preserve: run-train"，所以"run-train"是保留的名称，而"Rigor Train"可能也需要保留？指令说"Preserve product names, protocol names, URLs, numbers, and technical terms." 但"Rigor Train"可能是一个产品名或技能名？为了保险，保留"Rigor Train"不翻译。但注意：源文本中"Rigor Train skill"整体，其中"Rigor Train"可能是一个专有名词

rigorpilot-skills/skills/safe-debug

用于深度学习研究工作的严格调试/严格审计技能。当用户粘贴回溯信息、终端错误、CUDA内存不足、检查点加载失败、形状不匹配、NaN损失症状或训练失败，并希望在打补丁前进行保守诊断，且调试修复与研究贡献明确分离时使用。不适用于大规模重构、推测性适配、自动探索性修补或常规仓库熟悉。