graphify
From the author
Use for any question about a codebase, its architecture, file relationships, or project content — especially when graphify-out/ exists, where the question should be treated as a graphify query first. Turns any input (code, docs, papers, images, videos) into a persistent knowledge graph with god nodes, community detection, and query/path/explain tools.
Install
npx skills add gavishap/omnia-vault --skill graphify -a claude-code
Installs to .claude/skills/graphify/ · Each command fetches the skill straight from GitHub with the open skills CLI.
No download: this skill’s licence (Custom or unclear) does not let us redistribute its files. The install commands fetch them from GitHub instead.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 75
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- understandEgonex-AI/Understand-AnythingAnalyze a codebase to produce an interactive knowledge graph for understanding architecture, components, and relationshipsPlanning★ 88.8K
- docs-from-codeVarnan-Tech/opendirectoryGenerates and updates README.md and API reference docs by reading your codebase's functions, routes, types, schemas, and architecture. Uses graphify to build a knowledge graph first, then writes accurate docs from it. Use when asked to write docs, generate a README, document an API, update stale docs, create an API reference from code, add an architecture section, or document a project in any language. Trigger when a user says their docs are missing, outdated, or wants to document their codebase without writing it manually.Engineering★ 686
- graphql-architectsandbaseai/sandbase-skillsPlan, implement, or review graphql architect work in an existing codebase with compatibility, security, and verification controls. Use when the user explicitly requests graphql architect work.Planning★ 203
- understand-chatEgonex-AI/Understand-AnythingUse when you need to ask questions about a codebase or understand code using a knowledge graphEngineering★ 88.8K
- knowledge-graphllopresto87/CypressBuild and maintain the project's knowledge graph — a tiered set of nodes under docs/graph/ that lets an agent load only the few facts a task needs instead of the whole codebase. Use when adopting a project, when a fact changes, when a node grows too large, or when a task should have matched a node's triggers and didn't. Enforces one home per fact (dedup), honest per-node budgets, cite-don't-fabricate, and a mechanical linter. The library wiki (docs/graph/libraries/) is a leaf tier of this graph, not a separate system.Productivity★ 116
- planningmblode/agent-skillsCreates and reviews executable implementation plans grounded in repository evidence, with vertical slices, explicit decisions, and verification criteria. Use when asked to "plan this feature", "stress-test this plan", "grill me", or "split this into tickets". For architecture use codebase-architecture; for code review use tidy.Planning★ 171
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in