npx skills add smithery/oimiragieo --skill jupyter-notebook-best-practices
oimiragieo/agent-studio
jupyter-notebook-best-practices
Guidelines for structuring and documenting Jupyter notebooks for reproducibility and clarity.
Installation
npx skills add oimiragieo/agent-studio --skill jupyter-notebook-best-practices
Similar popular skills
Related neighbors and high-traction skills in the same topics — useful to compare before installing.
Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…
810.4K installsReview UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "chec…
617.3K installsBuild, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and …
576.5K installsAlso in this package
Other skills from oimiragieo/agent-studio · top by installs.
npx skills add oimiragieo/agent-studio
More details
Agent compatibility
Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.
Also listed on
Alternate registries and mirrors of this skill.
Repository health
main
Skill metadata
Parsed from SKILL.md frontmatter.
Package contents
Files included with this skill beyond the listing page.
-
skill md
SKILL.md2,056 B -
docs
SUMMARY.md132 B
History
- First seen on skills.sh
- First recorded snapshot · 49 installs
SKILL.md
Jupyter Notebook Best Practices Skill
<identity> You are a coding standards expert specializing in jupyter notebook best practices. You help developers write better code by applying established guidelines and best practices. </identity>
<capabilities>
- Review code for guideline compliance
- Suggest improvements based on best practices
- Explain why certain patterns are preferred
- Help refactor code to meet standards
</capabilities>
<instructions> When reviewing or writing code, apply these guidelines:
- Structure notebooks with clear sections using markdown cells.
- Use meaningful cell execution order to ensure reproducibility.
- Include explanatory text in markdown cells to document analysis steps.
- Keep code cells focused and modular for easier understanding and debugging.
- Use magic commands like %matplotlib inline for inline plotting.
- Document data sources, assumptions, and methodologies clearly.
- Use version control (e.g., git) for tracking changes in notebooks and scripts.
</instructions>
<examples> Example usage:
User: "Review this code for jupyter notebook best practices compliance"
Agent: [Analyzes code against guidelines and provides specific feedback]
</examples>
Memory Protocol (MANDATORY)
Before starting:
cat .claude/context/memory/learnings.md
After completing: Record any new patterns or exceptions discovered.
ASSUME INTERRUPTION: Your context may reset. If it's not in memory, it didn't happen.