ClawAudit verdict

contact-discovery

88
🟢 Trusted
Low risk — reviewed by ClawAudit, behavior matches stated purpose

Public contact discovery using Prismfy API; PRISMFY_API_KEY used transparently for documented search service, file_write is for saving reports, behavior matches stated pre-outreach research purpose.

⚠ Flagged for review — coarse, uncorroborated signal, not a confirmed exploit. Review the config yourself before installing.

Automated static analysis — not a human review. ClawAudit flags capabilities, not confirmed intent, and can produce false positives. Disagree with this verdict? Use Dispute below.

58
security
60
transparency
90
maintenance

Permission integrity

Performs file operations but does not declare file-accessing binaries

file_read+write

Findings (1)

Pattern match critical

Possible hardcoded credential

SKILL.md · code · API_KEY="ss_live_your_key_here

Why the tier is capped

Execution sink present in raw bytes (Hard Floor: class F). Final tier capped at Caution — cannot be lifted by any downgrade, example-payload opt-in, or allowlist.

Permissions & capabilities

Requires 1 environment variable. (1 sensitive: PRISMFY_API_KEY). Requires 2 system binaries. (1 elevated: curl).

file_write

Is this flag fair?

Check another skill Browse the registry Auditing your own skills or configs? Use the API