Project Integrity Check

VerifiedSafe

Run a two-phase integrity check covering pipeline consistency (scripts, data, parameters) and manuscript audit (figures, references, orphans).

Sby Skills Guide Bot
DevelopmentIntermediate
1008/12/2026
Claude CodeCursorWindsurfCopilotCodex
#integrity-check#reproducibility#pipeline-audit#manuscript-audit

Recommended for

Our review

This skill performs a two-phase audit of a research project, verifying pipeline integrity (scripts, data, params) and manuscript consistency (figures, tables, references).

Strengths

  • Comprehensive check of both code and manuscript
  • Catches missing files and undocumented references
  • Clearly separates pipeline and manuscript audits
  • Non-destructive (doesn't fix without approval)

Limitations

  • Requires README tables and params.do to be up-to-date
  • Assumes a specific project structure
  • May produce many findings if project is not well-maintained
When to use it

Use before submission or after significant changes to ensure all outputs are reproducible and manuscript references are valid.

When not to use it

Not for ad-hoc checks or when the project lacks structured README tables and parameter files.

Security analysis

Safe
Quality score85/100

This skill is a manual checklist for project integrity checks. It does not instruct the AI to execute any commands, access external resources, or take destructive actions. It poses no execution risk.

No concerns found

Examples

Run full integrity check
Run the full project integrity check for this repository.
Check manuscript references
Audit only Phase 2 — verify all figure and table references in manuscript.tex resolve to existing files.
Verify pipeline files
Run Phase 1 to ensure every script and data file in the README pipeline table exists and is in the correct directory.

Run a full project integrity check. Two phases:

Phase 1 — Pipeline integrity: (1) Every script listed in README pipeline table exists. (2) Every input data file listed exists. (3) No scripts or data files sitting in wrong directories. (4) Output directories exist. (5) params.do values match README parameters table.

Phase 2 — Manuscript audit: (1) Every entry in README table/figure map has an existing output file and source script. (2) Every \includegraphics and \input in manuscript.tex resolves to an existing file. (3) Find any output files not referenced in the manuscript (orphans). (4) Find any manuscript references not in the table/figure map (undocumented).

Report all findings. Do not fix anything without user approval.

Related skills