Back to skill

Security audit

观远 BI · 马甲实战版

Security checks for vulnerabilities and agentic risk

Overview

ClawScan marked this skill suspicious because it reports an unpinned installer and a confirmed uninstall backup risk, while several other findings are disputed or based on incomplete analysis.

The verdict is suspicious, so treat installation as a review decision rather than a routine install. Consider whether you trust the publisher and can verify the installer source and version; remember that the scan was partial and cannot establish that uninspected content is safe.

Vulnerability Patterns
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
Vulnerability Patterns
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Tool MisuseTool Parameter Abuse, Chaining Abuse, Unsafe Defaults
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
Findings (146)

Credential Access

High
Category
Privilege Escalation
Confidence
70% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · CHANGELOG.md (reported line 314)May include surrounding context.

md
### Changed

- **官方全家桶 07-01 版本对齐**(`@guandata/guanskill@0.1.10`,2026-07-01 发布)。本 skill 路由总表、manifest/README/package/marketplace 里的官方版本 pin 全部刷新:
  - **`guancli` 1.0.36 → 1.0.38**:新增 **Personal Access Token (PAT) 登录方式**,支持在自动化、CI 或无浏览器环境中用 PAT 完成认证;`auth` 相关命令增强 PAT profile 的状态展示和修改保护(避免把 PAT 配置误当普通登录处理);API 调用按当前认证上下文选身份,提升 PAT 场景下 ChatBI/指标/资源接口稳定性。(1.0.37 与 1.0.38 同内容,官方连发两版。)
  - **`guanvis` 0.1.28 → 0.1.29**:**筛选器级联联动**(上游筛选约束下游筛选项);画布布局可放置筛选器;**自定义图表的数据视图可作点击联动来源、页面筛选器可过滤自定义图表**;表格卡片支持只配维度字段,`init` 支持多数据集页面数据集别名;比较卡支持本期/对比期输出,发布覆盖保护可识别并修复异常线上资源、必要时跳过覆盖备份。
  - **`guanetl` 0.1.17 → 0.1.18**:创建 ETL 时目录类型诊断更清晰,识别误用工作流/经典数据流目录并提示使用智能 ETL 目录;更新智能 ETL / 数据集输出目录 / 工作流目录边界说明。
  - **`guands` 0.1.17 → 0.1.18**:`dataset import` 支持按列指定字段类型;`dataset replace-data` 增加 `--encoding` 和 `--delimiter`;导入参数校验忽略未导入列的类型提示。

Tool Parameter Abuse

High
Category
Tool Misuse
Confidence
80% confidence
Finding

Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).

Content

Scanner excerpt · CHANGELOG.md (reported line 371)May include surrounding context.

md
### Fixed

- **🔴 删除顺序矛盾实测定案(P0 correctness)**:评审团发现 `SKILL.md` 对「ETL + 其输出数据集」的删除顺序自相矛盾——B-0.5 清理坑(line 219)与 Part D 删除段写「先删 ETL、反过来撞 6001」,而 B-7.1 / B-O step 10 / B-1 API 全图写「先删 ds、反过来撞 2002」。**2026-06-17 在 workshop513 真实实例做净零回归实测**(建两个一次性独立 DATAFLOW ETL、各测一个方向、测完全删):
  - `etl-first`(输出集还在就 `DELETE /api/etl`)→ **`2002 输出数据集已存在` 失败**;
  - `ds-first`(先 `DELETE /api/data-source/<输出dsId>`,ETL 还在)→ **`DataSource deleted` 成功、不报 6001**;再 `DELETE /api/etl` → 成功。
  - 裁决:**B-7.1 / line 233 / 255-256 正确(ds-first),line 219 与 Part D 删除段记反了**。已统一到 ds-first,并在 B-7.1 加实测复核锚点;澄清 `6001 依赖于该数据集` 只属删*输入*数据集或 churn `NOT_FOUND` 幽灵场景,不属正常输出集清理。删掉了草案误提的「按错误码自动判别顺序」兜底规则(红队证伪:套到 line 219 会反向推翻已实测的 ds-first)。
- **`guanetl delete` 命令引用清理**:README.md / README.en.md 路由表把 0.1.14 已移除的 `guanetl delete` 从命令串删除(本轮实跑 `guanetl --help` 确认 delete 不在命令列;README 自身 V3.0.5 changelog 已写「移除 delete」,路由表与之自相矛盾)。

Tool Parameter Abuse

High
Category
Tool Misuse
Confidence
80% confidence
Finding

Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).

