Content
46%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 well-structured for progressive disclosure with real bundle files referenced one level deep, but it is weighed down by generic, non-CV-specific boilerplate bullet lists and lacks concrete executable CV code and validation checkpoints in its workflows. Actionability and workflow clarity are mid-range; conciseness is the weakest dimension.
Suggestions
Cut generic sections ('Core Expertise', 'Best Practices', 'Senior-Level Responsibilities') that restate what Claude already knows and replace them with concrete CV-specific guidance.
Add copy-paste-ready code examples for the core workflows (e.g., a minimal YOLO training snippet, a SAM segmentation call) instead of one-line CLI hints.
Add explicit validation checkpoints to training and deployment workflows (e.g., validate dataset, evaluate metrics before deploy, rollback on drift) to lift workflow clarity above 3.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is padded with generic bullet lists ('Advanced production patterns', 'Scalable system design', 'Team leadership and mentoring') that explain nothing CV-specific Claude does not already know, with several unnecessary boilerplate sections; noticeably below the efficient midpoint. | 2 / 5 |
Actionability | Provides real executable script invocations ('python scripts/vision_model_trainer.py --input data/ --output results/') and common commands, but most guidance is abstract bullet lists rather than concrete, copy-paste CV code, leaving it incomplete. | 3 / 5 |
Workflow Clarity | Training and deployment are presented as one-liners with no sequenced steps or validation checkpoints; for batch/destructive operations like model training and production deployment the missing validation/feedback loops cap this at 3 per the rubric. | 3 / 5 |
Progressive Disclosure | The overview points to three real, one-level-deep reference files (confirmed present in references/) and the scripts/ directory, clearly signaled and listed in both a Reference Documentation section and a Resources section; held at 4 because some reference summaries repeat inline rather than being fully split out. | 4 / 5 |
Total | 12 / 20 Passed |