Review Standards

A new shared resource should be reviewed for:

Correct location and naming
Valid frontmatter and discovery text
Portability expectations
Security implications, especially for hooks and scripts
Clear purpose and expected usage
Duplication with existing resources
Cheapest sufficient primitive for the intended workflow
Justified context size, including whether long examples or repeated guidance can be moved into docs or scripts instead
An intentional default output budget instead of open-ended verbosity
Clear limits on when the resource should not be used

Audit candidates should also be reviewed for:

Clear provenance back to an audit summary or selection manifest
Portable fit as a skill, instruction, prompt adapter, agent, hook, script, or template
Absence of secrets, machine-specific paths, or repo-specific assumptions
A justified decision when the right outcome is template-only, docs-only, or discard