scientific-runtime
Skill585 starsChanged 3 months agoMITView on GitHub
Use when serving scientific CLI tasks through ScholarAIO, especially when the agent should prefer scholaraio toolref, handle partial coverage safely, or avoid turning user work into documentation maintenance.
In this repository47 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/scholaraio.mdcCursor rule
- academic-writingSkill
- arxivSkill
- auditSkill
- backupSkill
- bioinformaticsSkill
- citation-checkSkill
- citationsSkill
- documentSkill
- drawSkill
- enrichSkill
- exploreSkill
- exportSkill
- graphSkill
- gromacsSkill
- importSkill
- indexSkill
- ingestSkill
- insightsSkill
- lammpsSkill
- literature-reviewSkill
- metricsSkill
- nature-workflowSkill
- openfoamSkill
- paper-guided-readingSkill
- paper-writingSkill
- patent-fetchSkill
- patent-searchSkill
- posterSkill
- publishSkill
- quantum-espressoSkill
- renameSkill
- research-gapSkill
- review-responseSkill
- scientific-tool-onboardingSkill
- scrubSkill
- searchSkill
- setupSkill
- showSkill
- technical-reportSkill
- topicsSkill
- translateSkill
- workspaceSkill
- writing-polishSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
16 rules. About 0 are common, 12 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈12
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 13
Use it alongside a tool-specific scientific skill such as:
- Distinctive: line 44
Use the tool-specific skill for workflow and scientific norms.
- Very specific: line 45
Use toolref first for commands, parameters, program pages, and option meanings.
- Very specific: line 46
If toolref is sufficient, continue normally.
- Very specific: line 47
If toolref is partial, fall back to official docs and continue the task.
- Distinctive: line 49
Do not turn the current user task into documentation maintenance work.
- Distinctive: line 72
Before writing configuration or scripts, first resolve:
- Very specific: line 80
If toolref does not fully answer the question:
- Distinctive: line 84
do not ask the user to stop and repair the docs layer first
- Distinctive: line 85
do not expose internal refactor details unless they materially affect current behavior
- Distinctive: line 100
If it is a one-off edge case, do not derail the user task.
- Distinctive: line 108
When code changes are involved:
- Distinctive: line 111
treat package-internal reorganizations as an implementation detail
- Distinctive: line 112
if a refactor changes behavior visible through CLI or top-level imports, treat that as a regression until proven otherwise
- Distinctive: line 126
When answering the user:
- Distinctive: line 128
keep maintenance details short
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Scientific Runtime Protocol
This is a shared runtime skill for scientific CLI work.
It is not a tool manual. It tells the agent how to behave when serving real users on scientific tool tasks.
Use it alongside a tool-specific scientific skill such as:
quantum-espressolammpsgromacsopenfoambioinformatics
Core Principle
ScholarAIO is for users, not for people who want to co-maintain the internal documentation layer.
So the agent should absorb complexity whenever possible.
The user should experience:
- natural language help
- reliable parameter lookup
- graceful fallback when coverage is partial
The user should not experience:
- being asked to manually patch
toolref - being forced to learn internal parser gaps
- being blocked because a documentation layer is imperfect
Runtime Protocol
For any scientific CLI task:
- Identify the scientific tool or sub-tool that matches the problem.
- Use the tool-specific skill for workflow and scientific norms.
- Use
toolreffirst for commands, parameters, program pages, and option meanings. - If
toolrefis sufficient, continue normally. - If
toolrefis partial, fall back to official docs and continue the task. - Mention the coverage gap briefly only when it affects confidence or maintainability.
- Do not turn the current user task into documentation maintenance work.
Toolref-First Behavior
The agent should prefer:
scholaraio toolref show <tool> ...for precise lookupsscholaraio toolref search <tool> "..."for natural-language entry
The stable public surfaces are:
- the
scholaraio toolref ...CLI - the top-level
scholaraio.stores.toolrefpackage facade
The agent should not route users through internal implementation modules such as:
scholaraio.stores.toolref.fetchscholaraio.stores.toolref.manifestscholaraio.stores.toolref.storagescholaraio.stores.toolref.search
Those internal module boundaries may change during refactors. User-facing guidance should stay anchored to the CLI and the top-level package behavior.
Before writing configuration or scripts, first resolve:
- which program or subcommand is relevant
- which parameters are high-risk
- which defaults or restrictions matter for validity
When Toolref Is Incomplete
If toolref does not fully answer the question:
- continue using the official documentation source
- clearly separate "task progress" from "maintenance opportunity"
- do not ask the user to stop and repair the docs layer first
- do not expose internal refactor details unless they materially affect current behavior
Use this pattern:
- "I used
toolreffor the main entry point." - "For this deeper detail, I fell back to the official docs because current coverage is partial."
Escalation Rule
Escalate a gap to onboarding or maintenance only when:
- the same gap appears repeatedly
- it blocks a common task
- it affects correctness, not just convenience
If it is a one-off edge case, do not derail the user task.
Separation Of Responsibilities
- tool-specific skill: when to use the tool, workflow, scientific norms
toolref: interface and parameter reference- scientific runtime: how to behave under uncertainty or partial coverage
When code changes are involved:
- preserve the public
scholaraio.stores.toolrefentry surface - treat package-internal reorganizations as an implementation detail
- if a refactor changes behavior visible through CLI or top-level imports, treat that as a regression until proven otherwise
Anti-Patterns
Do not:
- dump raw flags from memory
- tell the user to "go improve toolref first"
- confuse a successful CLI run with a valid scientific result
- replace scientific judgment with parameter lookup alone
- instruct the user to use internal module names as if they were the supported interface
Output Style
When answering the user:
- keep maintenance details short
- foreground scientific progress and decision-making
- mention fallback only when it materially changes confidence or provenance
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

