Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
CNC Quote Workflow
v2.0.2CNC智能报价Workflow - 多Agent协作闭环。从黑盒24h到白盒10min。主赛道Workflow Hacker + 副赛道Agent Worker。
⭐ 0· 71·1 current·1 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The skill advertises a 3-agent workflow (parser → RAG → meta-cognition) and 10‑minute white‑box quoting, but the code/configuration actively forces a Rule-Only (pure math) fallback in production mode. Several modules the multi-agent flow depends on (case_retriever, risk_control, uniskill-v4) are not bundled; given config.json sets stability.mode='production' the engine's _should_fallback() returns True and the full multi-agent pipeline will be skipped in typical runs. This is an internal inconsistency between claimed capabilities and what will actually run.
Instruction Scope
Runtime instructions are simple (pip install pyyaml; import and run WorkflowEngine). The code reads its local config.json and may insert an absolute path '/home/admin/.openclaw/workspace/skills/uniskill-v4' into sys.path to enable UniSkill optionally. That path insertion would cause the runtime to load local code if present — not inherently malicious but worth noting. There are no network endpoints, no secret reading, and no broad file system reads beyond the skill folder and an optional user path.
Install Mechanism
This is an instruction + code bundle with no install spec; dependencies are minimal (pyyaml). No downloads from external URLs or archive extraction are present. Risk from install mechanism is low.
Credentials
The skill requests no environment variables, no credentials, and no special config paths beyond reading its own config.json and workflow.yaml. The use of an absolute user path for optional UniSkill is a local path access but does not request secrets.
Persistence & Privilege
Skill flags are default (not always:true). It does not attempt to modify other skills or system settings. The code may add a path to sys.path at runtime to load optional components, but it does not persistently change agent config or enable itself across agents.
What to consider before installing
Summary of what to consider before installing/running:
- Capability mismatch: The README/SKILL.md promises a 3-agent, fast workflow, but config.json sets production mode and the engine's logic will trigger Rule-Only fallback (pure rule math) — you will likely not get the advertised multi-agent behavior unless you change config or provide missing modules.
- Missing components: agent2_rag expects case_retriever and risk_control modules and agent3 tries to optionally load UniSkill from an absolute local path; none of those are included. If you enable them, inspect their code before use.
- Optional local path insertion: agent3_meta inserts '/home/admin/.openclaw/workspace/skills/uniskill-v4' into sys.path. If that path exists on your system it could cause the workflow to import and execute local code. Only enable/unpack third-party components you trust.
- Bugs and robustness: There are small code issues (e.g., agent3 references Path without importing it) and version mismatches (config.json v2.0.1 vs skill v2.0.2). Test in an isolated environment first.
Recommendations:
1. Run this in a sandbox or isolated environment (no sensitive data) to confirm actual behavior.
2. If you need the multi-agent pipeline, obtain and review the missing modules (case_retriever, risk_control, uniskill-v4) and verify their provenance and code before placing them on the filesystem where the skill can import them.
3. If you do not want the Rule-Only fallback, edit config.json (stability.mode) and understand the implications; changing it may cause the engine to attempt imports that are currently missing.
4. Contact the author/maintainer to clarify why production mode forces fallback and to request the missing components or an explanation of intended deployment.
Given these inconsistencies, exercise caution and verify the runtime behavior before trusting this skill for production quoting.Like a lobster shell, security has layers — review code before you run it.
latestvk97dakg7p4sgfz01yjvg4ny9k183zvg0
License
MIT-0
Free to use, modify, and redistribute. No attribution required.