Automated summary
Runs a full project integrity audit in two phases: pipeline verification and manuscript reference checking.
Strengths
- Checks both code/data pipeline and manuscript outputs
- Detects orphaned files and missing references
- Does not modify anything without user approval
Limitations
- Assumes a specific README structure with pipeline tables and figure/map listings
- Requires all files to be in expected directories
- May not cover all project-specific conventions
When you need to ensure a reproducible research project is complete and consistent before sharing or submission.
When the project does not follow a README-based structure or you need to fix issues automatically.
Security analysis
SafeSkill performs read-only integrity checks without executing any scripts or making changes; no network access, system modification, or risky tools are employed.
No concerns found
How this analysis is madeExamples
Run the project integrity check on this repository and report all findings.Check the manuscript.tex references and table/figure map for any missing files or undocumented outputs.Verify that all scripts and data files listed in the README pipeline table exist and are in the correct directories.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.
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/project-integrity-check-ms9wnz1o/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/project-integrity-check-ms9wnz1o' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/project-integrity-check-ms9wnz1o/download' --output '.skill-downloads/project-integrity-check-ms9wnz1o/SKILL.md.part' && mv '.skill-downloads/project-integrity-check-ms9wnz1o/SKILL.md.part' '.skill-downloads/project-integrity-check-ms9wnz1o/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
This file does not provide a usable name/description header for this native procedure. It remains available to download and inspect; use the manual method below.
Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/project-integrity-check-ms9wnz1o/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.