llm-knowledge-bases 安全扫描报告 — 可信 | ClawSafe

0 /100

llm-knowledge-bases

Inspired by a public workflow shared by Andrej Karpathy (@karpathy). From raw research to a living Markdown knowledge base that compounds with every question.

LLM Knowledge Bases is a lightweight, documentation-only skill that defines workflows and rules; all actual Vault I/O is delegated to a separate plugin, with no declared or inferred sensitive capabilities beyond documentation metadata.

技能名称llm-knowledge-bases

分析耗时29.2s

引擎pi

✓

可以安装

Approve for use. No security concerns identified.

资源类型	声明权限	推断权限	状态	证据
文件系统	`NONE`	`NONE`	—	SKILL.md explicitly forbids direct file writes; all Vault I/O is mediated by plu…
网络访问	`NONE`	`NONE`	—	No network calls; only references https://x.com/karpathy in attribution text (RE…
命令执行	`NONE`	`NONE`	—	Shell scripts only scaffold directories (mkdir/printf) and invoke clawhub CLI wi…
环境变量	`NONE`	`NONE`	—	No environment variable access in any script or implementation
技能调用	`NONE`	`NONE`	—	Skill defines workflows but does not invoke other skills
剪贴板	`NONE`	`NONE`	—	No clipboard access found
浏览器	`NONE`	`NONE`	—	No browser access found
数据库	`NONE`	`NONE`	—	No database access found

1 项发现

🔗

中危外部 URL 外部 URL

https://x.com/karpathy

README.md:8

目录结构

10 文件 · 22.5 KB · 773 行

Markdown 6f · 690L Shell 2f · 62L JSON 1f · 17L YAML 1f · 4L

├─ 📝 CHANGELOG.md Markdown 47L · 2.3 KB

├─ 📋 clawhub.json JSON 17L · 439 B

├─ 🔧 init_llm_kb_repo.sh Shell 51L · 1.2 KB

├─ 📝 maintenance-playbook.md Markdown 91L · 2.6 KB

├─ 📋 openai.yaml YAML 4L · 272 B

├─ 🔧 publish.sh Shell 11L · 465 B

├─ 📝 README.md Markdown 158L · 4.7 KB

├─ 📝 RELEASE.md Markdown 74L · 2.7 KB

├─ 📝 repo-layout.md Markdown 110L · 2.5 KB

└─ 📝 SKILL.md Markdown 210L · 5.4 KB

安全亮点

✓ All capabilities are explicitly NONE; skill is a documentation-only specification

✓ SKILL.md clearly states: do not use generic file tools for Vault operations — only plugin tools

✓ Shell scripts use only safe primitives (mkdir, printf) with hardcoded paths and no pipe from user input

✓ No external dependencies (no requirements.txt, package.json, Cargo.toml, or Pipfile)

✓ Safety boundaries are well-defined: never modify raw/, never write wiki/ directly, never fabricate IDs

✓ Failure handling is explicit and prevents bypass: do not work around the error by writing directly to the Vault

✓ No base64, no eval, no curl|bash, no environment iteration, no credential access

✓ No hidden HTML comments, no steganography, no obfuscation

✓ No sensitive paths (~/.ssh, ~/.aws, .env) accessed anywhere