Skip to content

Contribute

Everything on this site is maintained in a public GitHub repository. Anyone can contribute. The first recipes come from one centre, so examples and errors from other groups are the most useful input the site gets.

Ways to contribute

Add an example

You used a recipe in your group. Say what you did, how you checked the output, and what worked or did not. An example from a second group changes a recipe's status from tried to reproduced. Add an example

Report an error

An agent made an error that others should know about. Say what happened, how it was found, and what would have prevented it. Names and details are removed by default. Report an error

Contribute a skill

There are two kinds of skill contribution.

  • A local version of an existing brief. You built a skill from one of the briefs and it works at your institute. Share a link, and it is listed on the skill's page as an example for others.
  • A new brief. You have a skill that others could use. Write it as a brief: the general steps, and the questions only a local user can answer. What a brief contains lists the sections. Remove internal paths, names, credentials and institute forms.

Submit a skill

Propose a recipe

You give a task to an agent and the results hold up. Describe the steps, how you check the output, and what went wrong. Propose a recipe

Disagree with a recipe

A recipe does not work in your setting. Say where and why. Cases where a recipe failed carry the most weight. Disagree with a recipe

Discuss

Each recipe and each skill has a discussion thread at the bottom of its page. For anything open-ended, use GitHub Discussions.

No GitHub account?

Write to the AI for Science Google Group at aiforscience@googlegroups.com, and start the subject with "aiforscientists". The group is shared with aiforscience.eu. The editors carry what you send into the site, with attribution unless you ask otherwise.

Edit directly

Every page has an edit button that opens a pull request. CONTRIBUTING.md covers working in the repository: the checks to run, the branch convention, and the licence your contribution carries.

Writing rules

  • Short, plain sentences.
  • Every result states the conditions under which it worked.
  • Every recipe states how its output is checked.
  • Names and details are removed from examples unless the contributor asks to be named.
  • No advice on getting around institutional rules or model restrictions.

What happens next

The editors review contributions in public, on the issue or pull request. New recipes start as draft. See How recipes work for the status levels, and Editors and review for who decides.

Code of conduct

Everyone taking part is covered by the code of conduct.