Run any Skill in Manus with one click

analyze-project

Stars506

Forks9

UpdatedMay 18, 2026 at 03:58

Rigor Analyze / Rigor Audit read-only skill for deep learning research repositories. Use when the user wants to read and understand a repository, inspect model structure and training or inference entrypoints, review configs and insertion points, or flag suspicious implementation patterns without modifying code or running heavy jobs. Do not use for active command execution, broad refactoring, speculative code adaptation, or automatic bug fixing.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

lllllllama

lllllllama/RigorPilot-Skills

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Data ScientistsComputer and Mathematical Occupations·SOC 15-2051

File Explorer

4 files

SKILL.md

readonly

name

analyze-project

description

analyze-project

Use this as the Rigor Analyze / Rigor Audit read-only skill. The installed slug remains analyze-project for compatibility.

Use the shared operating principles in ../../references/agent-operating-principles.md; this skill should guide read-only analysis without constraining the model's project-specific reasoning.

When to apply

The user wants to understand a deep learning repository before changing it.
The user needs a map of model structure, training entrypoints, inference entrypoints, and config relationships.
The user wants conservative suggestions about likely insertion points or suspicious implementation patterns.
The user explicitly wants read-only analysis and not heavy execution.

When not to apply

When the main task is to execute a failing command or debug a traceback.
When the user wants environment setup or asset download only.
When the user wants speculative adaptation or broad exploratory patching.
When the task is a general literature summary without repository analysis.

Clear boundaries

This skill is read-mostly.
It may run lightweight static inspection helpers.
It does not patch repository code.
It does not own final reproduction outputs.
It should mark suspicious patterns as heuristics, not confirmed bugs.

Output expectations

analysis_outputs/SUMMARY.md
analysis_outputs/RISKS.md
analysis_outputs/status.json

Notes

Use references/analysis-policy.md and the shared references/research-pitfall-checklist.md.

More from this repository

same repository

ai-research-explore

lllllllama/RigorPilot-Skills

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, narrow code-only or run-only exploration, passive repo analysis, verified novelty claims, or implicit experimentation.

2026-05-18506

ai-research-reproduction

lllllllama/RigorPilot-Skills

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.

2026-05-18506

env-and-assets-bootstrap

lllllllama/RigorPilot-Skills

Rigor Setup skill for README-first deep learning repo reproduction. Use when the task is specifically to prepare a conservative conda-first environment, checkpoint and dataset path assumptions, cache location hints, and setup notes before any run on a README-documented repository. Do not use for repo scanning, full orchestration, paper interpretation, final run reporting, or generic environment setup that is not tied to a specific reproduction target.

2026-05-18506

explore-code

lllllllama/RigorPilot-Skills

Rigor Improve implementation leaf skill for auditable candidate implementation in deep learning research repositories. Use when the researcher explicitly authorizes exploratory work on an isolated branch or worktree to transplant modules, adapt a backbone, add LoRA or adapter layers, replace a head, or stitch together meaningful low-risk migration ideas with rollback-aware records in `explore_outputs/`. Do not use for end-to-end exploration orchestration on top of `current_research`, trusted baseline reproduction, conservative debugging, environment setup, verified contribution claims, or default repository analysis.

2026-05-18506

explore-run

lllllllama/RigorPilot-Skills

Rigor Improve / Rigor Explore run leaf skill for bounded exploratory evidence in deep learning research repositories. Use when the researcher explicitly authorizes exploratory runs such as small-subset validation, short-cycle guess-and-check, batch sweeps, idle-GPU search, or quick transfer-learning trials, with fair-comparison caveats and no-overclaim summaries in `explore_outputs/`. Do not use for end-to-end exploration orchestration on top of `current_research`, trusted baseline execution, conservative training verification, default routing, verified SOTA claims, or implicit experimentation.

2026-05-18506

minimal-run-and-audit

lllllllama/RigorPilot-Skills

Rigor Run skill for README-first deep learning repo reproduction. Use when the task is specifically to capture or normalize evidence from the selected smoke test or documented inference or evaluation command and write standardized `repro_outputs/` files, including patch notes when repository files changed. Do not use for training execution, initial repo intake, generic environment setup, paper lookup, target selection, hidden scientific-meaning changes, or end-to-end orchestration by itself.

2026-05-18506

name

analyze-project

description

analyze-project

Use this as the Rigor Analyze / Rigor Audit read-only skill. The installed slug remains analyze-project for compatibility.

Use the shared operating principles in ../../references/agent-operating-principles.md; this skill should guide read-only analysis without constraining the model's project-specific reasoning.

When to apply

The user wants to understand a deep learning repository before changing it.
The user needs a map of model structure, training entrypoints, inference entrypoints, and config relationships.
The user wants conservative suggestions about likely insertion points or suspicious implementation patterns.
The user explicitly wants read-only analysis and not heavy execution.

When not to apply

When the main task is to execute a failing command or debug a traceback.
When the user wants environment setup or asset download only.
When the user wants speculative adaptation or broad exploratory patching.
When the task is a general literature summary without repository analysis.

Clear boundaries

This skill is read-mostly.
It may run lightweight static inspection helpers.
It does not patch repository code.
It does not own final reproduction outputs.
It should mark suspicious patterns as heuristics, not confirmed bugs.

Output expectations

analysis_outputs/SUMMARY.md
analysis_outputs/RISKS.md
analysis_outputs/status.json

Notes

Use references/analysis-policy.md and the shared references/research-pitfall-checklist.md.