Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Quotation Workflow
v3.0.0自动化生成报价单(Excel/Word/HTML/PDF),集成数据验证防止示例数据,支持 OKKI CRM
⭐ 1· 91·1 current·1 all-time
byJaden's built a claw@cjboy007
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
high confidencePurpose & Capability
Name/description, scripts, and docs align with an automated quotation generator (HTML/Word/Excel/PDF) and built-in validation. However the metadata/os/binaries list is incomplete or inconsistent: SKILL.md and docs repeatedly call soffice (LibreOffice) for PDF conversion and reference node smtp/okki scripts, but the registry requires only 'chrome' and 'python3' and declares no required credentials. The OS restriction to 'darwin' also appears unnecessary given cross-platform Python/LibreOffice/Chrome usage.
Instruction Scope
Runtime instructions tell the agent to run local Python scripts, Chrome headless, and LibreOffice conversions and to read/write local files — which is expected. But the SKILL.md and various scripts reference environment variables (QUOTATION_DEV_ENV), other skills (imap-smtp-email), and OKKI sync/HTTP calls in future work; those cross-skill/service interactions expand scope and are not fully documented. The skill does not instruct sending data to unknown remote endpoints in the provided excerpts, but it does plan OKKI/SMTP integration (placeholders) which would introduce network access and credential use.
Install Mechanism
No install spec (instruction-only plus included scripts). Nothing in the manifest downloads code at install time; scripts are local files. This minimizes install-time risk.
Credentials
The code and docs rely on an environment variable QUOTATION_DEV_ENV to gate --skip-validation, but the skill declares no required env vars. The docs and workflow also reference SMTP/OKKI integrations which will require credentials, yet no credentials/config paths are declared. Additionally, LibreOffice (soffice) is used in examples but not declared as a required binary. These omissions make the declared environment/credential requirements incomplete and unpredictable.
Persistence & Privilege
The skill does not request 'always: true' or modify other skills' configurations. It is user-invocable and can be run autonomously (platform default) but does not demand elevated or persistent platform privileges.
What to consider before installing
This skill appears to implement the advertised quotation workflow, but there are several practical inconsistencies you should resolve before installing or letting an agent run it autonomously:
- Review env-var use: the scripts check QUOTATION_DEV_ENV to allow --skip-validation, but that variable is not declared in the skill metadata. If you plan to use skip-validation, be explicit about where/how QUOTATION_DEV_ENV is set and restrict it to dev shells.
- Check required binaries: examples and docs use 'soffice' (LibreOffice) for PDF conversion but the metadata only lists 'chrome' and 'python3'. Install and test LibreOffice or update the skill metadata to include it.
- Audit cross-skill/service calls: the skill references OKKI and SMTP flows (okki-sync.js, smtp.js). If you enable those, they will require credentials (OKKI API keys, SMTP creds). Those credentials are not declared — verify how and where they will be provided and stored before enabling integrations.
- Inspect scripts for network activity: currently OKKI verification is a placeholder, but future P1/P2 work intends network calls. Search the repository for HTTP/network libraries (requests, urllib, node fetch) and confirm endpoints and auth behavior.
- Test in isolation: run the validation and generation scripts locally on non-sensitive sample files to confirm behavior (they call sys.exit(1) on validation failure, which blocks automation when appropriate).
- Principle of least privilege: only provide external credentials (CRM, SMTP) to the agent if you trust and have reviewed the code that will use them; prefer injecting credentials at runtime rather than baking them into environment or repository.
If you want, I can: (1) list all places the code references environment variables and external programs, (2) scan the scripts for network calls and external endpoints, or (3) produce a short checklist of changes to make the skill metadata consistent (declare soffice and QUOTATION_DEV_ENV, and enumerate required credentials if OKKI/SMTP will be used).Like a lobster shell, security has layers — review code before you run it.
latestvk978awbsvfnh1epyrxxht2z2ts83pwpk
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
📋 Clawdis
OSmacOS
Binschrome, python3
