universal-service-access
纯文档型凭证管理指导,无可执行代码,文档包含较完整安全规则但缺乏实现细节和验证机制。
Why this conclusion was reached
0/4 dimensions flaggedDeclared resources and inferred behavior are broadly aligned.
No obvious high-risk egress or execution signals were found.
There is no explicit malicious chain in the report.
Dependency information is incomplete, so supply-chain confidence stays limited.
What drove the risk score up
无 scripts/ 或可执行文件,风险大幅降低
SKILL.md 未声明所需的 allowed-tools,权限边界不明确
声称是'安全凭证管理器'但无技术实现,可能诱导用户泄露凭证
'STORE SECURELY' 等指令无实现代码,无法验证是否执行
大量 'NEVER' 规则易被 prompt injection 覆盖
Most important evidence
声称安全但无技术验证
文档声称是'安全凭证管理器',包含 Never Echo Secret、Secure Storage 等规则,但无实现代码验证规则是否被执行。纯文档型 skill 可能被用户过度信任。
SKILL.md:48 缺少 allowed-tools 声明
SKILL.md 未声明 AI agent 执行时需要的 allowed-tools。凭证管理暗示需要 filesystem 和 network 权限,但边界不明确。
SKILL.md:1 规则易被覆盖风险
大量 'NEVER DISPLAY SECRET'、'NEVER COMMIT SECRET TO GIT' 等绝对性规则以纯文本呈现,无技术防护,可能被恶意上下文覆盖。
SKILL.md:63 Declared capability vs actual capability
SKILL.md:38 提到 'periksa SECRET STORE / ENVIRONMENT' 暗示需读环境变量,但无明确声明 SKILL.md:48 'Universal Workflow: DISCOVER → AUTHENTICATE → AUTHORIZE → CONNECT → EXECUTE' 暗示需网络写权限 SKILL.md:11 明确声明 'Kelola kredensial',但无实现代码验证 Suspicious artifacts and egress
No obvious IOC was extracted.
Dependencies and supply chain
There are no structured dependency warnings.
File composition
SKILL.md