Overleaf
Analysis
This Overleaf skill is coherent, but it asks the user to grant browser-cookie/keychain access and includes account-changing workflows that should be reviewed carefully before use.
Findings (4)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.
The agent can accept Overleaf project invitations programmatically ... no manual clicking required.
The invite workflow uses authenticated browser cookies to change account/project state, and the provided code pattern iterates through pending invites rather than requiring an explicit confirmed target by default.
pyoverleaf (`pipx install pyoverleaf`) ... We have audited pyoverleaf v0.1.7 and found it safe.
The install command does not pin the package to the audited version, while the package is expected to handle browser cookies and authenticated Overleaf operations.
We have audited pyoverleaf v0.1.7 and found it safe.
The artifact provides a broad safety assurance without including audit evidence, and the recommended install path is not pinned to that audited version.
Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.
pyoverleaf needs "Always Allow" keychain access to read browser cookies. This grants the tool access to your browser's cookie storage.
The skill relies on local browser session cookies and keychain access rather than a scoped Overleaf credential, giving the third-party CLI access to sensitive authentication material.
