plugin discoverability is bad
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 12.5k
- Forks
- 991
- Avg merge
- 3d 13h
- Merged PRs (30d)
- 10
Description
while there's the docs page, beyond that it's really the wild west out here - today I searched github for "llm install -e '.[test]'". Lots of other unrelated projects come up if you search pypi and github in most sensible-seeming ways (ie "llm-"). examples of things i wish i knew about earlier include llm-cmds which is an active fork the author hasnt published elsewhere for whatever reason, and llm-jupyter. They dont all make PRs here either. half of Simon's repos are data scraping, surely this is doable.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the existing docs page and the examples named in the issue, including llm-cmds and llm-jupyter. Define an inventory of relevant plugins and how it should stay current; done means users can discover these projects without relying on broad GitHub or PyPI searches.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100