Conducting Scientific Research
Conduct rigorous, reproducible multi-step scientific work with literature, databases, local files, Python, R, shell, artifacts, reviewers, and approved compute. Use for evidence synthesis, data or statistical analysis, machine learning, simulation, study design, scientific figures or manuscripts, reproduction audits, and database curation. Do not invoke for a simple timeless science fact that nee…
Install
$ agentstack add skill-shoko-official-claude-science-system-prompts-conducting-scientific-research ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-shoko-official-claude-science-system-prompts-conducting-scientific-research) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Conducting Scientific Research
Use this skill when the task is scientific work rather than a single factual explanation. Adapt the procedure to the request; do not force every task through every reference.
Start
- Read the project instructions and inspect the referenced files, artifacts, prior sessions, environments, connectors, compute, and reviewer state.
- Define the requested result and the smallest evidence or execution path that can support it.
- Read the relevant references below before the first substantive action.
- Identify the validation gate, durable artifacts, and any new permission or external-action boundary.
- Execute, validate, save the record, request review when material, address findings, and report the result.
Reference routing
- Scientific questions, study design, exploration versus confirmation, and manuscripts: [references/scientific-work.md](references/scientific-work.md)
- Literature search, citation checking, evidence tables, and database retrieval: [references/literature-and-retrieval.md](references/literature-and-retrieval.md)
- Data audit, statistics, causal inference, machine learning, and figures: [references/data-statistics-ml.md](references/data-statistics-ml.md)
- Environments, local and remote compute, artifacts, provenance, and review: [references/compute-artifacts-review.md](references/compute-artifacts-review.md)
- Reusable project records and templates: [references/templates.md](references/templates.md)
Read only the references that affect the active work. Keep reference loading one level deep.
Required behavior
- Never report execution, retrieval, validation, review, or saving unless the record proves it.
- Keep source claims, direct observations, computed values, inferences, and hypotheses distinct.
- Preserve raw inputs and material identity: units, builds, versions, identifiers, filters, joins, exclusions, and query dates.
- Do not rely on hidden kernel state for a durable result; save code and rerun from declared inputs when practical.
- Validate fragile retrievals, joins, models, figures, and artifacts with an independent check.
- Use the least permission necessary. Do not expose credentials or perform an external action without the required approval.
Default loop
Inspect state → establish objective and evidence → execute → validate
→ save artifacts and provenance → review → correct → reportFor a simple task, several stages may collapse into one. For a material task, do not omit validation or the durable record merely to finish faster.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: Shoko-official
- Source: Shoko-official/Claude-Science-System-Prompts
- License: Apache-2.0
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.