360 Secure SkillHub
360 安全技能中心

repo-intake-and-plan

面向 README 优先的复现任务:扫描仓库结构与常见项目文件,提取文档中记录的命令,保守分类推理、评估与训练候选,输出最小可信复现计划及歧义风险清单;本身不安装环境、不下载资产、不执行命令。

lllllllama
热度 0.00
最近更新 2026-10-18 15:53:53
分类:开发依赖:读写文件 / 代码执行 / 内部调用大模型应用场景:工作流 / 研究 / 报告撰写

安装技能

复制下面的话术发给你的 Agent,它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill: npx secure-skills-cli add lllllllama/rigorpilot-skills/repo-intake-and-plan
Metadata
name
repo-intake-and-plan
description
Rigor Intake helper for README-first deep learning repo reproduction. Use when the task is specifically to scan a repository, read the README and common project files, extract documented commands, classify inference, evaluation, and training candidates, and return the smallest trustworthy reproduction plan to the main orchestrator. Do not use for environment setup, asset download, command execution, final reporting, paper lookup, or end-to-end orchestration.

repo-intake-and-plan

Use this as the Rigor Intake helper. The installed slug remains repo-intake-and-plan for compatibility.

When to apply

  • At the beginning of README-first reproduction work.
  • When the main skill needs a fast map of repo structure and documented commands.
  • When inference, evaluation, and training candidates must be classified conservatively.
  • When the user explicitly wants to inspect the repo first and not run anything yet.

When not to apply

  • When execution has already started and the task is now about running commands or writing outputs.
  • When the target is not a repository-backed reproduction task.
  • When the user only wants paper interpretation without repo inspection.
  • When the user already has a selected documented command and only needs setup or execution.

Clear boundaries

  • This skill scans and plans.
  • This skill is helper-tier and should usually be orchestrator-invoked.
  • It does not install environments.
  • It does not prepare large assets.
  • It does not execute substantive reproduction commands.
  • It does not decide high-risk patching.

Input expectations

  • Target repository path.
  • Access to README and common project files if present.
  • Optional user hints about desired priority, such as inference-first.

Output expectations

  • concise repo structure summary
  • documented command inventory
  • inferred candidate categories: inference, evaluation, training, other
  • minimum trustworthy reproduction recommendation
  • notable ambiguity or risk list

Notes

Use references/repo-scan-rules.md and helper scripts under scripts/.