maintaining an LLM wiki has been a lot more effort than I thought, at least if we are trying to maintain a high quality in structure and writing comprehension (for easier lookups both for the agent and human). Are people just shotgunning their agent wikis or how
> maintaining an LLM wiki has been a lot more effort than I thought
Same here. Wikis start out good, but either devolve in a journal-y mess after a while and many updates, or require constant expensive rewrites. (I didn't use the software of the OP.)
We need to make an effort to distinguish “this is a thing for humans” vs “this is a thing for bots” in our naming IMHO. In that respect, “open wiki” is not such a great name. “Agent Wiki” or similar would be better.
Without such a qualifier, “wiki” carries a strong connotation of (usually collaborative) human involvement. That’s literally what it’s famous for.
Thats just my $0.02 on the naming. I definitely think it’s a worthwhile idea. All the best.
Have a look at the prompts in the GitHub [0]. It defines a System Prompt and specifies the documentation structure. This would allow you to switch coding agents, instead of relying on how your coding agent interprets the command "write docs".
This is mostly a thin clintypescript wrapper around the prompts.
This could have been a SKILL
maintaining an LLM wiki has been a lot more effort than I thought, at least if we are trying to maintain a high quality in structure and writing comprehension (for easier lookups both for the agent and human). Are people just shotgunning their agent wikis or how
> maintaining an LLM wiki has been a lot more effort than I thought
Same here. Wikis start out good, but either devolve in a journal-y mess after a while and many updates, or require constant expensive rewrites. (I didn't use the software of the OP.)
We need to make an effort to distinguish “this is a thing for humans” vs “this is a thing for bots” in our naming IMHO. In that respect, “open wiki” is not such a great name. “Agent Wiki” or similar would be better.
Without such a qualifier, “wiki” carries a strong connotation of (usually collaborative) human involvement. That’s literally what it’s famous for.
Thats just my $0.02 on the naming. I definitely think it’s a worthwhile idea. All the best.
What does this do better than just asking your agent to "write docs" or a more robustly defined prompt/skill?
Have a look at the prompts in the GitHub [0]. It defines a System Prompt and specifies the documentation structure. This would allow you to switch coding agents, instead of relying on how your coding agent interprets the command "write docs".
[0]: https://github.com/langchain-ai/openwiki/blob/main/src/agent...
I swear most of these tools are made for the sake of it…
While good old prompting is often better than plan mode or superpower skills.
This is what we do. The same agent writing the code can also write the docs.