Content

Scanner excerpt · CHANGELOG.md (reported line 371)May include surrounding context.

md
### Fixed

- **🔴 删除顺序矛盾实测定案(P0 correctness)**:评审团发现 `SKILL.md` 对「ETL + 其输出数据集」的删除顺序自相矛盾——B-0.5 清理坑(line 219)与 Part D 删除段写「先删 ETL、反过来撞 6001」,而 B-7.1 / B-〇 step 10 / B-1 API 全图写「先删 ds、反过来撞 2002」。**2026-06-17 在 workshop513 真实实例做净零回归实测**(建两个一次性独立 DATAFLOW ETL、各测一个方向、测完全删):
  - `etl-first`(输出集还在就 `DELETE /api/etl`)→ **`2002 输出数据集已存在` 失败**;
  - `ds-first`(先 `DELETE /api/data-source/<输出dsId>`,ETL 还在)→ **`DataSource deleted` 成功、不报 6001**;再 `DELETE /api/etl` → 成功。
  - 裁决:**B-7.1 / line 233 / 255-256 正确(ds-first),line 219 与 Part D 删除段记反了**。已统一到 ds-first,并在 B-7.1 加实测复核锚点;澄清 `6001 依赖于该数据集` 只属删*输入*数据集或 churn `NOT_FOUND` 幽灵场景,不属正常输出集清理。删掉了草案误提的「按错误码自动判别顺序」兜底规则(红队证伪:套到 line 219 会反向推翻已实测的 ds-first)。
- **`guanetl delete` 命令引用清理**:README.md / README.en.md 路由表把 0.1.14 已移除的 `guanetl delete` 从命令串删除(本轮实跑 `guanetl --help` 确认 delete 不在命令列;README 自身 V3.0.5 changelog 已写「移除 delete」,路由表与之自相矛盾)。

Tool Parameter Abuse

High
Category
Tool Misuse
Confidence
80% confidence
Finding

Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).

Content

Scanner excerpt · CHANGELOG.md (reported line 372)May include surrounding context.

md
- **🔴 删除顺序矛盾实测定案(P0 correctness)**:评审团发现 `SKILL.md` 对「ETL + 其输出数据集」的删除顺序自相矛盾——B-0.5 清理坑(line 219)与 Part D 删除段写「先删 ETL、反过来撞 6001」,而 B-7.1 / B-O step 10 / B-1 API 全图写「先删 ds、反过来撞 2002」。**2026-06-17 在 workshop513 真实实例做净零回归实测**(建两个一次性独立 DATAFLOW ETL、各测一个方向、测完全删):
  - `etl-first`(输出集还在就 `DELETE /api/etl`)→ **`2002 输出数据集已存在` 失败**;
  - `ds-first`(先 `DELETE /api/data-source/<输出dsId>`,ETL 还在)→ **`DataSource deleted` 成功、不报 6001**;再 `DELETE /api/etl` → 成功。
  - 裁决:**B-7.1 / line 233 / 255-256 正确(ds-first),line 219 与 Part D 删除段记反了**。已统一到 ds-first,并在 B-7.1 加实测复核锚点;澄清 `6001 依赖于该数据集` 只属删*输入*数据集或 churn `NOT_FOUND` 幽灵场景,不属正常输出集清理。删掉了草案误提的「按错误码自动判别顺序」兜底规则(红队证伪:套到 line 219 会反向推翻已实测的 ds-first)。
- **`guanetl delete` 命令引用清理**:README.md / README.en.md 路由表把 0.1.14 已移除的 `guanetl delete` 从命令串删除(本轮实跑 `guanetl --help` 确认 delete 不在命令列;README 自身 V3.0.5 changelog 已写「移除 delete」,路由表与之自相矛盾)。
- **References 目录行数回填**:`## 📚 References 目录` 表里 8 条偏差 >20% 的 `~N` 行数估值回填(part-c-html-dashboard ~390→~620、part-e ~620→~760、ai-nativ

Tool Parameter Abuse

High
Category
Tool Misuse
Confidence
80% confidence
Finding

Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).

Content

Scanner excerpt · CHANGELOG.md (reported line 372)May include surrounding context.

