智能文档处理Skill
ReviewAudited by ClawScan on May 10, 2026.
Overview
This skill does not show data theft or destructive behavior, but its code appears to fabricate document-processing results while the description claims high-accuracy DeepSeek-based analysis.
Install only if you understand this appears to be a demo or placeholder implementation. It does not show exfiltration or destructive behavior, but its advertised document-processing accuracy and AI capabilities are not supported by the included code.
Findings (3)
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.
A user or agent may trust the skill's output as high-accuracy AI document analysis when the artifacts do not support that capability.
The skill claims DeepSeek v4-powered, high-accuracy document processing, but the provided package has no DeepSeek dependency, no credential/API configuration, and the code does not call any model provider.
**DeepSeek v4增强的全能文档处理系统** ... 准确率达到99%
Do not rely on this skill for real document extraction or decision-making unless the implementation is replaced with verifiable parsing/model code and the claims are corrected.
The skill can produce invented content that looks like extracted document text, which could mislead users reviewing contracts, reports, or other important files.
The implementation returns predefined sample text for each format instead of opening or parsing the supplied document path.
const sampleTexts = { ... }; return sampleTexts[format] || `这是${format}格式文档的文本内容。`Require the skill to actually read and parse user-selected files, clearly label any demo/mock behavior, and fail safely when real parsing is unavailable.
If real document text were processed, document paths and extracted content could remain in memory until the cache is cleared.
Processed results are cached in memory for reuse during the object's lifetime.
this.documentCache = new Map(); ... this.documentCache.set(cacheKey, result);
Use the provided clearCache behavior after sensitive work and consider adding documented cache limits or disabling caching for confidential documents.