Why this matters
Science needs shareable method layers, not just isolated tool use.
Operational knowledge is still too private
Valuable work often depends on tacit prompts, undocumented shell history, and fragile habits that do not survive handoff across people, labs, or time.
Powerful scientific tools remain hard to operationalize
APIs, command-line programs, and data resources are often strong in capability but weak in day-to-day transferability. The missing layer is frequently method packaging rather than new algorithms.
Reusable skills can turn one-off routines into infrastructure
A published skill can preserve exact commands, references, output expectations, and safety constraints while making a workflow easier to invoke and easier to teach.
Platform Structure
Scientific Tooling now separates platform identity from project identity.
1
Organization
Scientific Tooling serves as the umbrella brand and public-facing site.
2
Repository
Structured Intelligence is the flagship repository and active implementation surface.
3
Manuscripts
Formal web editions translate reusable workflows into scientific prose.
4
Reuse
Researchers can inspect, rerun, critique, and extend the operational layer.
The point of this structure is clarity. The domain and organization describe the broader initiative; the project path identifies the current flagship implementation.
Current Projects
Start with the flagship repository, then move into manuscripts and artifacts.
Flagship Repository
Structured Intelligence
A repository for skill-based scientific tooling: reusable local skills, scripts, manuscripts, and validation logic designed for AI-assisted scientific work that remains inspectable.
- NCBI E-utilities workflows for PubMed retrieval and briefing
- Standalone RPS-BLAST and CDD annotation orchestration
- Plain-text assets for Codex and Claude Code environments
skills/
manuscripts/
validation scripts
Publication Layer
Structured Intelligence Manuscript Series
Publication-style web pages that explain why the workflows matter, where operational barriers exist, and how an independent AI interface layer can improve reuse without hiding the original method.
- Web editions for NCBI E-utilities and RPS-BLAST workflows
- Availability, limitations, and positioning written for scientists
- Markdown sources preserved for citation and revision
web manuscripts
markdown source
availability notes
Publishing Model
The platform is meant to host reusable scientific practice, not just describe it.
What gets published
Skills, scripts, references, manuscripts, validation rules, and reproducible output expectations. The goal is to make scientific operations public enough to inspect and teach.
What remains explicit
This is an independent, unofficial AI interaction layer around upstream tools and services. It does not replace original software, databases, or expert judgment, and it does not imply endorsement.
Organization
Scientific Tooling is now the public-facing layer for the work.
The domain and organization name are meant to support a broader initiative. Structured Intelligence remains the current flagship repository, but the site structure now leaves room for additional projects, manuscript collections, and reusable workflow assets over time.
The broader initiative adds an independent AI interface layer around existing scientific tools and services. It does not claim ownership of upstream software, databases, or documentation, and it does not imply endorsement by the original authors or institutions.