attack-path-analysis
Use when Codex is already in the attack-path-analysis phase of a security scan or the user explicitly asks to trace a security finding from source to sink and…
Build and maintain a workspace-local, Obsidian-friendly research vault using Karpathy's LLM Wiki pattern.
$ npx -y skills add CoWork-OS/CoWork-OS --skill llm-wiki --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/llm-wikiContext preview
The summary Claude sees to decide when to auto-load this skill.
Build and maintain a workspace-local, Obsidian-friendly research vault using Karpathy's LLM Wiki pattern.
name: llm-wiki description: "Build and maintain a workspace-local, Obsidian-friendly research vault using Karpathy's LLM Wiki pattern." version: "1.1.0" metadata: author: CoWork OS Contributors <info@coworkosapp.com>
Create and maintain a persistent markdown research vault with immutable raw sources, linked concept/entity pages, maps of content, and a maintenance log.
| Name | Type | Required | Description | |---|---|---|---| | objective | string | No | Topic, question, or research objective. If omitted, ask one short scoping question before durable ingest work. | | mode | string | No | `auto`, `init`, `ingest`, `query`, `lint`, or `refresh` | | path | string | No | Workspace-relative or absolute vault path | | obsidian | string | No | `auto`, `on`, or `off` |
Local-first personal agentic OS and everything app for coding, knowledge work, web design, automations, and artifacts.
Repo: CoWork-OS/CoWork-OS
Use when Codex is already in the attack-path-analysis phase of a security scan or the user explicitly asks to trace a security finding from source to sink and…
Use when the user asks for a deep, exhaustive, multi-pass, or variance-reducing repository-wide Codex Security scan. Run repeated independent repository-wide…
Use when Codex is already in the finding-discovery phase of a security scan or the user explicitly asks to discover candidate security findings in a repository…
Use when the user explicitly asks to fix and verify a validated or plausible security finding. Do not use as the primary trigger for full PR, commit, branch,…
Use when the user asks for a security review of a pull request, commit, branch diff, working-tree patch, or other Git-backed change set.
Use when the user asks for a repository-wide or scoped-path security scan.