Security audit
Security checks for vulnerabilities and agentic risk
The skill is mostly aligned with enterprise knowledge management, but its command/file authority, broad triggers, and under-described external data flows need human review before installation.
Review this skill before installing in an environment with private documents or shared team data. Use it only for the intended knowledge-base workflows, confirm the know CLI and storage locations, avoid callback_url unless the endpoint is trusted, and keep cloud embedding/API credentials in environment variables or a secret store. Review sync, permission, invite, and export commands before allowing execution.
The skill claims no extra API key is needed, but elsewhere states that cloud embedding models and external API services may be used. This inconsistency can mislead operators into enabling external integrations without properly planning credential handling, causing accidental secret exposure or unexpected data egress to third-party services.
The trigger condition is much broader than the skill's stated knowledge-management purpose, expanding use to generic data analysis, reporting, and visualization tasks. In an agent ecosystem, this can cause the skill to be invoked in unrelated contexts where it has powerful exec/write capabilities, increasing the chance of overreach, unsafe command execution, or unintended handling of sensitive data.
The skill supports a callback_url for asynchronous completion but does not clearly warn that results or metadata may be sent to an external destination. This creates a data exfiltration risk because users or downstream agents may supply arbitrary URLs, causing sensitive knowledge-base content, logs, or identifiers to be transmitted off-platform without informed consent.
No suspicious patterns detected.
