Enterprise Knowledge Base Reader

PassAudited by ClawScan on May 10, 2026.

Overview

This is a coherent read-only enterprise knowledge-base reader, but users should notice that it uses embedding-provider API keys, sends query text to that provider, and reads from a shared local knowledge-base store.

This skill appears suitable if you want a read-only enterprise KB search tool. Before installing, confirm the shared KB directory contains data the agent is allowed to read, use an approved DashScope/OpenAI-compatible embedding provider, keep API keys out of source-controlled config files, and consider pinning dependencies for production use.

Findings (6)

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.

What this means

The agent may consult this KB before answering many business-related questions, which can be helpful but may be broader than some users expect.

Why it was flagged

The skill explicitly instructs the agent to prioritize KB retrieval for a broad range of business questions; this is aligned with the skill’s purpose but affects tool-use behavior.

Skill content
用户提出任何业务问题、产品咨询、公司政策、员工手册、操作流程、规章制度、FAQ、项目信息等问题时,必须优先调用本知识库检索相关内容
Recommendation

Install it only where automatic KB consultation for business topics is desired, and give the agent explicit instructions when a question should not use this knowledge base.

What this means

Users must provide a valid embedding-provider key, and that key authorizes calls to DashScope or OpenAI-compatible services.

Why it was flagged

The skill requires provider API credentials for embeddings, even though registry metadata lists no primary credential or required env vars.

Skill content
$env:DASHSCOPE_API_KEY='your-dashscope-key' ... $env:OPENAI_API_KEY='your-openai-key'
Recommendation

Use a least-privilege or dedicated API key where possible, keep it in environment variables rather than checked-in config files, and monitor provider usage.

What this means

Business questions or other text entered as queries may leave the local machine and be processed by DashScope or OpenAI, depending on configuration.

Why it was flagged

User query text is sent to the configured embedding provider to generate an embedding vector.

Skill content
response = self.client.embeddings.create(
                model=self.model,
                input=text
            )
Recommendation

Avoid entering highly sensitive queries unless the configured provider is approved for that data, and review the provider’s data-handling policy.

What this means

Answers may include or rely on stored enterprise documents, including any inaccurate or poisoned content that an administrator previously added to the KB.

Why it was flagged

The skill retrieves persistent enterprise KB content from a shared local data store and uses it to answer user questions.

Skill content
kb-data/
├── chroma_db/     # 向量数据库 (只读访问)
└── documents/     # 原始文档 (只读访问)
Recommendation

Use this only with a curated KB, maintain access controls on the shared KB directory, and treat retrieved content as reference material rather than unquestionable authority.

What this means

The installed dependency set may change over time, which can affect reliability and supply-chain risk.

Why it was flagged

Dependencies are installed from package indexes using lower-bound version ranges, so future installs may resolve to different package versions.

Skill content
chromadb>=0.4.15
openai>=1.3.0
dashscope>=1.14.0
numpy>=1.24.0
Recommendation

Prefer a pinned requirements file or lockfile in managed environments, and install from trusted package sources.

What this means

Users could overestimate how API keys are protected if they place them in configuration rather than using environment variables.

Why it was flagged

The documentation claims encrypted key storage, but the supplied code only shows environment/config loading for API keys and does not show an encryption mechanism.

Skill content
API安全: 支持多种API提供商,密钥加密存储
Recommendation

Do not rely on encrypted key storage unless the implementation is separately verified; keep secrets in approved secret-management mechanisms or environment variables.