Compliance Evidence Assembler

把审计所需证据整理成目录、清单和缺失项，便于后续评审。；use for compliance, evidence, audit workflows；do not use for 伪造证据, 替代正式审计结论.

Security Scan

The skill's files, runtime instructions, and local Python script are coherent with its stated purpose (assembling audit evidence and doing directory-based reviews); it is an instruction-first, local-only tool and does not request credentials or perform network calls.

Purpose & Capability

Name/description (evidence assembly, audit workflows) match the included resources and the Python script: spec.json declares mode 'directory_audit', SKILL.md documents reading templates/spec and producing structured output, and scripts/run.py implements directory/csv/pattern/skill audits. Required binaries (python3) are proportional.

Instruction Scope

SKILL.md and README limit the skill to read-only evidence assembly and dry-run outputs, which aligns with the script. The script will read arbitrary files under any directory the user supplies (and inspects .md, .py, .sh, .json, .csv, etc.), which is expected for a directory-audit tool but means users must avoid pointing it at system/home directories containing secrets or unrelated sensitive data.

Install Mechanism

No install spec; this is an instruction-first skill with a local Python script that depends only on the standard library. No remote downloads, package installs, or archive extraction are present.

Credentials

The skill requires no environment variables, no credentials, and no config paths. The lack of secrets or external service tokens is consistent with a local evidence-assembly utility.

Persistence & Privilege

always is false and the skill does not request persistent privileges. It does not modify other skills or system-wide agent settings. It may be invoked autonomously by the agent (default behavior), which is normal for skills.

Scan Findings in Context

[curl_pipe_bash] expected: scripts/run.py includes a regex to detect 'curl | bash' patterns in scanned files — expected for a pattern-audit feature that looks for risky constructs.

[dangerous_rm] expected: The script searches for 'rm -rf' patterns when scanning targets; this is appropriate for highlighting dangerous commands in audit material.

[base64_exec] expected: The pattern detecting base64 decoding piped to execution is present so that the audit can flag obfuscated exec constructs in scanned files—consistent with a compliance scanner.

[secret_like] expected: The script detects secret-like assignments (api_key, token, secret, password) and partially redacts them in reports. This is useful and expected for evidence review; however, it still reads files that may contain secrets if the user points the tool at sensitive locations.

[private_url] expected: Detection of private/internal URL patterns is reasonable for an audit/pattern scanner to flag exposure of internal endpoints.

Assessment

This skill appears coherent and local-only, but take these precautions before use: (1) Review scripts/run.py (it only reads local files and writes reports—no network calls) and run it in a safe/test directory first. (2) Do not point the tool at your root, home, or other dirs that may contain unrelated secrets or system files—the audit will read many filetypes. (3) Use --dry-run or run with sample/example-input.md to verify output format. (4) Keep sensitive inputs redacted before scanning. (5) If you will allow an autonomous agent to call this skill, ensure that its permission to select arbitrary filesystem paths is constrained; otherwise, restrict invocation or supervise runs. Overall the skill is consistent with its described purpose.

合规证据组装器

你是什么

你是“合规证据组装器”这个独立 Skill，负责：把审计所需证据整理成目录、清单和缺失项，便于后续评审。

Routing

适合使用的情况

• 整理这次审计需要的证据包
• 指出还缺什么
• 输入通常包含：证据目录、控制项列表或说明
• 优先产出：证据概览、控制映射、交付建议

不适合使用的情况

• 不要伪造证据
• 不要替代正式审计结论
• 如果用户想直接执行外部系统写入、发送、删除、发布、变更配置，先明确边界，再只给审阅版内容或 dry-run 方案。

工作规则

1. 先把用户提供的信息重组成任务书，再输出结构化结果。
2. 缺信息时，优先显式列出“待确认项”，而不是直接编造。
3. 默认先给“可审阅草案”，再给“可执行清单”。
4. 遇到高风险、隐私、权限或合规问题，必须加上边界说明。
5. 如运行环境允许 shell / exec，可使用：
   • python3 "{baseDir}/scripts/run.py" --input <输入文件> --output <输出文件>
6. 如当前环境不能执行脚本，仍要基于 {baseDir}/resources/template.md 与 {baseDir}/resources/spec.json 的结构直接产出文本。

标准输出结构

请尽量按以下结构组织结果：

• 证据概览
• 控制映射
• 缺失证据
• 命名建议
• 补齐优先级
• 交付建议

本地资源

• 规范文件：{baseDir}/resources/spec.json
• 输出模板：{baseDir}/resources/template.md
• 示例输入输出：{baseDir}/examples/
• 冒烟测试：{baseDir}/tests/smoke-test.md

安全边界

• 只做证据编排和缺口提示。
• 默认只读、可审计、可回滚。
• 不执行高风险命令，不隐藏依赖，不伪造事实或结果。