OpenAlexandria
AdvisoryAudited by Static analysis on Apr 30, 2026.
Overview
No suspicious patterns detected.
Findings (0)
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.
An agent could upload research results or user-provided material to OpenAlexandria when the user only expected a search or local assistance workflow.
This instructs agent-side submission after research, but does not require explicit user approval or define what content is safe to submit to the external/federated service.
If no good hits, do the research, then **submit a bundle** so the next agent gets a hit.
Only submit bundles after explicit user approval, and add guidance to exclude secrets, private documents, unpublished work, personal data, and customer/business-confidential content.
Anyone or any agent using the configured key can submit content and check account-related limits/status for OpenAlexandria.
The skill discloses API-key use for submissions and whoami; this is expected for the integration, but users should understand that submissions happen under that account/key.
Submissions require an OpenAlexandria API key ... export OPENALEXANDRIA_API_KEY="oa_..."
Use a scoped key if available, avoid passing keys on shared command lines, and revoke or rotate the key if unwanted submissions occur.
Search results from the node may contain inaccurate, untrusted, or intentionally manipulative content that could influence the agent's answer.
The skill encourages using retrieved federated knowledge as context, while also noting that stronger trust, signature, and reputation layers are not yet present.
Before web search, query OpenAlexandria for likely cache hits... Trust/signatures/reputation are layered in Phase II.
Treat OpenAlexandria results as untrusted hints, verify important claims against primary sources, and avoid letting retrieved content override the user's instructions.