Qmd
breferrari/obsidian-mind
Search the vault using QMD semantic search. An agent skill from breferrari/obsidian-mind.
Use Ontoly's deterministic Software Graph, MCP server, and agent skills for architecture review, request tracing, impact analysis, and dependency analysis.
Install Ontoly Software Graph
$ npx skills add sickn33/agentic-awesome-skills --skill ontoly-software-graph -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install sickn33/agentic-awesome-skills ontoly-software-graph --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/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/ontoly-software-graph .claude/skills/ontoly-software-graph && 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 "ontoly-software-graph" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/ontoly-software-graph into .claude/skills/ontoly-software-graph/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ontoly-software-graph", 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/sickn33/agentic-awesome-skills/tree/main/skills/ontoly-software-graphType 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 sickn33/agentic-awesome-skills --skill ontoly-software-graph -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install sickn33/agentic-awesome-skills ontoly-software-graph --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/ontoly-software-graph .agents/skills/ontoly-software-graph && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "ontoly-software-graph" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/ontoly-software-graph into .agents/skills/ontoly-software-graph/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ontoly-software-graph", 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 sickn33/agentic-awesome-skills --skill ontoly-software-graph -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install sickn33/agentic-awesome-skills ontoly-software-graph --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/ontoly-software-graph .cursor/skills/ontoly-software-graph && 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 "ontoly-software-graph" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/ontoly-software-graph into .cursor/skills/ontoly-software-graph/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ontoly-software-graph", 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/sickn33/agentic-awesome-skills.git --path skills/ontoly-software-graph--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 sickn33/agentic-awesome-skills --skill ontoly-software-graph -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install sickn33/agentic-awesome-skills ontoly-software-graph --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/ontoly-software-graph .gemini/skills/ontoly-software-graph && 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 "ontoly-software-graph" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/ontoly-software-graph into .gemini/skills/ontoly-software-graph/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ontoly-software-graph", 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 sickn33/agentic-awesome-skills ontoly-software-graphInstalls 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 sickn33/agentic-awesome-skills --skill ontoly-software-graph -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/ontoly-software-graph .github/skills/ontoly-software-graph && 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 "ontoly-software-graph" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/ontoly-software-graph into .github/skills/ontoly-software-graph/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ontoly-software-graph", 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 sickn33/agentic-awesome-skills --skill ontoly-software-graph -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install sickn33/agentic-awesome-skills ontoly-software-graph --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/ontoly-software-graph .opencode/skills/ontoly-software-graph && 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 "ontoly-software-graph" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/ontoly-software-graph into .opencode/skills/ontoly-software-graph/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ontoly-software-graph", 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.
Facts
- Skill name
ontoly-software-graph- GitHub stars
- 47k
- Used in
- 1 other repo
- Token cost
- ~1.8k tokens
- SKILL.md length
- 890 words
- Files
- 1
- Skills in repo
- 1,394
- Repo updated
- First seen
- Licence
- MIT
At a glance
Use Ontoly's deterministic Software Graph, MCP server, and agent skills for architecture review, request tracing, impact analysis, and dependency analysis.
- Works in 6 steps: Verify Ontoly Is Available → Build or Refresh the Graph → Check Trust, Diagnostics, and Coverage → …
- Tasks that involve Software architecture
- SKILL.md covers Overview, When to Use This Skill, How It Works and Examples, plus 5 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Ontoly Software Graph is an agent skill from sickn33/agentic-awesome-skills. Use Ontoly's deterministic Software Graph, MCP server, and agent skills for architecture review, request tracing, impact analysis, and dependency analysis.
Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Agent Workflows, covering Software architecture and MCP servers. It works with Model Context Protocol. The repository describes itself as: AAS Core is the local, agent-first control plane for complete catalog discovery, agent-owned selection, stack validation, and planning, backed by 2,400+ agentic skills. Includes… The licence is MIT.
When your agent uses it
- Tasks that involve Software architecture
- Tasks that involve MCP servers
Example prompts
- “/ontoly-software-graph”
Workflow steps
6 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 1e53ce2. It shows what the files ask for, not the result of running them.
Tool permissions
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.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Ontoly Software Graph loads about 1.8k tokens when it runs. Until then it costs about 44 tokens; SKILL.md has 890 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.
Safety
Auto-check passed
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.
SKILL.md
The full file from sickn33/agentic-awesome-skills at commit 1e53ce2, republished under its MIT licence (© sickn33). 890 words, ~1,819 tokens.
Download SKILL.mdSave it as
.claude/skills/ontoly-software-graph/SKILL.md (or your agent's skills folder).- name
- ontoly-software-graph
- description
- Use Ontoly's deterministic Software Graph, MCP server, and agent skills for architecture review, request tracing, impact analysis, and dependency analysis.
- category
- development
- risk
- critical
- source
- community
- source_repo
- 0xsarwagya/ontoly
- source_type
- community
- date_added
- 2026-07-14
- author
- 0xsarwagya
- tags
- software-graph, codebase-analysis, mcp, typescript, architecture, impact-analysis
- tools
- claude, cursor, gemini, codex, antigravity
- license
- MIT
Ontoly Software Graph
Overview
Ontoly builds a deterministic Software Graph from a TypeScript repository and exposes it through CLI queries, MCP capabilities, and agent skills. Use this skill when a coding agent needs evidence-backed codebase understanding before searching files directly.
This skill is an operating guide for the public Ontoly project. It does not contain compiler logic; all software understanding should come from Ontoly's generated graph, semantic model, query engine, and MCP server.
When to Use This Skill
- Use when the user asks for repository architecture, module ownership, or onboarding help.
- Use when tracing a request, route, controller, service, provider, dependency, or call chain.
- Use when estimating impact for removing, renaming, or refactoring a symbol, module, package, route, or service.
- Use when reviewing dependency topology, circular imports, dead code, configuration usage, or environment variables.
- Use when the user explicitly wants Ontoly, Software Graph, MCP, graph validation, semantic coverage, or agent skills.
How It Works
Step 1: Verify Ontoly Is Available
Check whether the repository already has Ontoly outputs such as .ontoly/, SoftwareGraph.json, validation reports, or documented Ontoly scripts. If the ontoly command is unavailable, ask the user whether to install or use the repository's documented package manager command.
Recommended local checks:
ontoly --help
find . -maxdepth 3 \( -name "SoftwareGraph.json" -o -name ".ontoly" \) -printStep 2: Build or Refresh the Graph
Only run a graph build in the repository the user asked about. Tell the user that graph generation may create local Ontoly artifacts before running it.
ontoly build .If the project documents a different command, prefer the documented command over guessing.
Step 3: Check Trust, Diagnostics, and Coverage
Before answering architectural questions, inspect Ontoly diagnostics, graph statistics, trust, and semantic coverage. Treat unresolved imports, low trust, missing framework detection, or graph validation failures as answer constraints.
Use the CLI or MCP capabilities exposed by the installed Ontoly version. Prefer structured graph queries over text search.
Step 4: Use Ontoly MCP Capabilities
Start or connect to the Ontoly MCP server when the host supports MCP:
ontoly mcpUse capabilities such as architecture summaries, dependency analysis, request tracing, impact analysis, configuration lookup, framework reports, dead-code analysis, and graph validation when available.
Step 5: Answer With Evidence
Every answer should include:
- The Ontoly capability or query used.
- The node, edge, route, package, or diagnostic evidence that supports the answer.
- A confidence statement derived from graph evidence.
- Any known limitations caused by missing graph regions or diagnostics.
Step 6: Fall Back Gracefully
Only inspect repository files directly when Ontoly cannot answer, the graph is missing, diagnostics make the graph untrustworthy for the question, or the user asks for source-level verification. When falling back, explain which graph evidence was insufficient.
Examples
Architecture Review
User asks: "Explain this repository."
Workflow:
- Verify or build the Ontoly graph.
- Check graph trust, diagnostics, detected frameworks, packages, modules, services, routes, and largest dependency hubs.
- Use Ontoly's architecture summary or equivalent query.
- Report the architecture with graph evidence and confidence.
Request Tracing
User asks: "Trace the login flow."
Workflow:
- Search graph nodes for authentication routes and controllers.
- Trace route-to-controller-to-service-to-repository relationships.
- Include unresolved edges or missing relationships as limitations.
- Avoid opening source files unless the graph cannot identify the flow.
Show full SKILL.md (370 more words)Show less
Impact Analysis
User asks: "What breaks if I remove UserRepository?"
Workflow:
- Locate the graph node for
UserRepository. - Query callers, consumers, dependency injection edges, modules, routes, and packages that reference it.
- Separate direct dependents from transitive impact.
- Include confidence based on explicit graph relationships.
Best Practices
- Prefer Ontoly graph queries before grep, AST parsing, or broad file search.
- Keep graph evidence separate from inference.
- Treat diagnostics as part of the answer, not as noise.
- Use exact node IDs, route paths, package names, and relationship names when available.
- Rebuild the graph after large user changes before making claims about current architecture.
- Keep fallbacks narrow and explain why they were needed.
Limitations
- Ontoly does not replace compiler, test, or runtime validation.
- Graph quality depends on the Ontoly version, supported language frontend, repository setup, and diagnostics.
- Missing or partial framework detection lowers confidence for framework-specific answers.
- Do not claim a relationship exists unless it is present in the graph or clearly labeled as an inference.
- Stop and ask for clarification if the repository path, target graph, or requested analysis scope is ambiguous.
Security & Safety Notes
- Run Ontoly only on repositories the user is authorized to analyze.
- Do not send graph files, source code, environment variables, diagnostics, or repository metadata to external services unless the user explicitly requests it.
- Treat environment-variable nodes, configuration nodes, and diagnostics as potentially sensitive.
- Graph generation is local analysis but can create files such as graph output, diagnostics, indexes, or caches inside the repository.
- Do not execute project build scripts, package installation, or network commands unless they are documented by the repository or approved by the user.
Common Pitfalls
Problem: Answering from file search even though the graph already contains the relationship. Solution: Query Ontoly first and use file inspection only as a fallback.
Problem: Reporting low-confidence inference as a graph fact. Solution: Label the claim as inferred and cite the supporting graph evidence separately.
Problem: Ignoring diagnostics. Solution: Include graph validation and compiler diagnostics when they affect confidence.
Related Skills
@developer-onboarding- Use for broad onboarding when Ontoly is unavailable.@sdk-dx- Use for SDK design and developer experience reviews after Ontoly identifies public APIs.@api-onboarding- Use for API-specific onboarding when route and operation evidence is available.
© sickn33, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/ontoly-software-graph of sickn33/agentic-awesome-skills.
Open the folder on GitHubat commit 1e53ce2
Used in 1 other repository
We found 5 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in sickn33/agentic-awesome-skills, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Ontoly Software Graph 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 |
|---|---|---|---|---|---|---|
| Ontoly Software Graph this skillsickn33/agentic-awesome-skills | 47k | 1 repos | ~1.8k | Automated safety check: Pass | MIT | |
| Qmdbreferrari/obsidian-mind | 4.9k | — | ~1.7k | Automated safety check: Pass | MIT | |
| Agent Memory MCPdavila7/claude-code-templates | 32k | 6 repos | ~526 | Automated safety check: Pass | MIT | |
| Crush Configurationcharmbracelet/crush | 29k | — | ~3.7k | Automated safety check: Pass | Custom licence | |
| PicoClaw Agentsipeed/picoclaw | 30k | — | ~7.2k | Automated safety check: Notes | MIT | |
| Chatgpt AppsHaohao-end/openagent | 807 | 1 repos | ~4.9k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Agent Memory MCP
davila7/claude-code-templates
A hybrid memory system that provides persistent, searchable knowledge management for AI agents (Architecture, Patterns, Decisions).
Crush Configuration
charmbracelet/crush
Explains how to configure the Crush coding agent with crushrc or crush.json, covering providers, models, LSPs, MCP servers, hooks, permissions and config precedence.
PicoClaw Agent
sipeed/picoclaw
Answers questions about running and changing PicoClaw, from onboarding and model selection to MCP server setup, skill loading and scheduled jobs.
Chatgpt Apps
Haohao-end/openagent
Build, scaffold, refactor, and troubleshoot ChatGPT Apps SDK applications that combine an MCP server and widget UI.
Chatgpt App Builder
alpic-ai/skybridge
Guide developers through creating and updating ChatGPT plugins.
More from sickn33/agentic-awesome-skills
All 1,394 skills in this repoLiuguang Banlan UI
sickn33/agentic-awesome-skills
Implements an interface in one of two named color modes, iridescent white or colorful black, from a parameterized starter that reports measured color intensity.
User Thoughts Memory
sickn33/agentic-awesome-skills
Saves a user's project decisions, rules and preferences into a project-local mdbase so later sessions and other agents can recover the intent.
Using LWC Memory and Graphs
sickn33/agentic-awesome-skills
Keeps project decisions, research and verified results available across coding-agent sessions through LWC memory, a document Wiki graph and a CodeGraph code index.
Find Complementary Founders
sickn33/agentic-awesome-skills
Guides an agent through assessing its own owner for cofounder fit, publishing an approved profile, and ranking complementary profiles other agents published for their owners.
Whatsapp Cloud API
sickn33/agentic-awesome-skills
Integracao com WhatsApp Business Cloud API (Meta). An agent skill from sickn33/agentic-awesome-skills.
Cline Pilot
sickn33/agentic-awesome-skills
Acts as a proxy for the Cline CLI, dispatching coding tasks one at a time, monitoring runs by hard evidence, relaying decisions to you and learning per-project preferences.
Related
Works with
Categories
Questions about Ontoly Software Graph
What does Ontoly Software Graph do?
Use Ontoly's deterministic Software Graph, MCP server, and agent skills for architecture review, request tracing, impact analysis, and dependency analysis. Ontoly Software Graph is an agent skill from sickn33/agentic-awesome-skills. Use Ontoly's deterministic Software Graph, MCP server, and agent skills for architecture review, request tracing, impact analysis, and dependency analysis.
When should I use Ontoly Software Graph?
Ontoly Software Graph fits situations like: tasks that involve Software architecture; tasks that involve MCP servers.
How do I install Ontoly Software Graph in Claude Code?
Run `npx skills add sickn33/agentic-awesome-skills --skill ontoly-software-graph -a claude-code`. Or copy the skill folder (skills/ontoly-software-graph in sickn33/agentic-awesome-skills) into .claude/skills/ontoly-software-graph in your project. Claude Code loads it when a task matches its description.
How do I install Ontoly Software Graph in Codex?
Run `npx skills add sickn33/agentic-awesome-skills --skill ontoly-software-graph -a codex`. Or copy the skill folder (skills/ontoly-software-graph in sickn33/agentic-awesome-skills) into .agents/skills/ontoly-software-graph in your project. Codex loads it when a task matches its description.
Can I use Ontoly Software Graph in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add sickn33/agentic-awesome-skills --skill ontoly-software-graph -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ontoly-software-graph, .gemini/skills/ontoly-software-graph, .github/skills/ontoly-software-graph and .opencode/skills/ontoly-software-graph in your project.
What does Ontoly Software Graph need to run?
SKILL.md names no scripts, command-line tools or credentials: Ontoly Software Graph is instructions for the agent only.
Does Ontoly Software Graph access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Ontoly Software Graph safe to install?
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.
What licence does Ontoly Software Graph use?
Ontoly Software Graph is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Ontoly Software Graph use?
About 1.8k tokens (SKILL.md is roughly 7.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Ontoly Software Graph?
Skills that share tags, products or a category with Ontoly Software Graph: Qmd (breferrari/obsidian-mind, 4.9k stars), Agent Memory MCP (davila7/claude-code-templates, 32k stars), Crush Configuration (charmbracelet/crush, 29k stars) and PicoClaw Agent (sipeed/picoclaw, 30k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Ontoly Software Graph?
sickn33 (a GitHub user) maintains it in sickn33/agentic-awesome-skills, which has 47,304 GitHub stars. The repository holds 1,394 skills in this directory. The repository was last updated on October 6, 2026.
Source: sickn33/agentic-awesome-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.