Daniel Rosehill Open Source Custom LLM Configuration Library
Index
LLM Name
- about.md
- Config
-- config.md
-- config.json
- The
LLM Name
is the LLM's name. about.md
provides a little bit of information about the custom LLM's intended purposeconfig
houses configuration files provided in markdown and JSON format (the latter for machine-readibility and portability)
About This Repository
This repository contains links to custom LLMs that I have build on top of ChatGPT (although increasingly I'm exploring the use of other LLMs including Claude).
I am finding amazing utility in creating custom LLMs for specific purposes (commonly those related to my professional life).
However, while it lacks the ability of custom LLMs to quickly store detailed contextual information, prompt engineering is often enough to quickly and dramatically accelerate the value yielded from working with LLMs.
The overarching objective is to create a sort of "fleet" of LLM agents to help me manage various aspects of my work and personal lives.
Like everything I open-source, I'm doing so to make a small contribution to the collective sum of human knowledge. If you'd like to use any of these LLMs for whatever reason, you have my full permission to do so.
File Formats
LLMs are organised into folders describing their purpose.
- LLMName/
- Config/
- config.txt
- config.json
- about.md
In this setup:
config.txt
is a text file containing the LLM configurationconfig.json
is a JSON file containing the LLM configurationabout.md
is a markdown document describing the purpose of the LLM and providing other details intended for a human reader
You can use JSON
directly in ChatLLM's custom LLM editor to effectively recreate any of these LLMs.
Pronouns
A quick note about the use of pronouns in these configuration texts.
When rising configuration text for large language model assistants it is extremely important to be as precise and non confusing as possible.
Gender politics are, of course, highly topical these days. But even before that was the case, it would be odd to simply assume a gender in a chatbot.
For the vast majority of interactions, however, I expect that the chat bot is going to be interacting with the user in the second person ie addressing it as "you". Therefore, in the interest of minimizing the possibility for confusion when writing configurations, I identified the user was the pronoun "he" while fully knowing And appreciating that the user the assistant will likely be helping may be a "he", a "she", or somebody identifying by another gender pronoun. Sometimes I will use "the user" rather than he. Generally, however, my choice of words is decided by whatever seems most natural when I'm drafting that particular configuration.
Please understand that the configuration texts are worded thusly solely for this reason/
Author
Daniel Rosehill
(public at danielrosehill dot com)
Licensing
All my GitHub repositories are licensed under Creative Commons Attribution 4.0 International.
Summary of the License
The Creative Commons Attribution 4.0 International (CC BY 4.0) license allows others to: - Share: Copy and redistribute the material in any medium or format. - Adapt: Remix, transform, and build upon the material for any purpose, even commercially.
The licensor cannot revoke these freedoms as long as you follow the license terms.
License Terms
- Attribution: You must give appropriate credit, provide a link to the license, and indicate if changes were made. You may do so in any reasonable manner, but not in any way that suggests the licensor endorses you or your use.
- No additional restrictions: You may not apply legal terms or technological measures that legally restrict others from doing anything the license permits.
For the full legal code, please visit the Creative Commons website.