md
- **🔴 删除顺序矛盾实测定案(P0 correctness)**:评审团发现 `SKILL.md` 对「ETL + 其输出数据集」的删除顺序自相矛盾——B-0.5 清理坑(line 219)与 Part D 删除段写「先删 ETL、反过来撞 6001」,而 B-7.1 / B-〇 step 10 / B-1 API 全图写「先删 ds、反过来撞 2002」。**2026-06-17 在 workshop513 真实实例做净零回归实测**(建两个一次性独立 DATAFLOW ETL、各测一个方向、测完全删):
  - `etl-first`(输出集还在就 `DELETE /api/etl`)→ **`2002 输出数据集已存在` 失败**;
  - `ds-first`(先 `DELETE /api/data-source/<输出dsId>`,ETL 还在)→ **`DataSource deleted` 成功、不报 6001**;再 `DELETE /api/etl` → 成功。
  - 裁决:**B-7.1 / line 233 / 255-256 正确(ds-first),line 219 与 Part D 删除段记反了**。已统一到 ds-first,并在 B-7.1 加实测复核锚点;澄清 `6001 依赖于该数据集` 只属删*输入*数据集或 churn `NOT_FOUND` 幽灵场景,不属正常输出集清理。删掉了草案误提的「按错误码自动判别顺序」兜底规则(红队证伪:套到 line 219 会反向推翻已实测的 ds-first)。
- **`guanetl delete` 命令引用清理**:README.md / README.en.md 路由表把 0.1.14 已移除的 `guanetl delete` 从命令串删除(本轮实跑 `guanetl --help` 确认 delete 不在命令列;README 自身 V3.0.5 changelog 已写「移除 delete」,路由表与之自相矛盾)。
- **References 目录行数回填**:`## 📚 References 目录` 表里 8 条偏差 >20% 的 `~N` 行数估值回填(part-c-html-dashboard ~390→~620、part-e ~620→~760、ai-nativ

Tool Parameter Abuse

High
Category
Tool Misuse
Confidence
80% confidence
Finding

Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).

Content

Scanner excerpt · CHANGELOG.md (reported line 372)May include surrounding context.

md
- **🔴 删除顺序矛盾实测定案(P0 correctness)**:评审团发现 `SKILL.md` 对「ETL + 其输出数据集」的删除顺序自相矛盾——B-0.5 清理坑(line 219)与 Part D 删除段写「先删 ETL、反过来撞 6001」,而 B-7.1 / B-〇 step 10 / B-1 API 全图写「先删 ds、反过来撞 2002」。**2026-06-17 在 workshop513 真实实例做净零回归实测**(建两个一次性独立 DATAFLOW ETL、各测一个方向、测完全删):
  - `etl-first`(输出集还在就 `DELETE /api/etl`)→ **`2002 输出数据集已存在` 失败**;
  - `ds-first`(先 `DELETE /api/data-source/<输出dsId>`,ETL 还在)→ **`DataSource deleted` 成功、不报 6001**;再 `DELETE /api/etl` → 成功。
  - 裁决:**B-7.1 / line 233 / 255-256 正确(ds-first),line 219 与 Part D 删除段记反了**。已统一到 ds-first,并在 B-7.1 加实测复核锚点;澄清 `6001 依赖于该数据集` 只属删*输入*数据集或 churn `NOT_FOUND` 幽灵场景,不属正常输出集清理。删掉了草案误提的「按错误码自动判别顺序」兜底规则(红队证伪:套到 line 219 会反向推翻已实测的 ds-first)。
- **`guanetl delete` 命令引用清理**:README.md / README.en.md 路由表把 0.1.14 已移除的 `guanetl delete` 从命令串删除(本轮实跑 `guanetl --help` 确认 delete 不在命令列;README 自身 V3.0.5 changelog 已写「移除 delete」,路由表与之自相矛盾)。
- **References 目录行数回填**:`## 📚 References 目录` 表里 8 条偏差 >20% 的 `~N` 行数估值回填(part-c-html-dashboard ~390→~620、part-e ~620→~760、ai-nativ

Tool Parameter Abuse

High
Category
Tool Misuse
Confidence
80% confidence
Finding

Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).

Content

Scanner excerpt · CHANGELOG.md (reported line 380)May include surrounding context.

md
### Changed

