Skip to content
Agentmart
Submit a tool

scientific-coding-style

describes how to write code to be read and validated by human scientists.

Skill by int-brain-lab

IndexedMIT★ 54
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/int-brain-lab-scientific-coding-style

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

describes how to write code to be read and validated by human scientists.

Use cases: writing, research

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/scientific-coding-style

What's inside

Skill name
scientific-coding-style
Description
describes how to write code to be read and validated by human scientists.
License
MIT
Instructions
12 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

The code you write will be read and checked by scientists, not software engineers. 

Keep it simple and short. The user will read all of the code so brevity is essential.

Avoid defensive programming, catching edge cases (try/catch) and type checking unless absolutely necessary. It is better for code to occasionally crash than to be complex. It is better to crash than to silently produce incorrect results.  

Avoid classes unless they increase clarity. Avoid clever code that is hard to read.  

**Do** use vectorization wherever possible. For speed and also brevity; scientists will find this easier to read than loops. 

 Use comments to explain the scientific reasoning behind your code.  Use descriptive variable names. Each function should have a docstring explaining what it does, what its inputs and outputs are (including array sizes), and any assumptions it makes.

From int-brain-lab/ibl-ai-agent, MIT.

More from int-brain-lab/ibl-ai-agent

Signals

Stars
54
Forks
16
Open issues
10
Last commit (this folder)
Jun 13, 2026 (4 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from int-brain-lab

Cite this page

scientific-coding-style skill. Agent Mart. https://agentmart.dev/skills/int-brain-lab-scientific-coding-style (last updated 2026-10-24)