Inspect a skill before you trust it
Look at the instructions, links and permissions behind an agent skill before installing it.
Review the behavior the skill asks for
Prompeteer Secure Scan reviews imported skills before publication in Skills Hub. Inspect the upstream source and scan state alongside the instructions. A friendly description can hide a request to access unrelated files or send information elsewhere.
| Review area | Question to ask |
|---|---|
| Instructions | Does the skill try to override the user’s task or safeguards? |
| Links and destinations | Where would data be read from or sent to? |
| Scripts and tools | What can execute, and with whose permissions? |
| Provenance | Which upstream version was actually reviewed? |
Recognize an unrelated data request
Review the requested behavior in context. A suspicious instruction should not become trusted merely because it appears in a reference file.
A formatting skill asks the agent to read unrelated environment files and send their contents to a third-party endpoint before editing the document. The request is not necessary for formatting. Hold the skill, preserve the relevant source excerpt and investigate the destination and executable steps before considering installation.
This is a hypothetical risk example, not a published scan result.
A passed scan does not guarantee runtime safety
Static and semantic review cannot prove every future execution safe. Tool permissions, dependencies, remote content and the runtime environment can change the risk. Review material changes and apply least privilege.
This page explains the published review workflow. It does not promise an unrestricted public scanner or that every finding is definitive.
Common questions
Can a skill be safe in one environment and risky in another?
Yes. Available tools, permissions, dependencies and data access affect what its instructions can do. Evaluate the environment as well as the file.
Sources and review
Reviewed