- **`page?force=true` 级联删页纳入 B-7.0 删除安全闸(P0 safety)**:Part D 删除段把「`DELETE /api/page/<pgId>?force=true` 唯一可行」补成条件句——级联删整页内嵌卡片且不可逆,须用户逐项确认;**仅当本地保有该 page 的 guanvis 源(`page.js` / card 定义)可 republish 重建时确认即可、无需对账;BI UI 手搭、本地无源的发布页按不可逆 DELETE 走 B-7.0 完整对账**。B-13 红线(line 667)DELETE 括号补上 `/api/page/<id>?force=true`。
- **跨工具 / 橱窗元数据 drift 修正**:`AGENTS.md` 三处(frontmatter 示例 `metadata.version` 3.0.0→3.1.2、`~940 lines`→`~1060 lines`、家族列表给 `guanadmin`/`guanexport` 加「2026-06-04 退出、当前 5 件」括注,不删历史叙述);`.claude-plugin/marketplace.json` 橱窗描述去掉已退役 Part A、补 Part D/E/ADS,`version` 1.6.0→3.1.2。
- **`description` 瘦身**:删末尾「Claude Code/OpenClaw/Codex/Hermes 通用。」(已在 manifest.compatibility 四端声明),脱离 974/1024 上限区。红队判定「治理 vs 重搭」是 AI-native ADS 差异化指纹,保留不删。
- `config.example.json` 加 `_note` 说明它对 v3 已是死字段(认证走 `guancli auth login`),但**保留字段不删**——`bin/install.js` uninstall 逻辑用它比对用户是否改过 config.json、改过则删前自动备份。

Tool Parameter Abuse

High
Category
Tool Misuse
Confidence
80% confidence
Finding

Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).

Content

Scanner excerpt · CHANGELOG.md (reported line 478)May include surrounding context.

md
- **workshop513 实盘实测沉淀**(BI 8.2.1-hf6,全 7 个官方 skill 读写跑通)—— v3 路由全部验证正确;新增 2 条只有真跑才知道的硬边界:
  - **Part B**:`guanetl edit` 逆向在此实例 **5/5 全失败**(API direct-save / BI UI / guanetl 自己 create+save 出来的全中,生成空 `etl.go`、`-v` 无报错、紧接 `save` 有清空线上 ETL 风险)→ 改现有 ETL 继续走 Part B `guancli fetch`。最小复现已提交观远官方。
  - **Part D**:删 guanvis-published 页面唯一可行 `DELETE /api/page/<id>?force=true`(卡片内嵌 `page.cards`、`/api/card` 删报 1002、guanvis 拒覆盖空页);删 ETL `DELETE /api/etl/<id>` 连带删输出集(先 ETL 后 ds,别用 `guanetl delete --cascade`)。

### Notes

Tool Parameter Abuse

High
Category
Tool Misuse
Confidence
80% confidence
Finding

Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).

Content

Scanner excerpt · CHANGELOG.md (reported line 478)May include surrounding context.

md
- **workshop513 实盘实测沉淀**(BI 8.2.1-hf6,全 7 个官方 skill 读写跑通)—— v3 路由全部验证正确;新增 2 条只有真跑才知道的硬边界:
  - **Part B**:`guanetl edit` 逆向在此实例 **5/5 全失败**(API direct-save / BI UI / guanetl 自己 create+save 出来的全中,生成空 `etl.go`、`-v` 无报错、紧接 `save` 有清空线上 ETL 风险)→ 改现有 ETL 继续走 Part B `guancli fetch`。最小复现已提交观远官方。
  - **Part D**:删 guanvis-published 页面唯一可行 `DELETE /api/page/<id>?force=true`(卡片内嵌 `page.cards`、`/api/card` 删报 1002、guanvis 拒覆盖空页);删 ETL `DELETE /api/etl/<id>` 连带删输出集(先 ETL 后 ds,别用 `guanetl delete --cascade`)。

### Notes

Tool Parameter Abuse

High
Category
Tool Misuse
Confidence
80% confidence
Finding

Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).

Content

Scanner excerpt · CHANGELOG.md (reported line 478)May include surrounding context.

md
- **workshop513 实盘实测沉淀**(BI 8.2.1-hf6,全 7 个官方 skill 读写跑通)—— v3 路由全部验证正确;新增 2 条只有真跑才知道的硬边界:
  - **Part B**:`guanetl edit` 逆向在此实例 **5/5 全失败**(API direct-save / BI UI / guanetl 自己 create+save 出来的全中,生成空 `etl.go`、`-v` 无报错、紧接 `save` 有清空线上 ETL 风险)→ 改现有 ETL 继续走 Part B `guancli fetch`。最小复现已提交观远官方。
  - **Part D**:删 guanvis-published 页面唯一可行 `DELETE /api/page/<id>?force=true`(卡片内嵌 `page.cards`、`/api/card` 删报 1002、guanvis 拒覆盖空页);删 ETL `DELETE /api/etl/<id>` 连带删输出集(先 ETL 后 ds,别用 `guanetl delete --cascade`)。

