skills.rest
seangalliher
seangalliherCOMMUNITY
Explore all skills by this author →
GitHub

notebook-quality

Enforce conclusion-first notebook entries with explicit evidence linkage in Ship's Records.

11|3|Updated Mar 7, 2026
Search Tags:#analysis#structure#data-analysis#notebook#temporal-threading
One-click install
npx skills add https://github.com/seangalliher/ProbOS --skill notebook-quality
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: notebook-quality
Source: https://github.com/seangalliher/ProbOS/tree/main/config/skills/notebook-quality
Command: npx skills add https://github.com/seangalliher/ProbOS --skill notebook-quality

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Notebook entries in Ship's Records sometimes become data dumps rather than analytical artifacts. This guide establishes a structured, conclusion-first approach that ensures entries present clear conclusions, supporting evidence, and actionable implications.

Core Features & Use Cases

  • Enforces conclusion-first structure: a concise conclusion followed by evidence and reasoning.
  • Promotes temporal threading and longitudinal analysis across cycles and topics.
  • Distinguishes data from analysis and encourages synthesis for decision-making.
  • Proficiency progression with Ward Room differentiation and cross-topic synthesis.

Quick Start

Write a notebook entry that starts with a concise conclusion, then presents evidence, implications, and next steps.

Frequently Asked Questions about notebook-quality

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure notebook entries for rigorous data analysis?▼

Temporal threading connects notebook entries across cycles and topics to support longitudinal analysis. It distinguishes isolated data dumps from continuous analytical artifacts, enabling cross-cycle synthesis for ongoing project decision-making.

What's the best way to separate data from analysis in research notebooks?▼

The best way to separate data from analysis is enforcing a conclusion-first structure. Start with the analytical conclusion, then present supporting evidence and reasoning, ensuring raw data does not become an unstructured data dump.

How do I write a conclusion-first notebook entry?▼

To write a conclusion-first notebook entry, start with a concise conclusion, then present supporting evidence, discuss implications, and outline actionable next steps to guide structured reasoning and decision-making.

Can I use a conclusion-first structure for longitudinal project analysis?▼

Yes, a conclusion-first structure supports longitudinal project analysis by enabling temporal threading. It applies across ongoing project cycles to facilitate cross-cycle synthesis and topic-level analysis over time.

Why does my notebook entry look like a data dump instead of an analytical artifact?▼

Notebook entries become data dumps when they lack a conclusion-first structure. Without explicit evidence linkage and separated data-vs-analysis sections, entries fail to provide actionable insights for decision-making.

Related Skills

Explore More Education & Research Skills→
petrSimonidesXartpetrSimonidesXart

approach-evaluation

Evaluate technical approaches against project constraints with documented evidence.

Community
Advanced
malloydatamalloydata
95

notebook-chat

Execute ad-hoc data queries on in-memory notebook contexts.

Official
Advanced
l3ochol3ocho

analytical-chart-selection

Map analytical questions to Plotly graph_objects trace types.

Community
Advanced
MattVOLTAMattVOLTA
4

log

Record project events and session outcomes to Supabase and log.md.

Community
Intermediate