Transparency is part of the installation model
The recommended manual installation is to save the published SKILL.md into the local Claude skills directory. The homepage displays the file so a user can inspect it before giving Claude permission to execute its commands.
Convenience installers are also available, but piping a remote script directly into a shell trades away that moment of review. The site explicitly presents manual installation as the more transparent path.
Common policy customizations
Because the behavior is ordinary shell code and instructions, individuals and teams can make the workflow more conservative. Customizations stay local unless you intentionally distribute the modified skill.
- Require a yes/no confirmation immediately before upload.
- Block sharing from named repositories or directory prefixes.
- Add proprietary token formats to the redaction list.
- Remove all tool results or image blocks before transmission.
- Point development copies at a local or self-managed endpoint.
Readable does not automatically mean safe
A skill can execute shell commands with the permissions available to Claude Code. Read the installed copy, review updates before replacing it, and understand any local changes. Transparency makes inspection possible; the user still has to exercise that control.