Goal: - Validate one Co-Scientist run directory from Claude Code. Expected input: - one run directory such as `runs/test1` Execution steps: 1. Resolve the run directory. 2. Decide whether the user wants a fresh-run validation or a resume validation. 3. Run one of: ```bash python -m tools.validation.contract_validation <run-dir> --skill co-scientist-pipeline ``` or ```bash python -m tools.validation.contract_validation <run-dir> --resume --skill co-scientist-pipeline ``` 4. Read and summarize ...
Scanned 9/7/2026
Install to Claude Code
Skills Directorynpx -y skills add panjose/Co-Scientist --skill co-scientist-validate --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Co Scientist Validate?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/panjose-co-scientist-validate)More formats (shields.io, HTML) on the badges page.
# co-scientist-validate
Goal:
- Validate one Co-Scientist run directory from Claude Code.
Expected input:
- one run directory such as `runs/test1`
Execution steps:
1. Resolve the run directory.
2. Decide whether the user wants a fresh-run validation or a resume validation.
3. Run one of:
```bash
python -m tools.validation.contract_validation <run-dir> --skill co-scientist-pipeline
```
or
```bash
python -m tools.validation.contract_validation <run-dir> --resume --skill co-scientist-pipeline
```
4. Read and summarize the validation result without rewriting the run artifacts unless the user asked for a fix.
Rules:
- This entry skill is a thin Claude Code surface over `tools.validation.contract_validation`.
- Keep the validator as the source of truth for run readiness.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
