Skip to content

Commit 0286da4

Browse files
PedramNavidclaude
andcommitted
Add /add-registry slash command and new cookbook entries
- Add Claude Code slash command to help contributors add notebooks to registry.yaml - Update PR template with checklist item for registry entries - Add new cookbook entries: crop tool, programmatic tool calling, tool search, automatic context compaction, ElevenLabs voice assistant 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <[email protected]>
1 parent 3c6d5f3 commit 0286da4

File tree

3 files changed

+120
-0
lines changed

3 files changed

+120
-0
lines changed

.claude/commands/add-registry.md

Lines changed: 72 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,72 @@
1+
---
2+
allowed-tools: Read,Glob,Grep,Edit
3+
description: Add a new notebook to registry.yaml
4+
---
5+
6+
Add a new entry to `registry.yaml` for the notebook specified in the prompt above.
7+
8+
## Instructions
9+
10+
1. **Read the notebook** at the specified path to understand its content
11+
2. **Check author exists** in `authors.yaml`:
12+
- Ask the user for the GitHub username of the notebook author
13+
- Read `authors.yaml` and check if that username exists as a key
14+
- If the author does NOT exist, ask the user for their details and add them to `authors.yaml`:
15+
- **name**: Full display name
16+
- **website**: GitHub profile URL or personal website
17+
- **avatar**: Use `https://github.com/<username>.png` as default
18+
3. **Generate the registry entry** with these fields:
19+
20+
### Required Fields
21+
- **title**: Extract from the notebook's first heading or create a concise, descriptive title
22+
- **description**: Write a brief 1-2 sentence description summarizing what the notebook teaches
23+
- **path**: The notebook path relative to the repository root
24+
- **authors**: Use the GitHub username from step 2
25+
- **date**: Use today's date in YYYY-MM-DD format
26+
- **categories**: Select 1-2 appropriate categories from this list:
27+
- Agent Patterns
28+
- Claude Agent SDK
29+
- Evals
30+
- Fine-Tuning
31+
- Multimodal
32+
- Integrations
33+
- Observability
34+
- RAG & Retrieval
35+
- Responses
36+
- Skills
37+
- Thinking
38+
- Tools
39+
40+
### Style Guidelines
41+
- Title should be concise but descriptive (see existing entries for examples)
42+
- Description should be ~15-20 words, focusing on what the user will learn/build
43+
- Choose categories that best match the notebook's primary focus
44+
45+
## Output
46+
47+
1. If author is new, show the proposed `authors.yaml` entry for review and add it after approval
48+
2. Show the user the proposed `registry.yaml` entry for review
49+
3. After user approval, use the Edit tool to append the entry to `registry.yaml`
50+
4. Maintain alphabetical ordering by path within the file, or append to the end if unclear
51+
52+
## Example Entry Formats
53+
54+
### authors.yaml (only if new author)
55+
```yaml
56+
github-username:
57+
name: Full Name
58+
website: https://github.com/github-username
59+
avatar: https://github.com/github-username.png
60+
```
61+
62+
### registry.yaml
63+
```yaml
64+
- title: Example Notebook Title
65+
description: Brief description of what this notebook covers and teaches users.
66+
path: category/notebook_name.ipynb
67+
authors:
68+
- github-username
69+
date: 'YYYY-MM-DD'
70+
categories:
71+
- Category Name
72+
```

.github/pull_request_template.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -24,6 +24,7 @@
2424
- [ ] Includes a problem statement or use case description
2525
- [ ] Code is well-commented and easy to follow
2626
- [ ] Includes expected outputs or results
27+
- [ ] Added entry to `registry.yaml` (run `/add-registry <notebook-path>` or add manually)
2728

2829
## Testing
2930

registry.yaml

Lines changed: 47 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,50 @@
11
# yaml-language-server: $schema=./.github/registry_schema.json
2+
- title: Giving Claude a Crop Tool for Better Image Analysis
3+
description: Give Claude a crop tool to zoom into image regions for detailed analysis
4+
of charts, documents, and diagrams.
5+
path: multimodal/crop_tool.ipynb
6+
authors:
7+
- nadine-anthropic
8+
date: '2025-11-22'
9+
categories:
10+
- Multimodal
11+
- Tools
12+
- title: Programmatic Tool Calling (PTC)
13+
description: Reduce latency and token consumption by letting Claude write code that
14+
calls tools programmatically in the code execution environment.
15+
path: tool_use/programmatic_tool_calling_ptc.ipynb
16+
authors:
17+
- PedramNavid
18+
date: '2025-11-24'
19+
categories:
20+
- Tools
21+
- title: Tool Search with Embeddings
22+
description: Scale Claude applications to thousands of tools using semantic embeddings
23+
for dynamic tool discovery.
24+
path: tool_use/tool_search_with_embeddings.ipynb
25+
authors:
26+
- henrykeetay
27+
date: '2025-11-24'
28+
categories:
29+
- Tools
30+
- title: Automatic Context Compaction
31+
description: Manage context limits in long-running agentic workflows by automatically
32+
compressing conversation history.
33+
path: tool_use/automatic-context-compaction.ipynb
34+
authors:
35+
- PedramNavid
36+
date: '2025-11-24'
37+
categories:
38+
- Tools
39+
- title: Low Latency Voice Assistant with ElevenLabs
40+
description: Build a low-latency voice assistant using ElevenLabs for speech-to-text
41+
and text-to-speech combined with Claude.
42+
path: third_party/ElevenLabs/low_latency_stt_claude_tts.ipynb
43+
authors:
44+
- Adriaan-ANT
45+
date: '2025-11-24'
46+
categories:
47+
- Integrations
248
- title: Prompting for Frontend Aesthetics
349
description: Guide to prompting Claude for distinctive, polished frontend designs
450
avoiding generic aesthetics.
@@ -523,3 +569,4 @@
523569
categories:
524570
- Multimodal
525571
- Tools
572+

0 commit comments

Comments
 (0)