[PR #4135] Add Scientific AI Tools #58930

New Issue

GiteaMirror · 2026-06-21T12:23:22-05:00

GiteaMirror commented

2026-06-21 12:23:22 -05:00

📋 Pull Request Information

Original PR: https://github.com/sindresorhus/awesome/pull/4135
Author: @Harsh9005
Created: 5/2/2026
Status: 🔄 Open

Base: main ← Head: add-scientific-ai-tools

📝 Commits (1)

139def9 Add Scientific AI Tools

📊 Changes

1 file changed (+1 additions, -0 deletions)

View changed files

📝 readme.md (+1 -0)

📄 Description

https://github.com/Harsh9005/awesome-scientific-ai-tools#readme

This list curates AI-powered tools, MCP servers, and agent skills that support scientific research workflows — literature search, citation management, reading and comprehension, writing, data analysis, scientific computing, figure generation, drug discovery, bioinformatics, clinical trials, preprints, grants, and AI models for science. It fills a gap between domain-specific awesome lists (Healthcare, Neuroscience, Bioinformatics) and general AI lists by focusing on tools researchers actually use in their day-to-day work.

By submitting this pull request I confirm I've read and complied with the below requirements 🖖

Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.

Requirements for your pull request

Fully AI-generated pull requests are not accepted.
Don't open a Draft / WIP pull request while you work on the guidelines. A pull request should be 100% ready and should adhere to all the guidelines when you open it. Instead use #2242 for incubation visibility.
Don't waste my time. Do a good job, adhere to all the guidelines, and be responsive.
You have to review at least 4 other open pull requests.
You have read and understood the instructions for creating a list.
This pull request has a title in the format Add Name of List. It should not contain the word Awesome.
Your entry here should include a short description of the project/theme of the list. It should not describe the list itself. The first character should be uppercase and the description should end in a dot. It should be an objective description and not a tagline or marketing blurb. It should not contain the name of the list.
Your entry should be added at the bottom of the appropriate category.
The title of your entry should be title-cased and the URL to your list should end in #readme.
No blockchain-related lists.
The suggested Awesome list complies with the below requirements.

Requirements for your Awesome list

Has been around for at least 30 days.
Is not AI-generated.
Run awesome-lint on your list and fix the reported issues.
The default branch should be named main, not master.
Includes a succinct description of the project/theme at the top of the readme.
It's the result of hard work and the best I could possibly produce.
The repo name of your list should be in lowercase slug format: awesome-name-of-list.
The heading title of your list should be in title case format.
Non-generated Markdown file in a GitHub repo.
The repo should have awesome-list & awesome as GitHub topics.
Not a duplicate. Please search for existing submissions.
Only has awesome items.
Does not contain items that are unmaintained, has archived repo, deprecated, or missing docs.
Entries have a description, unless the title is descriptive enough by itself.
Includes the Awesome badge.
Has a Table of Contents section.
Has an appropriate license. (CC0 1.0)
Has contribution guidelines.
All non-important but necessary content should be grouped in a Footnotes section at the bottom of the readme.
Has consistent formatting and proper spelling/grammar.
Does not use hard-wrapping.
Does not include a CI (e.g. GitHub Actions) badge.
Does not include an Inspired by awesome-foo or Inspired by the Awesome project kinda link at the top of the readme.

Go to the top and read it again.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/sindresorhus/awesome/pull/4135 **Author:** [@Harsh9005](https://github.com/Harsh9005) **Created:** 5/2/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `add-scientific-ai-tools` --- ### 📝 Commits (1) - [`139def9`](https://github.com/sindresorhus/awesome/commit/139def999517cb861f257f5464ec091bef42aabe) Add Scientific AI Tools ### 📊 Changes **1 file changed** (+1 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `readme.md` (+1 -0) </details> ### 📄 Description **https://github.com/Harsh9005/awesome-scientific-ai-tools#readme** This list curates AI-powered tools, MCP servers, and agent skills that support scientific research workflows — literature search, citation management, reading and comprehension, writing, data analysis, scientific computing, figure generation, drug discovery, bioinformatics, clinical trials, preprints, grants, and AI models for science. It fills a gap between domain-specific awesome lists (Healthcare, Neuroscience, Bioinformatics) and general AI lists by focusing on tools researchers actually use in their day-to-day work. ### By submitting this pull request I confirm I've read and complied with the below requirements 🖖 **Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.** ## Requirements for your pull request - [x] Fully AI-generated pull requests are not accepted. - [x] Don't open a Draft / WIP pull request while you work on the guidelines. A pull request should be 100% ready and should adhere to all the guidelines when you open it. **Instead use [#2242](https://github.com/sindresorhus/awesome/issues/2242) for incubation visibility**. - [x] **Don't waste my time.** Do a good job, adhere to all the guidelines, and be responsive. - [ ] **You have to review at least 4 other [open pull requests](https://github.com/sindresorhus/awesome/pulls?q=is%3Apr+is%3Aopen).** - [x] You have read and understood the [instructions for creating a list](https://github.com/sindresorhus/awesome/blob/main/create-list.md). - [x] This pull request has a title in the format `Add Name of List`. It should not contain the word `Awesome`. - [x] Your entry here should include a short description of the project/theme of the list. **It should not describe the list itself.** The first character should be uppercase and the description should end in a dot. It should be an objective description and not a tagline or marketing blurb. It should not contain the name of the list. - [x] Your entry should be added at the bottom of the appropriate category. - [x] The title of your entry should be title-cased and the URL to your list should end in `#readme`. - [x] No blockchain-related lists. - [x] The suggested Awesome list complies with the below requirements. ## Requirements for your Awesome list - [x] **Has been around for at least 30 days.** - [x] Is not AI-generated. - [x] Run [`awesome-lint`](https://github.com/sindresorhus/awesome-lint) on your list and fix the reported issues. - [x] The default branch should be named `main`, not `master`. - [x] **Includes a succinct description of the project/theme at the top of the readme.** - [x] It's the result of hard work and the best I could possibly produce. - [x] The repo name of your list should be in lowercase slug format: `awesome-name-of-list`. - [x] The heading title of your list should be in [title case](https://capitalizemytitle.com/) format. - [x] Non-generated Markdown file in a GitHub repo. - [x] The repo should have `awesome-list` & `awesome` as [GitHub topics](https://help.github.com/articles/about-topics). - [x] Not a duplicate. Please search for existing submissions. - [x] Only has awesome items. - [x] Does not contain items that are unmaintained, has archived repo, deprecated, or missing docs. - [x] Entries have a description, unless the title is descriptive enough by itself. - [x] Includes the [Awesome badge](https://github.com/sindresorhus/awesome/blob/main/awesome.md#awesome-badge). - [x] Has a Table of Contents section. - [x] Has an appropriate license. (CC0 1.0) - [x] Has [contribution guidelines](https://github.com/sindresorhus/awesome/blob/main/awesome.md#include-contribution-guidelines). - [x] All non-important but necessary content should be grouped in a `Footnotes` section at the bottom of the readme. - [x] Has consistent formatting and proper spelling/grammar. - [x] Does not use [hard-wrapping](https://stackoverflow.com/questions/319925/difference-between-hard-wrap-and-soft-wrap). - [x] Does not include a CI (e.g. GitHub Actions) badge. - [x] Does not include an `Inspired by awesome-foo` or `Inspired by the Awesome project` kinda link at the top of the readme. **Go to the top and read it again.** --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

GiteaMirror added the pull-request label 2026-06-21 12:23:22 -05:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/awesome-sindresorhus#58930