speckit-specify

SUSPICIOUS. The core purpose and file access are consistent with a specification-writing skill, and the static command-injection hits are benign documentation artifacts. The main risk is automatic execution of project-defined mandatory hooks from `.specify/extensions.yml`, which creates a transitive trust/autonomy surface if the repo is untrusted.