demis-hassabis Eval report.

Validation plan

What the agent should do next

1. 1Inspect repository, README/SKILL.md, license, and recent commits before production use.
2. 2Install in an isolated workspace or sandbox with no production secrets available.
3. 3Run the smallest representative task and record files touched, commands run, network access, and outputs.
4. 4Compare the selected skill against at least one alternative when the eval status is review or failed.
5. 5Promote only after the agent reports a successful verification result and unresolved warnings are accepted.

Do not use when

Conditions that require another skill

• teams that need a vendor-supported SLA
• production agents without a repository review
• SKILL.md references references/principles.md, references/mental-models.md, and references/frameworks.md, but these files are not present in the submitted skill directory; broken references reduce completeness.
• The skill lacks explicit limitations and safe operating boundaries; it should clarify that it is a reasoning framework and not a substitute for domain expertise or safety review.
• The internal critique files (critique_agents.json, critique_skill.json) are included in the workspace, which may clutter the skill; consider removing generated artifacts.
• Quality score needs review