Agent skill · product strategy · sickn33
ontoly-software-graph
Use Ontoly's deterministic Software Graph, MCP server, and agent skills for architecture review, request tracing, impact analysis, and dependency analysis.
Why this skill is useful
Provides domain-specific knowledge on using Ontoly's Software Graph for architecture review and dependency analysis that the AI wouldn't reliably generate on its own.
What it needs
Requires ontoly installed locally. About 4k tokens when loaded. Last updated 2026-08-07. 44,571 stars on the source repository.
What this skill does
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: Step 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. 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. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sickn33/ontoly-software-graph--5bfc0e