### Notes

Tool Parameter Abuse

High
Category
Tool Misuse
Confidence
80% confidence
Finding

Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).

Content

Scanner excerpt · README.en.md (reported line 82)May include surrounding context.

md
- ✅ **Field usage dual-source audit** (page + ETL grep — looking only at dashboards **overestimates removable fields by 8×**)
- ✅ **POST /api/etl/direct-save** — full payload schema for create + update (same endpoint)
- ✅ **Real error retrieval** — `status:FINISHED` is just the trigger result; the real error lives in `GET /api/task/<id>.response.result.error`
- ✅ **Delete topology**: `DELETE /api/data-source/` MUST come before `DELETE /api/etl/`
- ✅ **v2→v3 batch refactoring SDK**: `transformV2ToV3()` 7-step rewrite + node ID remapping
- ✅ **CTO Zhang Jin's full-chain rewrite methodology**: 4 deliverables + 8 hard rules + 5-step workflow + three-layer verification + diff tracking 5-step + empty snapshot handling

Tool Parameter Abuse

High
Category
Tool Misuse
Confidence
80% confidence
Finding

Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).

Content

Scanner excerpt · README.md (reported line 79)May include surrounding context.

md
- ✅ **字段使用度双源审计**(page + etl 双源 grep,避免**仅看板会高估 8 倍可裁字段**)
- ✅ **POST /api/etl/direct-save** create + update 同接口的完整 payload schema
- ✅ **task error 真错误定位**(`status:FINISHED` 是任务触发结果,真错误在 `GET /api/task/<id>.response.result.error`)
- ✅ **删除拓扑**:`DELETE /api/data-source/` 必须先于 `DELETE /api/etl/`
- ✅ **v2→v3 批量改造 SDK**:`transformV2ToV3()` 7 步重写 + 节点 ID 重映射
- ✅ **CTO 张进的全链路重写方法论**:4 件交付 + 8 条硬规则 + 5 步标准工作流 + 三层验收 + 差异追踪 5 步法 + 空快照处理标准

Tool Parameter Abuse

High
Category
Tool Misuse
Confidence
80% confidence
Finding

Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).

Content

Scanner excerpt · README.en.md (reported line 82)May include surrounding context.

md
- ✅ **Field usage dual-source audit** (page + ETL grep — looking only at dashboards **overestimates removable fields by 8×**)
- ✅ **POST /api/etl/direct-save** — full payload schema for create + update (same endpoint)
- ✅ **Real error retrieval** — `status:FINISHED` is just the trigger result; the real error lives in `GET /api/task/<id>.response.result.error`
- ✅ **Delete topology**: `DELETE /api/data-source/` MUST come before `DELETE /api/etl/`
- ✅ **v2→v3 batch refactoring SDK**: `transformV2ToV3()` 7-step rewrite + node ID remapping
- ✅ **CTO Zhang Jin's full-chain rewrite methodology**: 4 deliverables + 8 hard rules + 5-step workflow + three-layer verification + diff tracking 5-step + empty snapshot handling

Tool Parameter Abuse

High
Category
Tool Misuse
Confidence
80% confidence
Finding

Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).

Content

Scanner excerpt · README.md (reported line 79)May include surrounding context.

md
- ✅ **字段使用度双源审计**(page + etl 双源 grep,避免**仅看板会高估 8 倍可裁字段**)
- ✅ **POST /api/etl/direct-save** create + update 同接口的完整 payload schema
- ✅ **task error 真错误定位**(`status:FINISHED` 是任务触发结果,真错误在 `GET /api/task/<id>.response.result.error`)
- ✅ **删除拓扑**:`DELETE /api/data-source/` 必须先于 `DELETE /api/etl/`
- ✅ **v2→v3 批量改造 SDK**:`transformV2ToV3()` 7 步重写 + 节点 ID 重映射
- ✅ **CTO 张进的全链路重写方法论**:4 件交付 + 8 条硬规则 + 5 步标准工作流 + 三层验收 + 差异追踪 5 步法 + 空快照处理标准

Description-Behavior Mismatch

High
Category
MCP Tool Poisoning
Confidence
92% confidence
Finding

The supplied chunk is an installer entry point, with no visible implementation of the declared Guandata workflows. Although installation can support a larger BI toolset, it is the sole operation shown here and is not disclosed in the description. The assessment is limited to the visible command and its comment; the implementation of guanskill was not supplied.

Content

No source excerpt is available for this finding.

Description-Behavior Mismatch

