Add author and notebook registry for cookbooks #237
Conversation
Model Check Results✅ No model references found in changed files This PR adds author and notebook registry infrastructure files (schemas, templates, and YAML configs). None of the changed files contain Claude model references, so there are no model validation issues to report. Changed Files Reviewed:
Summary:All changed files are metadata and configuration files with no Claude API model usage. The PR is clear from a model validation perspective. |
Summary
Errors per inputErrors in README.md
Errors in skills/CLAUDE.md
Errors in skills/README.md
Errors in temp_md/00_The_one_liner_research_agent.md
Errors in temp_md/01_skills_introduction.md
Errors in temp_md/01_The_chief_of_staff_agent.md
Errors in temp_md/02_skills_financial_applications.md
Errors in temp_md/02_The_observability_agent.md
Errors in temp_md/03_skills_custom_development.md
Errors in temp_md/claude_3_rag_agent.md
Errors in temp_md/extended_thinking.md
Errors in temp_md/extended_thinking_with_tool_use.md
Errors in temp_md/extracting_structured_json.md
Errors in temp_md/finetuning_on_bedrock.md
Errors in temp_md/getting_started_with_vision.md
Errors in temp_md/guide.md
Errors in temp_md/memory_cookbook.md
Errors in temp_md/pdf_upload_summarization.md
Errors in temp_md/prerecorded_audio.md
Errors in temp_md/rag_using_mongodb.md
Errors in temp_md/rag_using_pinecone.md
Errors in temp_md/tool_choice.md
Errors in temp_md/usage_cost_api.md
Errors in temp_md/using_citations.md
Errors in temp_md/using_llm_api.md
Errors in temp_md/wikipedia-search-cookbook.md
|
Model Check Results ✅I've reviewed the changed files in this pull request for Claude model usage. SummaryNo model references found in changed files - All clear! ✅ Changed Files Analyzed
FindingsThe changed files in this PR are schema definitions and configuration files that do not contain any Claude model references. These files define:
No action required - This PR does not introduce any model references that need validation. Automated model check based on Claude Models documentation |
2cb79fb to
a762c94
Compare
Model Usage Review - ✅ PASSEDI've reviewed all model references in this PR against the current public models list from the Claude documentation. Summary✅ All model references are valid and use current public models Model References FoundThe PR uses the following valid model identifiers:
Best Practices Observed✅ Excellent use of model aliases: The PR consistently uses aliases ending in version numbers (e.g., ✅ Consistent model selection: Appropriate model choices for different use cases:
✅ Environment variable pattern: Uses environment variables for model configuration (e.g., RecommendationNo changes needed. This PR demonstrates excellent model usage practices by using current public model aliases consistently throughout the codebase. Generated by /model-check slash command |
Add JSON schemas and YAML configurations for managing cookbook metadata and author information. This includes: - authors_schema.json: Schema for mapping GitHub usernames to author details - registry_schema.json: Schema for cookbook metadata with required fields (title, path, slug, category, github_url, authors, date) - authors.yml: Initial author mappings with Anthropic and contributors - registry.yaml: Comprehensive cookbook registry with 70+ entries across multiple categories (capabilities, patterns, tools, multimodal, etc.)
a762c94 to
295d9cd
Compare
Update schema validation to require `categories` array instead of single `category` string. Add `archived` boolean field for cookbook status tracking. Add GitHub Actions workflow to verify author URLs on pull requests and pushes. Normalize multi-line descriptions in registry entries.
- Create `.github/scripts/verify_authors.py` with additional checks - Verify GitHub handles exist and are valid - Check website and avatar URLs are accessible - Validate all registry.yaml authors are defined in authors.yaml - Update workflow to trigger on both authors.yaml and registry.yaml changes - Fix GitHub handle in authors.yaml (john-vajda → jpvajda, richmond-alake → RichmondAlake) - Standardize registry.yaml categories and fix typo (Aesthethics → Aesthetics)
…alidation Add path existence verification to the registry validation script. Add command-line interface to run specific validations. Update registry.yaml paths to match actual directory structure.
Add schema validation to the verification script using jsonschema library. Constrain registry categories to a predefined enum list. Update CI workflow to install jsonschema dependency.
| "type": "array", | ||
| "items": { | ||
| "type": "string", | ||
| "enum": [ |
There was a problem hiding this comment.
@elie there are the categories I came up with, let me know if you think there's others we should add!
There was a problem hiding this comment.
Let's call it Multimodal instead of Images so that we can future proof.
Do you imagine "Tools" being tool use specific? Or more like "Capabilities"
There was a problem hiding this comment.
Good catch, updated.
Tools was really just the tools feature.

All the 'capabilities' notebooks I have under RAG & Retrieval currently, that seemed to be closer to what a user might search. I found it hard to think of anything that wouldn't fall under a 'capability' especially now that there's multiple selections possible.
This adds the author/notebook registry for cookbooks as well as a PR template and yaml specs.