Zotero
Analysis
The skill is coherent for Zotero library management, but users should understand it can read and change their Zotero library using an API key.
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.
`delete` | Move items to trash ... `update` | Modify item metadata/tags ... `delete KEY1 --permanent --yes`
The documented commands can modify, bulk add, trash, or permanently delete Zotero items. This is purpose-aligned and disclosed, with some safeguards, but it is still high-impact account mutation capability.
Source: unknown Homepage: none
The registry metadata does not provide a verifiable source repository or homepage, which is a provenance gap for a skill that handles API credentials and account mutations.
Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.
Requires two environment variables: ZOTERO_API_KEY ... ZOTERO_USER_ID ... For group libraries, set `ZOTERO_GROUP_ID` instead of `ZOTERO_USER_ID`.
The skill needs a Zotero API key and user or group library identifier, which is expected for Zotero Web API management but grants account-level library access depending on the key permissions.
Checks for exposed credentials, poisoned memory or context, unclear communication boundaries, or sensitive data that could leave the user's control.
Optional env var for CrossRef/Unpaywall polite pool ... `CROSSREF_EMAIL` ... Tries three legal OA sources in order: Unpaywall → Semantic Scholar → DOI content negotiation.
The skill discloses external provider calls for DOI lookup and open-access PDF discovery, which may send citation metadata, DOIs, and optionally an email address to third-party services.
