PostToolUse (Skill|Read) vs PreToolUse (Write|Edit|MultiEdit|Bash)

Side by side on the facts. GitHub figures come straight from each repository; ratings come from signed-in reviewers here.

MetricPostToolUse (Skill|Read)Hook PreToolUse (Write|Edit|MultiEdit|Bash)Hook

Type: PostToolUse (Skill|Read)Hook; PreToolUse (Write|Edit|MultiEdit|Bash)Hook
Category: PostToolUse (Skill|Read)Other; PreToolUse (Write|Edit|MultiEdit|Bash)Other
GitHub stars: PostToolUse (Skill|Read)0; PreToolUse (Write|Edit|MultiEdit|Bash)0
Trust scoreⓘAuditability and maintenance signals — not a security audit.: PostToolUse (Skill|Read)Not yet assessed; PreToolUse (Write|Edit|MultiEdit|Bash)Not yet assessed
Community rating: PostToolUse (Skill|Read)No reviews yet; PreToolUse (Write|Edit|MultiEdit|Bash)No reviews yet
Last commit: PostToolUse (Skill|Read)Unknown; PreToolUse (Write|Edit|MultiEdit|Bash)Unknown
Licence: PostToolUse (Skill|Read)None declared; PreToolUse (Write|Edit|MultiEdit|Bash)None declared
Official: PostToolUse (Skill|Read)No; PreToolUse (Write|Edit|MultiEdit|Bash)No
Source: PostToolUse (Skill|Read) Repository; PreToolUse (Write|Edit|MultiEdit|Bash) Repository

Highlighted cells win that row on an objective measure. Rows without a clear winner — category, licence, source — are left unmarked. A higher trust score means better auditability and maintenance, not safer code.