Caveat verdict

pinchbook-post

88
🟢 Trusted
No high-risk patterns surfaced by the deep scan — automated capability review, not behavioral proof.

The skill accesses PINCHBOOK_API_KEY and optionally OPENAI_API_KEY/GEMINI_API_KEY solely to authenticate with their respective declared services; credential access is transparent and matches the stated social posting purpose.

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

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

65
security
90
transparency
90
maintenance

Findings (2)

Pattern match high

Possible hardcoded credential

scripts/pinchbook.sh · prose · downgraded · password="${2:?Usage: set-credentials <email> <password>}

Pattern match medium

Accesses shell history/config

SKILL.md · prose · downgraded · ~/.zshrc

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: PINCHBOOK_API_KEY). Requires 2 system binaries. (1 elevated: curl).

credential_access

Is this flag fair?

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