Content
40%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is structurally okay — real, clearly signaled reference files and a scripts directory — but it is padded with generic senior-engineer boilerplate, its Quick Start commands point to stub scripts, and it lacks any sequenced workflow with validation checkpoints for its destructive/batch operations.
Suggestions
Cut the generic boilerplate sections ('Core Expertise', 'Best Practices', 'Senior-Level Responsibilities') and keep only data-science-specific guidance Claude would not already know.
Replace the stub scripts (bodies are '# Implementation here') with real executable logic, or remove the commands until the tools actually work.
Add a sequenced end-to-end workflow (e.g., design experiment -> validate config -> run -> evaluate -> check metrics) with explicit validation checkpoints before any deploy/training step.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Large sections ('Core Expertise', 'Best Practices', 'Senior-Level Responsibilities', 'Security & Compliance') are generic senior-engineer boilerplate Claude already knows ('Test-driven development', 'Monitor everything critical', 'Mentor junior engineers'), adding noticeable padding without data-science-specific signal. | 2 / 5 |
Actionability | Concrete command invocations are present ('python scripts/experiment_designer.py --input data/ --output results/'), but they point at stub scripts whose bodies are '# Implementation here' / '# Add validation logic', and the rest are generic tool commands, leaving the guidance incomplete rather than copy-paste ready. | 3 / 5 |
Workflow Clarity | There is no real sequenced workflow — 'Quick Start' lists three independent commands in parallel — and destructive/batch operations like '--deploy' and training carry no validation or verification checkpoints, so the content stays well below the cap of 3. | 2 / 5 |
Progressive Disclosure | References to references/statistical_methods_advanced.md, experiment_design_frameworks.md, and feature_engineering_patterns.md are real, one level deep, and clearly signaled in dedicated 'Reference Documentation' and 'Resources' sections, though the body still carries generic inline content that could be trimmed. | 4 / 5 |
Total | 11 / 20 Passed |