graphify
Skill191 starsChanged 5 months agoMITView on GitHub
Knowledge graph engine for B2B sales intelligence. Builds queryable graphs from product catalogs, customer conversations, and market research. Powered by graphify.
- Installs packages
125 other projects use a version of this.
Adopted by
Most recently taken up by
- chrisezedi/claude-skillstheir own version, first seen Nov 16, 2026
- adeiltonpessini/kit-memoria-iatheir own version, first seen Nov 16, 2026
- miratcan/claude-skillstheir own version, first seen Nov 16, 2026
- AlexanderTar/swarmruntheir own version, first seen Nov 16, 2026
- lunox-work/sandbox-factorytheir own version, first seen Nov 16, 2026
- matt-riley/agent-skillstheir own version, first seen Nov 15, 2026
Used with
Projects with it also use remotion-maps, remotion-saas and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
OpenAISkillremotion-maps
Remotion Map animation knowledge
Also in 4 projects that use this
OpenAISkillremotion-saas
Build an app with Remotion
Also in 4 projects that use this
royaluniondesign-sysSkilldeployment-patterns
Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications.
Also in 4 projects that use this
mstuder-slalomSkilldjango-verification
Verification loop for Django projects: migrations, linting, tests with coverage, security scans, and deployment readiness checks before release or PR.
Also in 3 projects that use this
ttmouseSkillprompt-master
提示词主控 - 智能选择合适的领域skill并生成提示词,支持自动领域分类和调度
Also in 4 projects that use this
seikaikyoSkilldoubt-driven-development
對非平凡決策啟動新鮮 context 對抗審查(找碴不背書),在修正還便宜的時候抓出錯誤方向。適用:高風險改動(production、資安敏感邏輯、不可逆操作)、不熟的程式碼、要宣稱「這樣是安全的 / 可行的」之前。機械性操作與一行修改不適用。
Also in 6 projects that use this
Other versions125 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 125
- safishamsi/graphify★ 148ksame name
- Graphify-Labs/graphify★ 148ksame name
- zaxbysauce/opencode-swarm★ 532same name
- ZaxbyHub/opencode-swarm★ 531same name
- nandyalu/trailarr★ 486same name
- bdfinst/agentic-dev-team★ 304same name
- cin12211/orca-q★ 225same name
- sammcj/agentic-coding★ 172same name
- EBISPOT/ols4★ 108same name
- buildomator/buildomator★ 102same name
115 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository12 other files it gives its agents.
- AGENTS.mdAGENTS.md
- workspace/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- b2b-sdr-agentSkill
- chroma-memorySkill
- delivery-queueSkill
- lead-discoverySkill
- quotation-generatorSkill
- sdr-humanizerSkill
- supermemorySkill
- telegram-toolkitSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 123 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 32
When to use: Before quotation, during BANT qualification, when customer asks about related products.
- Distinctive: line 108
After building a graph, query it for specific sales intelligence:
“Common” is measured: kept by at least 6 in 10 of the 123 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Graphify — Sales Intelligence Knowledge Graph
Build knowledge graphs from your product catalog, customer conversations, and market research to surface hidden connections, cross-sell opportunities, and competitive insights.
Based on graphify — adapted for B2B SDR context.
Triggers
- Manual: "Build a knowledge graph of our products"
- Manual: "Map customer relationships"
- Manual: "Analyze competitive landscape"
- Cron (optional): Weekly rebuild after lead-discovery updates
Prerequisites
# Ensure graphify is installed
python3 -c "import graphify" 2>/dev/null || pip install graphifyy -q --break-system-packages 2>&1 | tail -3Use Cases
1. Product Catalog Graph
Build a graph from product-kb/ to understand product relationships, shared certifications, overlapping target markets, and cross-sell paths.
When to use: Before quotation, during BANT qualification, when customer asks about related products.
python3 -c "
import json
from graphify.extract import collect_files, extract
from graphify.build import build
from graphify.cluster import cluster, score_all
from graphify.analyze import god_nodes, surprising_connections
from pathlib import Path
# Extract from product catalog
files = collect_files(Path('product-kb'))
ast_result = extract(files)
# Build and analyze
G = build([ast_result])
communities, labels = cluster(G)
cohesion = score_all(G, communities)
gods = god_nodes(G, top_n=5)
surprises = surprising_connections(G, communities, top_n=5)
print('=== Core Products (God Nodes) ===')
for g in gods:
print(f' {g[\"label\"]} — {g[\"edges\"]} connections')
print('=== Surprising Connections ===')
for s in surprises:
print(f' {s[\"source\"]} ↔ {s[\"target\"]} [{s[\"confidence\"]}]')
"Sales actions from graph insights:
- God nodes = your anchor products → lead with these in cold outreach
- Surprising connections = non-obvious cross-sell paths → "customers who buy X often need Y"
- Communities = product families → bundle pricing opportunities
2. Customer Intelligence Graph
Build a graph from conversation histories and CRM data to map customer relationships, identify buying patterns, and find warm introduction paths.
Input sources:
- ChromaDB conversation history (
chroma:recall) - CRM records (Google Sheets)
- Supermemory research notes (
memory:search)
What to extract (semantic, not AST):
- Companies → employees (decision makers, influencers)
- Companies → products they bought or inquired about
- Companies → companies (same industry, same region, competitors)
- People → people (referrals, shared contacts)
- Deals → products, timelines, objections
Sales actions from graph insights:
- Cluster customers by behavior → tailor nurture campaigns per cluster
- Find bridge nodes (customers who connect segments) → referral candidates
- Detect isolated nodes (customers with no follow-up) → stalled lead recovery
3. Market Research Graph
Build a graph from lead-discovery research, competitor intel, and market signals stored in Supermemory.
What to extract:
- Competitors → products, pricing, markets
- Markets → trends, regulations, trade shows
- Customers → competitors they also buy from
- Regions → seasonal demand patterns
Sales actions from graph insights:
- Surprising connections between markets → expansion opportunities
- Competitor clusters → differentiation strategy
- Market god nodes → priority regions for lead-discovery rotation
Graph Query (runtime)
After building a graph, query it for specific sales intelligence:
# BFS — broad context around a topic
python3 -m graphify query "hydraulic excavator certification" --budget 1500
# DFS — trace a specific relationship chain
python3 -m graphify query "Dubai customer fleet" --dfs --budget 1000Use before:
- Responding to product questions → query product graph for specs and relationships
- Preparing quotations → find cross-sell opportunities in graph
- Cold outreach → understand prospect's market context from research graph
Graph Export
python3 -c "
from graphify.export import to_json, to_html
from graphify.build import build_from_json
from pathlib import Path
import json
data = json.loads(Path('graphify-out/graph.json').read_text())
G = build_from_json(data)
# Interactive HTML for owner dashboard
to_html(G, Path('graphify-out/graph.html'))
# JSON for programmatic access
to_json(G, Path('graphify-out/graph.json'))
"- HTML: Interactive vis.js graph — share with owner for pipeline visibility
- JSON: Machine-readable — feed into reporting or CRM enrichment
- Report:
graphify-out/GRAPH_REPORT.md— god nodes, communities, knowledge gaps
Output Format (report to owner)
Product Knowledge Graph:
- X nodes · Y edges · Z communities
- Core products: [god nodes list]
- Cross-sell opportunities: [surprising connections]
- Knowledge gaps: [isolated products with missing specs]
Recommendation: Update product-kb for [gap products] to improve graph coverage.Integration with Other Skills
| Skill | How Graphify Helps |
| lead-discovery | Query market graph before searching → better targeting |
| quotation-generator | Query product graph → include related products in quote |
| chroma-memory | Feed conversation data → build customer intelligence graph |
| supermemory | Feed research notes → build market research graph |
| sdr-humanizer | Graph context → more relevant, personalized conversations |
Rebuild Strategy
- Product graph: Rebuild when
product-kb/changes (new products, updated specs) - Customer graph: Rebuild weekly from ChromaDB + CRM snapshots
- Market graph: Rebuild after lead-discovery runs (daily 10:00 output)
Store graphs in graphify-out/ — survives across sessions, queryable anytime.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

