Review method
How we review a skill.
Our listing is an editorial assessment of a specific public source folder on a specific date. It helps you decide what to inspect next; it is not a safety certification.
What we verify
For each third-party listing, we use the public repository tree to confirm the folder and SKILL.md, read the applicable root or folder license, and record the latest folder commit we could find. We read the instruction file and inspect the folder contents. Reviews explain the intended use, when it may be a poor fit, and the presence of scripts or network steps. We link to the maintainer’s files instead of mirroring their SKILL.md.
What we check in our own release
For Five-Field Handoff, we read every text file, run our local pack scanner, build a versioned archive, and publish its SHA-256 beside the download. The current archive has no executable script or network action. A matching hash lets you compare bytes with this release, but cannot prove the instructions or results will be suitable for every use.
Limits of a review
A maintainer can update a repository after our check. Scripts and dependencies may behave differently in another environment. An AI agent may also interpret instructions unexpectedly. Read current source before installation, test with limited permissions, and review commands before execution. We do not run every third-party skill or certify downstream tools.
Report a concern
Email [email protected] with the listing URL, the source revision if known, and a clear description. Please avoid sending credentials or private project data. We will examine credible reports and correct or remove a listing where warranted.
Removal request
Maintainers may ask us to remove or correct a listing. Send the repository link and the reason to the same address. We will review the request and act within a reasonable time.