High
Category
MCP Tool Poisoning
Confidence
91% confidence
Finding

The supplied executable command performs skill-package synchronization rather than any declared Guandata BI operation. Its resources and immediate purpose concern agent skill installation or maintenance, a capability not disclosed in the description. Although synchronization can support software delivery, this chunk contains only that maintenance operation and does not establish it as an implementation step in a declared BI workflow. The external script's internal actions are not visible, so no additional capabilities are inferred.

Content

No source excerpt is available for this finding.

Incomplete referenced artifact analysis

High
Category
analysis-evasion
Confidence
100% confidence
Finding

Referenced artifact was not completely inspected

Content

Scanner excerpt · SKILL.md (reported line 42)May include surrounding context.

md
| 给已有看板接 AI / 固化指标口径 / 核对答案与页面筛选 / 检测公式或隐藏筛选变化 | [看板口径档案与只读验收](references/dashboard-evidence.md),用 `scripts/dashboard_evidence.py` 管理本地定义、原始取数与逐格断言 |

Incomplete referenced artifact analysis

High
Category
analysis-evasion
Confidence
100% confidence
Finding

Referenced artifact was not completely inspected

Content

Scanner excerpt · SKILL.md (reported line 106)May include surrounding context.

md
**看板口径档案与验收(V3.3.0)**:给已有看板接 AI 或核对答案时,读 [dashboard-evidence.md](references/dashboard-evidence.md)。先明确 profile、页面和所选卡片;脚本保留公式、别名、时间宏和联动定义,继承页面默认筛选取原始值,再按具体数据行及字

Incomplete referenced artifact analysis

High
Category
analysis-evasion
Confidence
100% confidence
Finding

Referenced artifact was not completely inspected

Content

Scanner excerpt · SKILL.md (reported line 265)May include surrounding context.

md
| [dashboard-evidence.md](references/dashboard-evidence.md) | 看板接 AI、口径档案、原始值及页面筛选对账、逐格断言与定义变化复查;脚本 `dashboard_evidence.py` | ~100 |

Incomplete referenced artifact analysis

High
Category
analysis-evasion
Confidence
100% confidence
Finding

Referenced artifact was not completely inspected

Content

Scanner excerpt · SKILL.md (reported line 43)May include surrounding context.

md
| 扫整库 ETL 治理 / 新建/修改/删除 ETL / 字段使用度审计 / 修复 ETL 报错 | [Part B:ETL 治理](references/part-b-governance.md) |

Incomplete referenced artifact analysis

High
Category
analysis-evasion
Confidence
100% confidence
Finding

Referenced artifact was not completely inspected

Content

Scanner excerpt · SKILL.md (reported line 54)May include surrounding context.

md
| 不知道用哪个 | 读 [ETL 治理流程](references/part-b-governance.md),再选择具体 reference |

Incomplete referenced artifact analysis

High
Category
analysis-evasion
Confidence
100% confidence
Finding

Referenced artifact was not completely inspected

Content

Scanner excerpt · SKILL.md (reported line 218)May include surrounding context.

md
整库治理、循环依赖、字段使用度或官方路径以外的引擎问题,读 [治理与写入手册](references/part-b-governance.md)。普通修改使用官方 guanetl。

Incomplete referenced artifact analysis

High
Category
analysis-evasion
Confidence
100% confidence
Finding

Referenced artifact was not completely inspected

Content

Scanner excerpt · SKILL.md (reported line 260)May include surrounding context.

md
| [part-b-governance.md](references/part-b-governance.md) | 原 Part B 治理与写入细节、历史修复与删除边界 | 完整下沉 |

Incomplete referenced artifact analysis

High
Category
analysis-evasion
Confidence
100% confidence
Finding

Referenced artifact was not completely inspected

Content

Scanner excerpt · SKILL.md (reported line 51)May include surrounding context.

md
t E:SuperApp 开放应用开发流水线**(V2.1.12 新增,拆到 [references/part-e-superapp-pipeline.md](references/part-e-superapp-pipeline.md)) |

Incomplete referenced artifact analysis

High
Category
analysis-evasion
Confidence
100% confidence
Finding

Referenced artifact was not completely inspected

Content

Scanner excerpt · SKILL.md (reported line 275)May include surrounding context.

md
| [part-e-superapp-pipeline.md](references/part-e-superapp-pipeline.md) | SuperApp 开放应用开发流水线 / `guancli app create/publish` 不读 `.env` 必须显式传 `--app-id` / 脚手架 bi-