Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Quotation Generator
v1.0.0Auto-generate professional PDF proforma invoices with company letterhead, multi-language support, and post-quote tracking.
⭐ 0· 39·1 current·1 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
high confidencePurpose & Capability
The stated purpose (generate/send proforma invoices and track post-quote status) is coherent, but the SKILL.md expects the agent to send drafts via WhatsApp, update a CRM, and read product-kb/catalog.json. None of these external integrations or file accesses are declared in the skill metadata (no required env vars, no config paths). That discrepancy is disproportionate to the declared requirements.
Instruction Scope
Runtime instructions explicitly instruct the agent to read product-kb/catalog.json, send drafts to the owner via WhatsApp, send final quotes to customers, and update CRM records and attachments. Those are concrete I/O operations involving local files and third-party services; the instructions do not specify which CRM, which WhatsApp API/endpoint, or how credentials/addresses are provided, creating ambiguity and risk of unauthorized data access or unintended exfiltration.
Install Mechanism
No install spec and no code files (instruction-only). That lowers installation risk since nothing is downloaded or written to disk by the skill itself.
Credentials
The skill declares no required environment variables or primary credential, yet its workflow requires credentials/tokens to use WhatsApp and a CRM, and access to product-kb files. This mismatch means the skill will need access to secrets or filesystem paths that are not communicated up-front — disproportionate and potentially dangerous.
Persistence & Privilege
always is false and the skill does not request persistent system-wide changes or modifications to other skills. Autonomous invocation is allowed (platform default) but not combined with additional privileges.
What to consider before installing
This skill could do what it says, but it currently leaves out critical operational details. Before installing or enabling it: 1) Require the author to declare the exact external integrations (which WhatsApp API/provider, which CRM) and list the specific environment variables (e.g., WHATSAPP_API_TOKEN, CRM_API_KEY) and config path(s) (e.g., product-kb/catalog.json) the skill needs. 2) Limit filesystem access to an explicit, sandboxed path and avoid granting wide read permissions. 3) Verify how owner approval via WhatsApp is authenticated (phone spoofing risk); prefer an out-of-band confirmation rather than unconditional send. 4) Ensure least-privilege credentials (scoped API tokens) and logging/audit for message sends and CRM updates. 5) Get clarity on handling of customer PII and attachments and confirm compliance with privacy rules. If the author cannot provide the above or if the skill would require you to paste high-privilege tokens into a generic agent, treat it as high-risk and do not enable it in production.Like a lobster shell, security has layers — review code before you run it.
latestvk971gkytnn2bb2mvr9vqhh2a55842v8z
License
MIT-0
Free to use, modify, and redistribute. No attribution required.