ontoly-software-graph
Use Ontoly's deterministic Software Graph and MCP capabilities for architecture review, request tracing, dependency analysis, configuration lookup, and impact analysis before falling back to source-file search.
Install / Use
npx skills add anbeime/skill --skill ontoly-software-graphInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Our assessment of ontoly-software-graph
ontoly-software-graph scores 86/100 on our quality scale, 2321st of 4,698 Development & Engineering skills we index (top 50%).
Its SKILL.md is 3.1 KB long, split into 6 sections with 1 code example: a solid amount of guidance for an agent.
With 7,172 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so ontoly-software-graph is actively maintained.
- Our last check on 2026-11-03 found the source still online.
- No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
- Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-09-28. Automated pattern scan on 2026-09-28. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
ontoly-software-graph compared with similar skills
All 4 of these similar skills score higher than ontoly-software-graph; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| ontoly-software-graph (this skill)by anbeime | 86 | 7.2k | 53d ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| Agent-Reachby Panniantong | 100 | 112.3k | 8d ago | CLAUDE.md |
| rufloby ruvnet | 100 | 81.9k | today | CLAUDE.md |
| headroomby headroomlabs-ai | 100 | 79.8k | today | CLAUDE.md |
Frequently asked questions
- How do I install ontoly-software-graph?
- Run
npx skills add anbeime/skill --skill ontoly-software-graph. The install tabs above show the steps for each supported agent. - Which AI agents does ontoly-software-graph work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is ontoly-software-graph safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is ontoly-software-graph still maintained?
- The repository was last updated about 2 months ago, so ontoly-software-graph is actively maintained.
Skill content
View source on GitHubname: ontoly-software-graph description: Use Ontoly's deterministic Software Graph and MCP capabilities for architecture review, request tracing, dependency analysis, configuration lookup, and impact analysis before falling back to source-file search.
Ontoly Software Graph
Use this skill when a coding agent needs evidence-backed software understanding from an Ontoly graph before searching repository files directly.
When to Use
- Explaining a repository architecture
- Tracing a request, route, controller, service, or dependency path
- Finding owners of services, modules, routes, configuration, or environment variables
- Reviewing dependency impact before a refactor
- Auditing dead code, cycles, unresolved imports, graph quality, or semantic coverage
- Preparing documentation, onboarding notes, or architecture review from graph evidence
Required Workflow
-
Check whether an Ontoly graph already exists by looking for
.ontoly/,SoftwareGraph.json,diagnostics.json, validation reports, or an Ontoly MCP configuration. -
If no graph exists and the user permits local analysis, run:
ontoly build . -
Inspect graph health before answering: diagnostics, graph hash, semantic coverage, trust or quality score, framework detection, and generation timestamp.
-
Prefer Ontoly CLI or MCP capabilities for graph questions instead of scanning source files first.
-
Use repository search only when Ontoly cannot answer, the graph is stale, the graph is incomplete, or the user explicitly asks for source-level verification.
-
Always cite graph evidence in the answer: node IDs, edge types, file paths, source locations, diagnostics, or framework analyzer output.
-
State confidence from graph evidence. Do not guess confidence.
Useful Ontoly Capabilities
ExplainArchitecturefor repository and package topologyFindDependenciesfor dependency trees and direct consumersImpactAnalysisfor refactor blast radiusTraceExecutionfor request, route, and call-flow tracingFindConfigurationUsagefor configuration and environment variable usageFrameworkReportfor detected framework concepts such as modules, controllers, providers, and routesFindDeadCodefor unreachable or unused graph regions
Answer Shape
When answering, include:
- the direct answer
- graph evidence
- confidence
- diagnostics or caveats
- fallback source inspection only if needed
Example:
AuthController handles authentication.
Evidence:
- node: class:src/auth/auth.controller.ts:AuthController
- route edges: HANDLES POST /login, POST /logout
- dependency edges: USES AuthService, JwtService
Confidence: high, because the graph has controller, route, and dependency edges with source locations.
Fallback Rules
- If the graph is missing, build it first when allowed.
- If graph validation fails, report the failure and use source search only to verify the affected area.
- If multiple nodes match the same name, ask for disambiguation or show the candidates with package/module context.
- If the requested concept is not in the graph, return
NOT_FOUNDwith the closest graph evidence instead of inventing an answer.
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
Agent-Reach
112.3kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
ruflo
81.9k🌊 The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory, self-learning intelligence, federation, vector RAG integration, and native Claude Code / Codex / Hermes and many more Integrated
headroom
79.8kCompress tool outputs, logs, files, and RAG chunks before they reach the LLM. 20% fewer tokens for coding agents, 60-95% fewer tokens for JSON, same answers. Library, proxy, MCP server.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
