My suggestion is to have a separate repo, and to add the dependencies with a requirements.txt file.
I’d like to have separate entries, in part because I want to make it easier for users to find the scripts they want, eg “oh, there’s a sugar / glycan script”
I also want to “grow the ecosystem” of plugins and I think it looks better if there are a bunch of options to download and install.
I guess at some point, having a website to search / explore the plugin list would be good too.
Okay, I have made the repo for the sugar plugin. Kindly have a look at it and do give the feedback on the same if anything needs to be changed.
Also I have sent a pr for the plugin.
Yes, do let me know if I can contribute to the same.
Also, Do you have any particular issues in mind that you think would benefit from my contributions, or should I just look for open issues that interest me?
Thank you very much!
So, do you have any other plugins in mind?..I will be happy to work on them as well.
Actually , I find myself at a point where I’m eager to contribute to the project but am facing a challenge in selecting the right issue to work on. 
I was wondering if you could suggest an issue or a set of issues that you believe would be a good fit for me or are there any issues on which I can help better.
Thanks and Sry I know its not good doubt 
One thing that would be really useful is to add images / screenshots of examples of the different option types for the script documentation, e.g.
https://two.avogadro.cc/develop/scripts/interface.html#integer-values
so Do I have to add screenshots of the Interface generated for the python scripts like this:
Yes, it would be great to have some example screenshots for the documentation.
Hello,
I have added some screenshots for the script documentation.
Kindly have a look at this.
Do let me know if any other screenshots need to be added.
Thank you!
