LLM Wiki Knowledge Graph
Egonex-AI/Understand-Anything
Detects a Karpathy-pattern LLM wiki and builds an interactive knowledge graph with entities, implicit relationships and topic clusters.
This skill should be used when users ask about their work context, what they're working on, recent activity, file relationships, or knowledge graph structure.
$ npx skills add jacob-dietle/context-os --skill context-os-cli -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jacob-dietle/context-os context-os-cli --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/jacob-dietle/context-os.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/context-os-cli .claude/skills/context-os-cli && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "context-os-cli" agent skill from https://github.com/jacob-dietle/context-os/tree/main/.claude/skills/context-os-cli into .claude/skills/context-os-cli/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "context-os-cli", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/jacob-dietle/context-os/tree/main/.claude/skills/context-os-cliType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add jacob-dietle/context-os --skill context-os-cli -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jacob-dietle/context-os context-os-cli --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jacob-dietle/context-os.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/context-os-cli .agents/skills/context-os-cli && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "context-os-cli" agent skill from https://github.com/jacob-dietle/context-os/tree/main/.claude/skills/context-os-cli into .agents/skills/context-os-cli/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "context-os-cli", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jacob-dietle/context-os --skill context-os-cli -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jacob-dietle/context-os context-os-cli --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jacob-dietle/context-os.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/context-os-cli .cursor/skills/context-os-cli && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "context-os-cli" agent skill from https://github.com/jacob-dietle/context-os/tree/main/.claude/skills/context-os-cli into .cursor/skills/context-os-cli/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "context-os-cli", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/jacob-dietle/context-os.git --path .claude/skills/context-os-cli--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add jacob-dietle/context-os --skill context-os-cli -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jacob-dietle/context-os context-os-cli --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jacob-dietle/context-os.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/context-os-cli .gemini/skills/context-os-cli && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "context-os-cli" agent skill from https://github.com/jacob-dietle/context-os/tree/main/.claude/skills/context-os-cli into .gemini/skills/context-os-cli/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "context-os-cli", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install jacob-dietle/context-os context-os-cliInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add jacob-dietle/context-os --skill context-os-cli -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jacob-dietle/context-os.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/context-os-cli .github/skills/context-os-cli && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "context-os-cli" agent skill from https://github.com/jacob-dietle/context-os/tree/main/.claude/skills/context-os-cli into .github/skills/context-os-cli/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "context-os-cli", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jacob-dietle/context-os --skill context-os-cli -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jacob-dietle/context-os context-os-cli --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jacob-dietle/context-os.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/context-os-cli .opencode/skills/context-os-cli && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "context-os-cli" agent skill from https://github.com/jacob-dietle/context-os/tree/main/.claude/skills/context-os-cli into .opencode/skills/context-os-cli/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "context-os-cli", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
context-os-cliThis skill should be used when users ask about their work context, what they're working on, recent activity, file relationships, or knowledge graph structure.
Context Os CLI is an agent skill from jacob-dietle/context-os. This skill should be used when users ask about their work context, what they're working on, recent activity, file relationships, or knowledge graph structure. Uses context-os CLI (including graph health/search/stats commands) combined with grep/glob for context restoration. Every claim MUST cite a receipt ID for user verification.
Its SKILL.md is about 4.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `references/heat-metrics-model.md`, `references/query-patterns.md` and `references/search-strategies.md`).
It sits in Knowledge Management, covering Knowledge graphs. The licence is MIT.
Read from SKILL.md and the folder at commit 1027e3f. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
gitFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context Os CLI loads about 4.1k tokens when it runs, and up to ~7.5k if it reads all its reference files. Until then it costs about 87 tokens; SKILL.md has 915 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from jacob-dietle/context-os at commit 1027e3f, republished under its MIT licence (© jacob-dietle). 915 words, ~4,099 tokens.
.claude/skills/context-os-cli/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.Use context-os CLI + grep + glob together for context restoration.
Core insight: The CLI finds WHICH files matter. Grep/Read find WHAT's in them.
# 1. Full context for a topic (start here — one command does it all)
context-os context "pixee" --format json
# 2. If you need to drill deeper, use targeted queries
context-os query flex --files "*pixee*" --agg count,recency --format json
# 3. Read hot files to understand what they are
Read: <top_file_from_step_1>
# 4. Search content IN those files
Grep: pattern="hubspot|integration" path=<directory_from_step_1>
# 5. Check git for recent changes
git log --oneline -10 -- <hot_files>Start with context for broad questions, drop to query subcommands for targeted drilldowns.
| Command | Purpose |
|---|---|
context <query> | Start here. Composed query across flex, heat, chains, sessions, timeline, co-access |
query <subcommand> | Targeted queries (flex, heat, chains, etc.) |
intel health | Check intel service health |
intel name-chain <id> | Name a chain using AI |
daemon status | Show daemon sync state + registration |
daemon once | Run a single sync cycle |
| Command | Purpose |
|---|---|
query flex --files "*pattern*" | Find files by path pattern |
query flex --time 7d | Find files touched in time window |
query heat --time 30d | File heat metrics (specificity, velocity, score, level) |
query co-access <file> | Find files accessed together |
query session <id> | All files in a session |
query sessions --time 7d | Session-grouped data |
query chains | List conversation chains |
query timeline --time 7d | Timeline data for visualization |
query verify <receipt> | Verify a previous query result |
query receipts | List recent query receipts |
Always use --format json — table output truncates long paths.
context CommandThe highest-level query. One command gives you executive summary, heat, work clusters, insights, continuity, timeline, and suggested reads.
context-os context "tastematter" --format json
context-os context "pixee" --time 14d --format jsonResponse includes:
executive_summary — status, work_tempo, hot_file_count, focus_ratiocurrent_state — key_metrics, evidence (file excerpts)continuity — left_off_at, pending_items, chain_contextwork_clusters — co-accessed file groups with PMI scoressuggested_reads — prioritized files (with surprise flag for unexpected)timeline — weekly focus areas with top files and access countsinsights — abandoned file detection, anomaliesverification — receipt_id, files/sessions/pairs analyzedquick_start — commands and directory structures from matching filesWhen to use context vs query:
| Need | Use |
|---|---|
| "What's happening with project X?" | context "X" |
| "What files are hot right now?" | query heat |
| "Find files matching a pattern" | query flex --files |
| "What did I work on this week?" | query flex --time 7d |
| "Show me session history" | query sessions |
| "What files go with this one?" | query co-access <file> |
query heat CommandShows file heat metrics with percentile-based classification.
context-os query heat --time 30d --format json
context-os query heat --files "*tastematter*" --sort specificity --format csvOptions:
-t, --time <TIME> Long window: 30d (default), 14d, 60d, 90d
-f, --files <FILES> File path pattern filter (glob-style)
-l, --limit <LIMIT> Max results (default: 50)
-s, --sort <SORT> Sort by: heat (default), specificity, velocity, name
--format <FORMAT> Output: table (default), json, compact, csvHeat levels use percentile classification:
Key fields: specificity (IDF-like), velocity, heat_score, heat_level
See references/heat-metrics-model.md for formula details and interpretation tables.
graph-exec CommandExecutes JavaScript against an in-memory knowledge graph (markdown files with frontmatter + wiki-links). Uses Boa JS engine — pure Rust, no Node/bun.
context-os graph-exec --graph <path-to-markdown-dir> '<javascript-code>'codemode Object (4 functions, all synchronous)codemode.graph_search({ pattern, scope?, maxResults? })
pattern: string — regex to match
scope: 'content' | 'frontmatter' | 'both' (default: 'both')
maxResults: number (default: 20)
Returns: [{ path, matches: [{ line, content }], score, frontmatter }]
codemode.graph_traverse({ start, direction?, maxDepth?, filter? })
start: string — node name (filename without .md, e.g. "context-engineering")
direction: 'outbound' | 'inbound' | 'both' (default: 'outbound')
maxDepth: number (default: 2)
filter: { status?, domain?, tags? }
Returns: { nodes: [{ path, name, depth, frontmatter }], edges: [{ from, to }] }
codemode.graph_read({ path, section?, maxLines? })
path: string — relative path (e.g. "technical/context-engineering.md")
section: string — extract named heading section only
Returns: { path, content, frontmatter, outbound_links, inbound_links }
codemode.graph_query({ filter, sort?, limit? })
filter: { status?, domain?, tags?, name?, validated_by? }
sort: 'name' | 'last_updated' | 'status'
limit: number (default: 50)
Returns: { nodes: [{ path, name, status, domain, tags, last_updated, link_count }], total }Functions are synchronous (not async). Wrap code in an IIFE:
# CORRECT — IIFE returns a value
context-os graph-exec --graph 04_knowledge_base '(() => {
const r = codemode.graph_query({ filter: { status: "canonical" } });
return JSON.stringify({ total: r.total, names: r.nodes.map(n => n.name) });
})()'
# WRONG — bare return is a syntax error
context-os graph-exec --graph 04_knowledge_base 'return codemode.graph_search({})'
# WRONG — async not needed (and Boa doesn't support top-level await)
context-os graph-exec --graph 04_knowledge_base 'async () => { ... }'Keep JS simple when passing inline. Avoid backslashes and nested quotes. If complex, use a heredoc:
context-os graph-exec --graph 04_knowledge_base "$(cat <<'JSEOF'
(() => {
const hubs = codemode.graph_query({ filter: {} });
const sorted = hubs.nodes
.sort((a, b) => (b.link_count.outbound + b.link_count.inbound) - (a.link_count.outbound + a.link_count.inbound))
.slice(0, 10);
return JSON.stringify(sorted.map(n => ({
name: n.name,
links: n.link_count.outbound + n.link_count.inbound
})));
})()
JSEOF
)"# Top hubs by link count
context-os graph-exec --graph 04_knowledge_base '(() => {
const r = codemode.graph_query({ filter: {} });
return JSON.stringify(r.nodes.sort((a,b) => (b.link_count.outbound+b.link_count.inbound)-(a.link_count.outbound+a.link_count.inbound)).slice(0,5).map(n => ({ name: n.name, out: n.link_count.outbound, in: n.link_count.inbound })));
})()'
# All canonical nodes
context-os graph-exec --graph 04_knowledge_base '(() => {
const r = codemode.graph_query({ filter: { status: "canonical" } });
return JSON.stringify({ total: r.total, nodes: r.nodes.map(n => n.name) });
})()'
# Traverse outbound from a node
context-os graph-exec --graph 04_knowledge_base '(() => {
const r = codemode.graph_traverse({ start: "context-engineering", direction: "both", maxDepth: 1 });
return JSON.stringify(r.nodes.map(n => ({ name: n.name, depth: n.depth })));
})()'
# Find orphan nodes (no links)
context-os graph-exec --graph 04_knowledge_base '(() => {
const r = codemode.graph_query({ filter: {} });
const orphans = r.nodes.filter(n => n.link_count.outbound === 0 && n.link_count.inbound === 0);
return JSON.stringify({ count: orphans.length, nodes: orphans.map(n => n.name) });
})()'
# Search then read (composition)
context-os graph-exec --graph 04_knowledge_base '(() => {
const results = codemode.graph_search({ pattern: "taste" });
const top = results[0];
const detail = codemode.graph_read({ path: top.path });
return JSON.stringify({ path: detail.path, outbound: detail.outbound_links, inbound: detail.inbound_links });
})()'If running inside Claude Code with the codemode-graph MCP server enabled, prefer the MCP tool over the CLI. The MCP tool description is embedded and the LLM gets the API right on the first call. Functions are async in MCP mode:
// MCP mode (async, tool description auto-loaded)
async () => {
const results = await codemode.graph_search({ pattern: 'context' });
return results[0];
}| Need | Use |
|---|---|
| Structural queries (hubs, clusters, orphans, traversal) | graph-exec or MCP |
| Simple file search by name | Glob |
| Content search | Grep |
| File activity/heat over time | context-os query heat |
| Co-access patterns | context-os query co-access |
| Full project context | context-os context |
# DON'T - CLI searches file PATHS, not content
context-os query flex --files "*notification design*" # Won't find anything# DO - Find files first, then search content
context-os query flex --files "*alert*" --format json # Find alert-related files
Grep: pattern="notification|digest|slack" path=<results> # Search content# DON'T - You'll miss semantic understanding
context-os query flex --files "*hubspot*" # Returns files but not WHAT they do# DO - CLI narrows, Read/Grep understands
context-os query flex --files "*hubspot*" --format json
Read: <top_result> # Understand what the file actually doescontext and go straight to query# DON'T - You'll miss insights, clusters, and continuity
context-os query flex --files "*pixee*" --format json# DO - Get the full picture first
context-os context "pixee" --format json
# THEN drill into specific areas if needed
context-os query heat --files "*pixee*" --format json| Need | Tool |
|---|---|
| Broad project context | context-os context "<topic>" |
| Find files by path pattern | context-os query flex --files |
| File heat/activity metrics | context-os query heat |
| Find files by content | Grep |
| Read file contents | Read |
| Find files by name glob | Glob |
| Check recent changes | git log |
Workflow pattern:
context → full picture (summary, heat, clusters, insights)
↓
query heat/flex → drill into specific files or patterns
↓
Read → understand what files contain
↓
Grep → find specific concepts in content
↓
git log → understand evolutionCanonical: ~/.context-os/context_os_events.db
If queries return empty results:
# Check database exists
ls ~/.context-os/context_os_events.db
# Check daemon status
context-os daemon status
# Run a single sync
context-os daemon once
# Rebuild indexes if needed
context-os build-chains
context-os index-filesEvery claim from query results MUST include receipt ID:
Found 147 Pixee files [q_7f3a2b]
To verify: context-os query verify q_7f3a2b| Helps | Doesn't Help |
|---|---|
| "What files did I touch for project X?" | "What was I thinking about?" |
| "When was this file last accessed?" | "Why did I make this change?" |
| "What files are related to this one?" | "What's the best architecture for X?" |
| "What's the status of this work?" | "How should I fix this bug?" |
| "What files are hot/cold right now?" | "What's in my calendar?" |
For semantic understanding, READ the files. The CLI tells you which ones matter.
For advanced patterns:
references/heat-metrics-model.md - Heat formula: specificity, exponential decay, percentile classificationreferences/search-strategies.md - 9 multi-step search strategies (Pilot Drilling, Triangulation, etc.)references/query-patterns.md - Path substring patterns and result interpretationcontext-os context <QUERY> [OPTIONS]
ARGUMENTS:
<QUERY> Search query (used as glob pattern *query*)
OPTIONS:
-t, --time <TIME> Time window (default: 30d)
-l, --limit <LIMIT> Max results per sub-query (default: 20)
--format <FORMAT> Output: json (default), compact, tablecontext-os query flex [OPTIONS]
OPTIONS:
-f, --files <FILES> File pattern (glob): "*pixee*", "*.py"
-t, --time <TIME> Time window: 7d (default), 14d, 30d
-c, --chain <CHAIN> Filter by chain ID
-s, --session <SESSION> Filter by session ID
-a, --agg <AGG> Aggregations: count, recency
-l, --limit <LIMIT> Max results (default: 20)
--sort <SORT> Order: count (default), recency
--format <FORMAT> Output: json (default), compactcontext-os query heat [OPTIONS]
OPTIONS:
-t, --time <TIME> Window: 30d (default), 14d, 60d, 90d
-f, --files <FILES> File pattern filter (glob-style)
-l, --limit <LIMIT> Max results (default: 50)
-s, --sort <SORT> Sort: heat (default), specificity, velocity, name
--format <FORMAT> Output: table (default), json, compact, csvcontext-os query timeline [OPTIONS]
OPTIONS:
-t, --time <TIME> Time range: 7d (default), 14d, 30d
-p, --files <FILES> File pattern filter
-c, --chain <CHAIN> Filter by chain ID
-l, --limit <LIMIT> Max files (default: 30)
--format <FORMAT> Output: json (default), compactcontext-os query sessions [OPTIONS]
OPTIONS:
-t, --time <TIME> Time range: 7d (default), 14d, 30d
-c, --chain <CHAIN> Filter by chain ID
-l, --limit <LIMIT> Max sessions (default: 50)
--format <FORMAT> Output: json (default), compact| Command | Purpose |
|---|---|
query search <term> | Keyword search in file paths |
query file <path> | History for specific file |
query co-access <path> | Files accessed with target |
query chains | List conversation chains |
query verify <receipt> | Verify a receipt |
query receipts | List recent receipts |
All support --format json.
| Command | Purpose |
|---|---|
sync-git | Sync git commits from repository |
parse-sessions | Parse JSONL session files |
build-chains | Build chain graph from sessions |
index-files | Build inverted file index |
watch | Watch directory for file changes |
daemon once | Run single sync cycle |
daemon start | Start daemon (foreground) |
daemon status | Show sync state + registration |
daemon install | Install daemon to run on login |
daemon uninstall | Remove daemon from login |
intel health | Check intel service health |
intel name-chain <id> | Name a chain using AI |
serve | Start HTTP API server |
Last Updated: 2026-04-07
Version: 6.0 (Renamed from context-query to context-os-cli. All local CLI commands now reference context-os binary. Publishing commands remain tastematter. Added graph health/search/stats from Spec 32.)
© jacob-dietle, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 3 other files (references) in .claude/skills/context-os-cli of jacob-dietle/context-os.
Open the folder on GitHubat commit 1027e3f
Context Os CLI next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Context Os CLI this skilljacob-dietle/context-os | 111 | — | ~4.1k | Automated safety check: Pass | MIT | |
| LLM Wiki Knowledge GraphEgonex-AI/Understand-Anything | 86k | 1 repos | ~1.5k | Automated safety check: Pass | MIT | |
| Ontology1mancompany/OneManCompany | 440 | 2 repos | ~1.5k | Automated safety check: Pass | Apache-2.0 | |
| Graphagenticnotetaking/arscontexta | 3.5k | 1 repos | ~4.9k | Automated safety check: Notes | MIT | |
| Obsidian Canvas BoardsAgriciDaniel/claude-obsidian | 15k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Knowledge Graphgnomeria/usbtree | 690 | — | ~1.5k | Automated safety check: Pass | MIT |
Egonex-AI/Understand-Anything
Detects a Karpathy-pattern LLM wiki and builds an interactive knowledge graph with entities, implicit relationships and topic clusters.
1mancompany/OneManCompany
Typed knowledge graph for structured agent memory and composable skills.
agenticnotetaking/arscontexta
Interactive knowledge graph analysis. An agent skill from agenticnotetaking/arscontexta.
AgriciDaniel/claude-obsidian
Creates, inspects and updates Obsidian JSON Canvas boards in a vault, with text, file, link, group and edge nodes, using safe recoverable edits.
gnomeria/usbtree
Set up and maintain a lightweight, file-based knowledge graph of the repo — entities, typed relations, decisions, gotchas — so agents load context fast instead of re-exploring the codebase every…
agenticnotetaking/arscontexta
Show vault statistics and knowledge graph metrics. An agent skill from agenticnotetaking/arscontexta.
jacob-dietle/context-os
A skill your agent uses when deciding what to work on next, when progress is stuck, or when the reflex is to build or automate before proving the current bottleneck.
jacob-dietle/context-os
This skill should be used to periodically defragment a multi-app/multi-service codebase — both CODE (duplicate deploy targets, colliding bindings, stale forks) and CONTEXT (parallel spec…
jacob-dietle/context-os
This skill should be used when producing content (newsletter posts, blog posts, LinkedIn posts) from existing corpus material.
jacob-dietle/context-os
This skill should be used when making architectural decisions, writing specs, or reviewing decisions that contain "future work", "v2", "simpler for now", "out of scope", or complexity claims.
jacob-dietle/context-os
This skill should be used when decomposing a spec into a multi-agent implementation plan with dependency ordering, parallelism decisions, contract testing, and verification strategy.
jacob-dietle/context-os
This skill should be used when a specific quality problem (UX, data, architecture, feature) needs systematic diagnosis and iterative fixing toward a defined target.
Categories
This skill should be used when users ask about their work context, what they're working on, recent activity, file relationships, or knowledge graph structure. Context Os CLI is an agent skill from jacob-dietle/context-os. This skill should be used when users ask about their work context, what they're working on, recent activity, file relationships, or knowledge graph structure.
Context Os CLI fits situations like: tasks that involve Knowledge graphs.
Run `npx skills add jacob-dietle/context-os --skill context-os-cli -a claude-code`. Or copy the skill folder (.claude/skills/context-os-cli in jacob-dietle/context-os) into .claude/skills/context-os-cli in your project. Claude Code loads it when a task matches its description.
Run `npx skills add jacob-dietle/context-os --skill context-os-cli -a codex`. Or copy the skill folder (.claude/skills/context-os-cli in jacob-dietle/context-os) into .agents/skills/context-os-cli in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jacob-dietle/context-os --skill context-os-cli -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/context-os-cli, .gemini/skills/context-os-cli, .github/skills/context-os-cli and .opencode/skills/context-os-cli in your project.
Going by SKILL.md and its folder, Context Os CLI needs the command-line tools its instructions call (git).
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Context Os CLI is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 4.1k tokens (SKILL.md is roughly 16k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.4k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Context Os CLI: LLM Wiki Knowledge Graph (Egonex-AI/Understand-Anything, 86k stars), Ontology (1mancompany/OneManCompany, 440 stars), Graph (agenticnotetaking/arscontexta, 3.5k stars) and Obsidian Canvas Boards (AgriciDaniel/claude-obsidian, 15k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
jacob-dietle (a GitHub user) maintains it in jacob-dietle/context-os, which has 111 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on August 13, 2026.
Source: jacob-dietle/context-os on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.