Automated summary
This skill fixes errors encountered during notebook execution by editing either the notebook cells or the underlying library source code.
Strengths
- Thorough analysis of the traceback to identify the root cause
- Direct fixes in notebook JSON cells or Python source files
- Verification by re-running the notebook to ensure no regressions
Limitations
- Requires understanding of both notebook and source code
- Cannot resolve environment or external dependency issues
- Limited to Python notebooks using an internal package
Use when a notebook fails due to logic errors, missing imports, or bugs in the associated source code.
Avoid when the error stems from environment issues (package versions, missing dependencies) or external data problems that cannot be fixed by code changes.
Security analysis
SafeThe skill instructs on analyzing errors and editing notebook cells or source code; it does not execute any dangerous commands, exfiltrate data, or bypass security.
No concerns found
How this analysis is madeExamples
This notebook cell failed with NameError: name 'np' is not defined. Fix the notebook by adding the missing import.The notebook error is caused by a bug in the `process_data` function in `gwexpy/utils.py`. Traceback shows IndexError. Fix the source code.The notebook cell fails with TypeError: cannot concatenate str and int. Identify the issue in the cell and fix it.name: fix_notebook description: ノートブックのエラーを、そのノートブック自体の修正またはソースコードの修正により解決する
Fix Notebook Errors
This skill handles fixing errors encountered during notebook execution.
Instructions
-
Analyze the Failure:
- Examine the traceback to determine if the error is in the notebook cell's logic or the underlying library.
-
Strategy A: Fix Notebook (Local):
- If the usage is wrong or imports are missing, edit the
.ipynbcells. - Modify the
"source"field of the failing code cell in the notebook JSON.
- If the usage is wrong or imports are missing, edit the
-
Strategy B: Fix Source Code:
- If the bug is in the
gwexpy/package, trace it to the source file. - Apply the fix to the Python source while ensuring no regressions.
- If the bug is in the
-
Verification:
- Re-run the notebook to confirm it passes.
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/fix-notebook-errors-mmh8qrfy/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/fix-notebook-errors-mmh8qrfy' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/fix-notebook-errors-mmh8qrfy/download' --output '.skill-downloads/fix-notebook-errors-mmh8qrfy/SKILL.md.part' && mv '.skill-downloads/fix-notebook-errors-mmh8qrfy/SKILL.md.part' '.skill-downloads/fix-notebook-errors-mmh8qrfy/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
This file does not provide a usable name/description header for this native procedure. It remains available to download and inspect; use the manual method below.
Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/fix-notebook-errors-mmh8qrfy/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.