Open a terminal, cd into an empty directory, and launch Scidekick:
mkdir iris-research && cd iris-research
skπΈ Screenshot 0: The Scidekick welcome screen / initial prompt.
Scidekick ships with a scientific wiki β a structured knowledge base with five entity types:
paper, hypothesis, experiment, evidence, insight.
Every research project starts here. The wiki enforces scientific rigor by linking hypotheses
to experiments and experiments to evidence.
sk wiki ingest --type hypothesis --title "Iris species are linearly separable"
Or, interactively:
Create a hypothesis in the wiki: "Iris species are linearly separable."
What happens: Scidekick creates a wiki entry with YAML frontmatter, a hypothesis ID, and cross-reference slots for experiments and evidence.
πΈ Screenshot 1: The
sk wiki ingestoutput showing the created hypothesis entry.
sk wiki ingest --type experiment --title "Iris exploratory data analysis" \
--hypothesis "Iris species are linearly separable"
Or, interactively:
Link an experiment titled "Iris exploratory data analysis" to the hypothesis "Iris species are linearly separable" in the wiki.
πΈ Screenshot 2: The experiment entry linked to the hypothesis.
sk wiki list
sk wiki show --title "Iris species are linearly separable"
πΈ Screenshot 3:
sk wiki showoutput with the full linked entry.
Key feature highlighted: The wiki is the source of truth that persists across your entire session. It's not a conversation log β it's a structured research artifact.
Or, interactively:
Show me all wiki entries related to Iris species separability.
Scidekick extends the base agent with installable skills β each is a domain-specialized mini-agent with its own tools, prompts, and validation metadata. Skills are loaded on demand and compose naturally.
Load the Iris dataset from sklearn and run an exploratory data analysis.
What happens: Scidekick detects the need for data analysis, loads the
exploratory-data-analysis skill automatically, and produces a structured
EDA report covering distributions, correlations, outliers, and quality metrics.
πΈ Screenshot 4: The EDA report with pairplots, correlation heatmaps, and per-feature statistics.
Based on the EDA, formulate a testable scientific hypothesis about Iris species separability.
What happens: Scidekick loads the hypothesis-generation skill. This skill follows the
scientific method framework β it doesn't just guess; it structures the hypothesis with
predictions, proposed mechanisms, and experimental design.
πΈ Screenshot 5: The structured hypothesis output with prediction, mechanism, and experimental design sections.
sk wiki ingest --type hypothesis --title "Petal dimensions alone discriminate Iris species" \
--prediction "A logistic regression on petal length and width achieves >95% accuracy"
Or, interactively:
Add the hypothesis we just formulated β "Petal dimensions alone discriminate Iris species" β to the wiki, with the prediction that logistic regression on petal length and width achieves >95% accuracy.
πΈ Screenshot 6: The wiki now has two linked hypotheses.
Scidekick has a meta-skill for publication-ready figures: scientific-visualization.
It orchestrates matplotlib/seaborn/plotly with journal-specific styling and colorblind-safe palettes.
Create a publication-quality multi-panel figure showing:
(1) petal length vs petal width colored by species with decision boundaries,
(2) feature importance from a trained classifier.
Use Nature journal styling and a colorblind-safe palette.
πΈ Screenshot 7: The generated figure with multi-panel layout, significance annotations, and Nature styling.
Key feature highlighted: The meta-skill composes lower-level skills (matplotlib, seaborn) with domain knowledge (journal requirements, accessibility standards). The user specifies what they want, not how to draw it.
Scidekick's scikit-learn skill provides comprehensive reference documentation and
best-practice patterns for ML workflows.
Train a logistic regression classifier on petal length and width to predict Iris species.
Use stratified 5-fold cross-validation, report per-class precision/recall/F1,
and produce a confusion matrix.
πΈ Screenshot 8: The training output with cross-validation scores, classification report, and confusion matrix.
Now train a KNN classifier on the same features and compare its cross-validation
performance to the logistic regression. Which model generalizes better?
πΈ Screenshot 9: Side-by-side comparison of both models.
Scidekick's statistical-analysis skill guides test selection, checks assumptions,
and produces APA-formatted results β removing the guesswork from statistical reporting.
Run a formal statistical comparison of the two classifiers' cross-validation scores.
Check assumptions and report in APA format.
πΈ Screenshot 10: APA-formatted statistical report (e.g., paired t-test or McNemar's test) with assumption checks.
This is where Scidekick diverges from a generic coding assistant. The wiki closes the loop: hypotheses β experiments β evidence β insights.
sk wiki ingest --type evidence --title "Logistic regression outperforms KNN on Iris" \
--experiment "Iris exploratory data analysis" \
--finding <You fill the results here>
πΈ Screenshot 11: The evidence entry linking back to the experiment and hypothesis.
Or, interactively:
Record evidence in the wiki. Link it to the "Iris exploratory data analysis" experiment.
sk wiki ingest --type insight --title "Linear separability for Iris" \
--hypothesis "Petal dimensions alone discriminate Iris species" \
--hypothesis "Iris species are linearly separable" \
--evidence "Logistic regression outperforms KNN on Iris"
πΈ Screenshot 12: The insight connecting multiple hypotheses and evidence.
Or, interactively:
Synthesize an insight in the wiki about the linear separability for Iris. Connect it to both hypotheses and the logistic-regression-vs-KNN evidence.
sk wiki query --type insight
sk wiki show --title "Linear separability confirmed for Iris"
πΈ Screenshot 13: The insight entry showing all linked hypotheses, experiments, and evidence β the complete research trail.
Key feature highlighted: The wiki creates a permanent, queryable research graph. Six months later, another agent (or another researcher) can trace the full chain of reasoning.
Or, interactively:
Show me the full research graph for the Iris project β all hypotheses, experiments, evidence, and insights linked together.
Scidekick connects your research to the broader scientific literature.
Search for papers about Iris dataset classification benchmarks and
compare their reported accuracies to our results.
What happens: Scidekick loads the paper-lookup skill, queries multiple academic
databases (arXiv, Semantic Scholar, PubMed, Crossref), and returns structured results.
πΈ Screenshot 14: Paper search results with accuracy benchmarks from the literature.
Evaluate the evidence quality of our finding against the literature.
Are there confounders we missed? Would our result replicate?
What happens: Scidekick loads scientific-critical-thinking, applies evidence-grading
frameworks (e.g., GRADE), and identifies potential confounders.
πΈ Screenshot 15: Critical evaluation output with confounder analysis and replication assessment.
Write a Methods section describing our Iris classification experiment
in IMRAD format with proper statistical reporting (APA style).
πΈ Screenshot 16: The generated Methods section with proper scientific prose.
Generate BibTeX citations for all papers we referenced.
What happens: Scidekick loads citation-management, validates each citation
against CrossRef/DOI resolution, and outputs clean BibTeX.
πΈ Screenshot 17: Verified BibTeX output.
Scidekick supports three experiment modes:
- Loop mode:
propose β test β measurecycles. The agent iterates autonomously. - Pipeline mode: fixed multi-step workflows. You define the stages; Scidekick executes them in order.
- Team mode: self-organizing agent teams. Multiple agents collaborate on sub-tasks.
sk experiment loop --hypothesis "Petal dimensions alone discriminate Iris species" \
--max-iterations 3
What happens: Scidekick enters a tight loop β it proposes an analysis, runs it, measures the result, and decides whether to iterate or conclude.
πΈ Screenshot 18: Loop mode output showing iteration 1, 2, and the convergence decision.
Or, interactively:
Run an experiment loop: test the hypothesis "Petal dimensions alone discriminate Iris species" with up to 3 iterations.
| Scidekick Feature | Demonstrated In | Why It Matters |
|---|---|---|
| Scientific Wiki | Steps 1β3, 6, 11β13 | Persistent, structured research artifacts β not a chat log |
| Skill ecosystem | Steps 4β5, 7β10, 14β17 | Domain-specialized mini-agents that compose naturally |
| Skill auto-loading | Steps 4, 5, 14, 15 | No manual skill selection β the harness detects intent |
| Scientific visualization | Step 7 | Publication-ready figures with journal styling |
| Statistical rigor | Step 10 | Test selection, assumption checks, APA reporting |
| Literature grounding | Steps 14β15 | Connects your work to the broader scientific record |
| Citation management | Steps 16β17 | Verified, validated BibTeX β no hallucinated references |
| Experiment modes | Step 18 | Autonomous iteration for hypothesis-driven research |
| Evidence graph | Steps 11β13 | Full traceability: hypothesis β experiment β evidence β insight |
| Critical thinking | Step 15 | Evidence grading frameworks catch confounders before peer review does |
- Each step is a prompt you type into Scidekick.
- πΈ markers indicate screenshot opportunities.
- The tutorial is self-contained β no pre-existing files or setup beyond
skitself. - Expected runtime: ~20 minutes end-to-end.
- If a skill isn't installed, Scidekick will prompt you:
sk install-skillsinstalls everything.


















