Not a task — informational heads-up for the maintainers, nothing to implement. Close it freely.
Hi — I curate StackMap, a hand-curated knowledge graph of open-source AI/agent tools. Every entry is human-reviewed: a summary, an opinionated note on when to use it (and when not), and typed edges to what it pairs with or competes against — with the why written down.
GraphGen earned a place on the map:
How we mapped it:
- pairs well with
llamafactory — GraphGen's README names LLaMA-Factory as the intended next step: generate gap-targeted QA data with GraphGen, then fine-tune any of LLaMA-Factory's 100+ models on it via LoRA/QLoRA.
- alternative to
adala — Two roads to training data without annotators: adala points labeling agents at real data and checks them against ground truth, graphgen synthesizes multi-hop QA from a knowledge graph aimed at the model's knowledge gaps.
If you want it visible in your README, every mapped repo has a badge:
[](https://stackmap.shipwithai.xyz/repos/InternScience/graphgen?utm_source=badge)
It renders as StackMap | ↔ 5 typed links and links to the page above. Static JSON — the count updates itself as the map changes, nothing for you to maintain.
If any of this misrepresents the project — an edge you'd dispute, a sharper "when NOT to use" — reply here and a human fixes it. And feel free to just close this issue; it's only a heads-up.
Hi — I curate StackMap, a hand-curated knowledge graph of open-source AI/agent tools. Every entry is human-reviewed: a summary, an opinionated note on when to use it (and when not), and typed edges to what it pairs with or competes against — with the why written down.
GraphGen earned a place on the map:
How we mapped it:
llamafactory— GraphGen's README names LLaMA-Factory as the intended next step: generate gap-targeted QA data with GraphGen, then fine-tune any of LLaMA-Factory's 100+ models on it via LoRA/QLoRA.adala— Two roads to training data without annotators: adala points labeling agents at real data and checks them against ground truth, graphgen synthesizes multi-hop QA from a knowledge graph aimed at the model's knowledge gaps.If you want it visible in your README, every mapped repo has a badge:
It renders as
StackMap | ↔ 5 typed linksand links to the page above. Static JSON — the count updates itself as the map changes, nothing for you to maintain.If any of this misrepresents the project — an edge you'd dispute, a sharper "when NOT to use" — reply here and a human fixes it. And feel free to just close this issue; it's only a heads-up.