Suggest an adapter
Describe an adapter you would like Jeff to have. Others upvote ideas, and the most wanted ones may be trained by the maintainers.
Missing an adapter? Describe the decision you need, and others can upvote it. The maintainers look at the most wanted ideas and may train them as official adapters, on the same recipe as the nine already on this site. There is no promise of which ideas, or when.
Where ideas go
Ideas live in the Adapter ideas category of the JeffHub GitHub Discussions. You sign in with GitHub; JeffHub stores no accounts. To support an idea that is already there, upvote it rather than posting it again. The board opens when the JeffHub repository is published.
What makes a good idea
An adapter makes one kind of decision: it picks between options you can name in advance and says how sure it is. It does not write text. When to use Jeff explains where that fits. The form asks for:
- The decision, in one or two plain sentences. For example: "Which department should handle this insurance claim?"
- The options it chooses between, or how they are made up when they change per request (such as an agent's tools).
- Two or three example inputs with the right answer. Made-up examples are fine; never post personal or confidential data.
- Where data could come from: public data sets and their licences, or how examples could be generated.
- Who would use it, and in what kind of application.
Build it yourself
If you would rather not wait, build it: start with the data guidelines, train it as in Training an adapter, and submit it. The form lets you say that you might, so others know.
