How does the cookbook-audit skill handle security?

It uses an automated detect-secrets script to scan notebooks for hardcoded API keys and credentials, checking them against a defined baseline.

Does this skill work directly with .ipynb files?

Yes, it processes .ipynb files by converting them into markdown in a temporary folder, which allows for a cleaner review without the noise of raw JSON or large outputs.

What dimensions are included in the audit scoring?

The skill evaluates four main dimensions: Narrative Quality, Code Quality, Technical Accuracy, and Actionability & Understanding, each scored out of 5.

What are TLOs and ELOs in this context?

Terminal Learning Objectives (TLOs) and Enabling Learning Objectives (ELOs) are specific, action-oriented goals that ensure the notebook provides clear value to the reader.

Cookbook Auditor

Name: Cookbook Auditor
Author: Activer007

byActiver007

•

Learning & Documentation

Audits and optimizes Jupyter notebooks against Anthropic’s style guidelines and technical best practices.

About

The cookbook-audit skill provides a systematic framework for reviewing technical notebooks to ensure they meet high standards of educational value and technical accuracy. It guides users through an automated and manual review process—scanning for hardcoded secrets, evaluating narrative flow, and verifying code quality—culminating in a detailed scoring report with prioritized recommendations for improvement. This skill is essential for developers and technical writers who want to create high-quality, problem-focused documentation that follows the Diataxis framework.

Key Features

Enforcement of Terminal and Enabling Learning Objectives (TLOs/ELOs)
Standardized scoring across narrative, code, and technical dimensions
Structured reporting with executive summaries and prioritized action items
1 GitHub stars
Automated secret detection and technical notebook validation
Markdown-based review process for cleaner context management

Use Cases

Auditing open-source contributions to ensure they meet style guide requirements
Scanning notebooks for security vulnerabilities like hardcoded API keys
Reviewing technical documentation for educational clarity and narrative flow

About

Key Features

Enforcement of Terminal and Enabling Learning Objectives (TLOs/ELOs)
Standardized scoring across narrative, code, and technical dimensions
Structured reporting with executive summaries and prioritized action items
1 GitHub stars
Automated secret detection and technical notebook validation
Markdown-based review process for cleaner context management

Use Cases

Auditing open-source contributions to ensure they meet style guide requirements
Scanning notebooks for security vulnerabilities like hardcoded API keys
Reviewing technical documentation for educational clarity and narrative flow