gpsaggese/helpers / .claude/skills/notebook.format_interactive_cells
notebook.format_interactive_cells
VerifiedFormat markdown cells corresponding to interactive cells in a Jupyter notebook
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 1.6 KB |
SKILL.md
View on GitHub---
description: Format markdown cells corresponding to interactive cells in a Jupyter notebook
model: haiku
---
# Goal
- Given a Jupyter notebook, format the markdown cells that correspond to interactive
or visualization cells
- Each visualization uses a triplet: pre-visualization markdown, the code cell, and
post-visualization markdown
# Workflow
## Update the Cell Triplets
- Make the markdown cells around each interactive cell follow the triplet structure:
- **Before the visualization**: a markdown cell with the goal, then a description
cell with the plot descriptions (under each title) and widget descriptions
(close to each widget)
- **After the visualization**: a guided-usage markdown cell that explains which
experiments to run and what was learned, then the implementation cell and the
`print_obj_info()` code cell
## Sync with Jupytext
- At the end, sync the paired `.py` file with Jupytext, following
`# Code Architecture and Responsibility` -> `## Utilities vs. Notebook
Responsibilities` in `.claude/skills/notebook.rules.md`
# Conventions
- Follow the rules in `.claude/skills/notebook.rules.md`, especially:
- `## Visualization Cell Triplet Details` for the structure of pre- and
post-visualization markdown cells
- `# Visualization and Interactivity` for the interactive widget patterns
- `## Cell Triplet Structure` for the overall three-cell organization
# Constraints
- Do not change the intent of the notebook
# Verification
- [ ] Confirm each interactive cell has both a pre- and post-visualization
markdown cell
- [ ] Confirm the `.ipynb` and paired `.py` file are in sync via Jupytext
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| deprecation-and-migrationaddyosmani/agent-skillsManages deprecation and migration. Use when removing old systems, APIs, or features. Use when migrating users from one implementation to another. Use when migrating a database schema in production, such as renaming or dropping a column without downtime (expand/contract). Use when deciding whether to maintain or sunset existing code. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| performance-optimizationaddyosmani/agent-skillsOptimizes application performance across frontend, backend, queries, and databases. Use when performance requirements exist, when you suspect performance regressions, when Core Web Vitals or load times need improvement, when N+1 query patterns need fixing, or when profiling reveals bottlenecks. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| agent-cost-reportthedotmack/claude-memBelievable agent cost report for any period, default the last 7 full days PT, not counting today. Measured tokens from Claude Code transcripts priced at OpenRouter list prices (ESTIMATED), measured provider spend when a sanctioned source exists, note-taker cost separate, Timing-style HTML/PDF plus report.json, line-items.csv, evidence.json. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| agent-cost-reportthedotmack/claude-memBelievable agent cost report for any period, default the last 7 full days PT, not counting today. Measured tokens from Claude Code transcripts priced at OpenRouter list prices (ESTIMATED), measured provider spend when a sanctioned source exists, note-taker cost separate, Timing-style HTML/PDF plus report.json, line-items.csv, evidence.json. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |