Obsidian Karpathy Wiki
v1.0.0Operate an Obsidian knowledge base as a persistent LLM wiki using a raw-to-source-to-wiki pattern. Use when Codex or another agent needs to ingest raw notes,...
⭐ 1· 30·0 current·0 all-time
bydpz_03@ducheneadas-source
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
Capability signals
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
OpenClaw
Benign
high confidencePurpose & Capability
Name and description describe operating an Obsidian vault; the skill is instruction-only and all required actions (ingest, summarize, promote, lint, heartbeat, write-back) are directly related to that purpose. No unrelated resources, credentials, or binaries are requested.
Instruction Scope
SKILL.md gives explicit, bounded instructions that operate on vault files (move loose notes, create/update source pages, update index/log, run periodic maintenance). These file reads/writes are expected for a vault-maintenance skill and there are no instructions to read unrelated system files, environment variables, or to transmit data to external endpoints.
Install Mechanism
No install spec and no code files — lowest-risk model. Nothing is downloaded or written to disk beyond the agent's normal file operations inside the vault as described.
Credentials
The skill declares no required environment variables, no primary credential, and no config paths. The requested scope (manipulating vault files) is proportionate to the described functionality.
Persistence & Privilege
always is false and disable-model-invocation is false (normal). The skill does not request persistent system-wide privileges or modify other skills' configurations. It describes recurring maintenance (heartbeat) but does not force-enable itself.
Assessment
This skill appears coherent and limited to operating inside an Obsidian vault. Before installing, consider: 1) Grant the agent access only to the specific vault directory (or a test copy) to avoid unintended exposure of unrelated files. 2) Review sample runs in read-only or dry-run mode first to confirm it moves/edits files as you expect. 3) Ensure the vault does not contain secrets or sensitive data you don't want an automated agent to modify. 4) If you are concerned about autonomous actions, keep disable-model-invocation enabled for this skill or require manual approval for maintenance runs. 5) When adapting the skill, follow the adaptation checklist in references and make explicit rules about what may be promoted into formal pages.Like a lobster shell, security has layers — review code before you run it.
latestvk97ebqgabf6qbnvraepj0b9swx84f99m
License
MIT-0
Free to use, modify, and redistribute. No attribution required.