Establish a Knowledge Base

[CraneReturn]

If I want to use graphify's ability to generate wikis from raw data for my Knowledge Base, the currently generated content seems to be flat. Is there any way I can place the generated wiki content according to my desired directory structure? For example, general tools would be placed in wiki/tools when generated, and some people-finding map capabilities would be placed in wiki/maps. Can this be achieved through skills or by setting some restrictions for agents? Has anyone kind enough tried this?

[starkmarkus]

I think this is a reasonable use case, but I would be careful about relying only on agent instructions for the directory structure.

If the generated wiki is currently flat, then a prompt/skill can probably influence the content and maybe suggest categories, but it may not reliably control where files are written unless Graphify exposes that as part of the generation pipeline.

The more robust approach would be to separate this into two steps:

1. classify each generated page into a knowledge-base category
2. write or move the page into the matching directory

For example:

tools/* -> general tools
maps/* -> mapping / people-finding / geospatial capabilities
people/* -> people or organization profiles
workflows/* -> procedures / playbooks

A skill could help define that taxonomy, but I would prefer an explicit output rule or config like a path-mapping file, rather than hoping the agent always follows the folder convention.

So my read is:

• if Graphify already supports custom output paths, use that directly
• if not, this may need a post-generation organizer step
• agent restrictions/skills can help classify content, but should not be the only source of truth
• a feature request for “wiki taxonomy / directory mapping” would make sense

For a knowledge base, this would be quite useful. Flat output is fine for small generated wikis, but once the generated content grows, having a deterministic directory structure becomes important for navigation, review, and long-term maintenance.