minimal-run-and-audit

द्वारा lllllllama

We need to translate the given English text to Hindi. The text describes a skill called "Rigor Run skill" for README-first deep learning repo reproduction. It specifies when to use it and when not to use it. We must preserve the name "minimal-run-and-audit" but it's not in the text, so we ignore. Also preserve technical terms like "README-first", "deep learning", "repro_outputs/", "patch notes", etc. No extra commentary. Just translation. Let's translate sentence by sentence: "Rigor Run skill for README-first deep learning repo reproduction." -> "README-first डीप लर्निंग रिपॉजिटरी पुनरुत्पादन के लिए Rigor Run कौशल।" (Note: "Rigor Run" is a name, keep as is? The text says "Rigor Run skill" - it's a skill name. Should we translate? The instruction says preserve product names, protocol names, etc. "Rigor Run" might be a

npx skills add https://github.com/lllllllama/rigorpilot-skills --skill minimal-run-and-audit

minimal-run-and-audit

Use this as the Rigor Run skill. The installed slug remains minimal-run-and-audit for compatibility.

Use the shared operating principles in ../../references/agent-operating-principles.md; this skill should make run evidence auditable without turning every command into a rigid protocol.

When to apply

  • After a reproduction target and setup plan exist.
  • When the main skill needs execution evidence and normalized outputs.
  • When a smoke test, documented inference run, documented evaluation run, or other short non-training verification is appropriate.
  • When the user already knows what command should be attempted and wants execution plus reporting only.

When not to apply

  • During initial repo scanning.
  • When environment or assets are still undefined enough to make execution meaningless.
  • When the task is a literature lookup rather than repository execution.
  • When the user is still deciding which reproduction target should count as the main run.

Clear boundaries

  • This skill owns normalized reporting for an attempted command.
  • It may receive execution evidence from the main skill or a thin helper.
  • It does not choose the overall target on its own.
  • It does not perform broad paper analysis.
  • It does not own training startup, resume, or long-running training state.
  • It should not normalize risky code edits into acceptable practice.
  • It must not hide changes that alter evaluation, preprocessing, checkpoints, metrics, or other scientific meaning.

Input expectations

  • selected reproduction goal
  • runnable commands or smoke commands
  • environment and asset assumptions
  • optional patch metadata

Output expectations

  • execution result summary
  • standardized repro_outputs/ files
  • SCIENTIFIC_CHANGELOG.md for changed scientific meaning and evidence status
  • COMPARABILITY_REPORT.md for README/paper/baseline comparability
  • clear distinction between verified, partial, and blocked states
  • PATCHES.md when repo files changed

Notes

Use references/reporting-policy.md, ../../references/research-rigor-principles.md, scripts/run_command.py, and scripts/write_outputs.py.

lllllllama की और Skills

ai-research-explore
lllllllama
Rigor Explore संगत कौशल स्लग, सार्थक और संभावित नवीन गहन शिक्षण अनुसंधान उम्मीदवारों के लिए। इसका उपयोग तब करें जब शोधकर्ता ने कार्य परिवार, डेटासेट, बेंचमार्क, मूल्यांकन विधि च
researchdata-analysisapi
analyze-project
lllllllama
Rigor Analyze / Rigor Audit केवल पढ़ने योग्य कौशल है जो गहन शिक्षण अनुसंधान रिपॉजिटरी के लिए है। इसका उपयोग तब करें जब उपयोगकर्ता किसी रिपॉजिटरी को पढ़ना और समझना चाहता है, मॉडल संरचना और प्रशिक्षण या अनुमान प्रवेश बिंदुओं का निरीक्षण करना चाहता है, कॉन्फ़िगरेशन और सम्मिलन बिंदुओं की समीक्षा करना चाहता है, या कोड को संशोधित किए बिना या भारी कार्य चलाए बिना संदिग्ध कार्यान्वयन पैटर्न को चिह्न
developmentcode-reviewresearch
ai-research-reproduction
lllllllama
RigorPilot पुनरुत्पादन-मोड ऑर्केस्ट्रेटर README-प्रथम गहन शिक्षण रिपॉजिटरी पुनरुत्पादन के लिए। उपयोग करें जब उपयोगकर्ता एक अंत-से-अंत, न्यूनतम-विश्वसनीय प्रवाह चाहता है जो पहले रिपॉजिटरी पढ़ता है, सबसे छोटा दस्तावेजीकृत अनुमान या मूल्यांकन लक्ष्य चुनता है, इनटेक, सेटअप, विश्वसनीय निष्पादन, वैकल्पिक विश्वसनीय प्रशिक्षण, वैकल्पिक रिपॉजिटरी विश्लेषण, और वैकल्प
researchdevelopmentdocument
explore-code
lllllllama
We need to translate the given English text into Hindi. The text describes a skill called "explore-code" but the instruction says to preserve the name only if it appears in the source text. The name "explore-code" does not appear in the provided text. So we just translate the text inside <text>. The text is a description of a skill for rigorous improvement implementation in deep learning research repositories. We need to preserve technical terms like "LoRA", "adapter layers", "backbone", "head", "rollback-aware records", "explore_outputs/", "current_research". Also preserve URLs if any (none here). Numbers: none. Protocol names: none. Product names: none. We translate into Hindi, keeping technical terms as is or with transliteration if needed. The instruction says "preserve" so likely keep them in English. But for Hindi translation, we can write them in English script within Hindi text. Also note: "Do not include the name unless it appears in the source text." So we don't add "explore-code".
developmentresearchcode-review
env-and-assets-bootstrap
lllllllama
README-प्रथम डीप लर्निंग रिपॉजिटरी पुनरुत्पादन के लिए रिगोर सेटअप कौशल। इसका उपयोग तब करें जब कार्य विशेष रूप से README-दस्तावेजित रिपॉजिटरी पर कोई रन करने से पहले एक रूढ़िवादी कोंडा-प्रथम वातावरण, चेकपॉइंट और डेटासेट पथ धारणाएं, कैश स्थान संकेत और सेटअप नोट्स तैयार करना हो। रिपॉजिटरी स्कैनिंग, पूर्ण ऑर्केस्ट्रेशन, पेपर व्याख्या, अंतिम रन रिपोर्टिंग, या सामान्य
developmentdevops
explore-run
lllllllama
We need to translate the given English text into Hindi. The text describes a skill called "explore-run" but the instruction says to preserve the name only if it appears in the source text. The name "explore-run" does appear in the source text? Actually, the source text says "Rigor Improve / Rigor Explore run leaf skill" - so "explore-run" is not explicitly written as a single word; it's "Rigor Explore run". But the name to preserve is "explore-run". However, the instruction says "Do not include the name unless it appears in the source text." The name "explore-run" does not appear as such. The source has "Rigor Explore run" which might be interpreted as the skill name. But the user says "Name to preserve: explore-run". I think we should not add it if not in source. The source text includes "Rigor Improve / Rigor Explore run leaf skill" - so "Rigor Explore run" is part of the text. We need to translate that. But the instruction says
researchdevelopmentdata-analysis
safe-debug
lllllllama
गहन शिक्षण अनुसंधान कार्य के लिए रिगोर डिबग / रिगोर ऑडिट कौशल। इसका उपयोग तब करें जब उपयोगकर्ता ट्रेसबैक, टर्मिनल त्रुटि, CUDA OOM, चेकपॉइंट लोड विफलता, आकार बेमेल, NaN हानि लक्षण, या प्रशिक्षण विफलता पेस्ट करता है और किसी भी पैचिंग से पहले रूढ़िवादी निदान चाहता है, जिसमें डिबग फिक्स को शोध योगदान से स्पष्ट रूप से अलग किया गया हो। व्यापक रीफैक्टरिंग, अनुमानात्मक अनु
developmenttestingcode-review
paper-context-resolver
lllllllama
README-प्रथम गहन शिक्षण रिपॉजिटरी पुनरुत्पादन के लिए रिगर पेपर संदर्भ सहायक। केवल तब उपयोग करें जब README और रिपॉजिटरी फ़ाइलें एक संकीर्ण पुनरुत्पादन-महत्वपूर्ण अंतर छोड़ती हैं और कार्य प्राथमिक पेपर स्रोतों से डेटासेट विभाजन, प्रीप्रोसेसिंग, मूल्यांकन प्रोटोकॉल, चेकपॉइंट मैपिंग, या रनटाइम धारणा जैसे किसी विशिष्ट पेपर विवरण को हल करना है, साथ ही विरोधाभासों को र
researchdocumentdata-analysis