gp_scratch

.claude/skills/book.read_and_summarize_chapter/SKILL.md → .claude/skills/book.read_chapter/SKILL.md

@@ -49,20 +49,18 @@ the book markdown file.
 
 Return the content to the user for context.
 
-## Step 4: Summarize Content
+## Step 4: Print Content Structure
 
-- Write a summary using the same structure of the chapter and subchapter in
-  markdown headers
+- Write a structure of the chapter and subchapter in markdown headers
   - Use numbers of chapter (e.g., 1.) and subchapters (e.g., 1.1)
   - Use the chapter numbers that come from the book
 
-- For each chunk of text, summarize the text using rules from
-  @.claude/skills/text.summarize_in_bullet_points/SKILL.md
-
 ## Step 5: Answer Follow-up Questions
 
-Answer any questions the user asks about the content just read, referencing
-specific sections or concepts from the chapter summary.
+- Do not do anything else (e.g., summarize the content), but wait for the user
+  to ask questions
+- Answer any questions the user asks about the content just read, referencing
+  specific sections or concepts from the chapter summary.
 
 # Example
 
@@ -77,14 +75,4 @@ specific sections or concepts from the chapter summary.
   - Chapter 3: Graphical Models
     - 3.1 Directed Acyclic Graphs (DAGs)
     - 3.2 d-separation and Conditional Independence
-
-  # Summary:
-
-  - **Chapter 3: Graphical Models**: DAGs represent causal relationships through
-    nodes and directed edges; d-separation criterion determines conditional
-    independence from graph structure
-    - **3.1 DAGs**: Nodes represent variables, edges represent direct causal
-      effects, acyclicity prevents circular reasoning
-    - **3.2 d-separation**: Variables are d-separated if no open path exists;
-      d-separation implies conditional independence under causal model assumptions
   ```

.claude/skills/graphviz.causal_kg_style/SKILL.md

@@ -8,10 +8,10 @@ I will give you a description or an image and your task is to produce a
 Graphviz/DOT representation of that graph that follows the rules below exactly.
 
 The resulting graph should allow a knowledgeable reader to
-- distinguish causation from correlation at a glance
-- identify exogenous vs endogenous variables
-- identify latent vs observable variables
-- recognize interventions and counterfactuals
+- Distinguish causation from correlation at a glance
+- Identify exogenous vs endogenous variables
+- Identify latent vs observable variables
+- Recognize interventions and counterfactuals
 
 Use color to distinguish variable types consistently.
 
@@ -22,7 +22,6 @@ Use color to distinguish variable types consistently.
 - Use Graphviz DOT syntax
 - Use a directed graph (`digraph`)
 - Set `rankdir=LR` for left-to-right causal flow
-- Prefer readability over compactness
 - Use both `color` (border) and `fillcolor` + `style=filled` to encode variable
   type (do not rely on color alone; keep shape conventions too)
 

.claude/skills/markdown.fix_bullet_points/SKILL.md

@@ -4,34 +4,84 @@ description: Reorganize a markdown file to use bullet points and ensure all fenc
 
 - Given a markdown file passed from the user
 
-# Step 1
-- Make sure the text is organized in bullet points
+# Organize text in bullet points
+- Make sure all the text is organized in bullet points
+  ```
+  **What it does**:
+  - Extracts each page of a PDF file as a separate PNG image
+  - Numbers output files sequentially (slides001.png, slides002.png, etc.)
+  - Supports customizable DPI for image quality control
+  - Creates output directory automatically with optional from-scratch mode
+  ```
 
-# Step 2
+# Handle fenced div
 - Make sure that all fenced div have a syntax description (e.g., python,
   markdown, verbatim)
   - Bad
     ````markdown
     The simplest ripgrep command searches for a pattern in the current directory:
 
     ```bash
-    > rg "pattern"
+    > rig "pattern"
     ```
     ````
   - Good
     ````markdown
     - The simplest ripgrep command searches for a pattern in the current
       directory:
       ```bash
-      > rg "pattern"
+      > rig "pattern"
       ```
     ````
 
-# Step 3
+# Format commands
 - Make sure Linux / MacOS shell commands are prepended with:
   - `>` when they are bash commands
   - `docker>` when they are commands run inside Docker
   - `claude>` when they are commands run inside Claude
 
-# Step 4
-- Run `lint_txt.py -i <FILE>` to reformat the text
+# Do not abuse level 3 headers
+- Do not use header level 3, but use bold when there are too many of them with
+  too small of content
+- E.g., convert
+  ```
+  ### What It Does
+  ...
+
+  ### Examples
+  ...
+  ```
+  to
+  ```
+  **What it does**
+  ...
+
+  **Examples**
+  ...
+  ```
+
+# Do not abuse bold
+- Do not abuse bold in the explanation of commands
+  - Bad
+    ```
+    - **Extract with higher DPI** for better image quality:
+    ```
+  - Good
+    ```
+    - Extract with higher DPI for better image quality:
+    ```
+
+# Add table
+
+- If the file contains a description of commands add a table at the beginning
+  with a summary of all the commands
+  - E.g.,
+    ```
+    | Script                     | Location                                          | Description                                                                                                             |
+    | :------------------------- | :------------------------------------------------ | :---------------------------------------------------------------------------------------------------------------------- |
+    | `concatenate_pdfs.py`      | `helpers_root/dev_scripts_helpers/documentation/` | Combines multiple PDF files into a single PDF (used for creating full book from chapters)                               |
+    | `count_book_pages.py`      | `class_scripts/`                                  | Counts pages in all PDF files in `{DIR}/book/` directory using macOS `mdls` command                                     |
+  ```
+
+# Lint
+- At the end of the process, run `lint_txt.py -i <FILE>` to reformat the text

.claude/skills/markdown.format_rules/SKILL.md

@@ -3,10 +3,6 @@ description: Format markdown files according to conventions for clarity, structu
 model: haiku
 ---
 
-# Summary
-
-- This file contains conventions for writing markdown files
-
 # Goals and Philosophy
 
 - Make the text easy to consume for both humans and AI

.claude/skills/slides.add_visuals/SKILL.md

@@ -0,0 +1,26 @@
+---
+description: Propose visuals for each slides
+---
+
+- Given a markdown file with slides for a college class, where each slide title
+  is prepended with `*`
+
+# Leave structure unchanged
+- Maintain the structure of the text and keep the content of the existing text
+
+# For each slide
+- If a slide doesn't contain a picture or a diagram (e.g., graphviz), consider
+  what can be used to illustrate the concepts visually, e.g.,
+  - Propose a graphviz diagram
+  - Find an image on the Internet (download and save it in a dir
+    `proposed_images`)
+  - Propose the description of an image in the format
+    ```
+    <image>
+    Description of the image
+    </image>
+    ```
+
+# Ask user to confirm and decide
+- Make numbered list of proposed changes for the user
+- Once user confirms changes, perform the changes

.claude/skills/slides.criticize_structure/SKILL.md

@@ -0,0 +1,44 @@
+---
+description: Criticize and suggest improvements for class slides
+---
+
+- Given a Markdown file storing slides for a class (where each slide title is
+  prepended with `*`)
+
+# Propose improvements
+- Read the content and make suggestions on how to improve the class, numbering
+  each suggestion so that it's easy to refer to
+  - Do not make changes but only make proposals
+
+## Change order of slides
+- Propose how to organize the slides in a different flow, separating cohesive
+  chunks with level 1 and 2 headers
+  - E.g.,
+    ```
+    # Topic 1
+
+    ## Topic 1.1
+
+    * Slide 1
+
+    * Slide 2
+    ```
+
+## Slides to remove
+- Remove slides whose content is redundant or unclear
+
+## Slides to merge
+- Merge slides to remove redundant content
+
+## Fix content of slides
+- If a slide content is incorrect, propose how to fix it
+
+## Ignore TODOs and comments
+- Leave the TODOs or comments in the format
+  ```
+  // ...
+  ```
+  untouched
+
+# Ask the user which improvement needs to be done
+- After the user approves a subset of changes, perform the changes in place

.claude/skills/slides.fix_errors/SKILL.md

@@ -0,0 +1,13 @@
+---
+description: Fix slides without changing their structure
+---
+
+- Given a markdown file with slides for a college class, where each slide title
+  is prepended with `*`
+
+# Leave structure unchanged
+- Maintain the structure of the text and keep the content of the existing text
+
+# Fix mistakes
+- Fix English grammar
+- Fix any mistake only if you are sure about the correction

.claude/skills/slides.format_rules/SKILL.md

@@ -2,36 +2,26 @@
 description: Format slides for technical audiences following structured presentation conventions
 ---
 
-You are an expert writer of slides and presentation.
-
-# Audience
-
-- Your target is college graduate in computer science
+You are an expert writer of slides and presentation for college students
+  - Your target audience is college graduate in computer science
   - You need to be clear and precise
 
 # Formatting
-
 - Don't use emoji
 - Don't use page separators
-- Make examples for concepts whenever possible
+- Don't use unicode characters but use Latex symbols if needed
+  - Instead of → use $\to$
 
-# When I Ask You to Create a Slide
-
-- Each slide should start with <* Slide title>
-- Each slide contains at most 8 bullet point arranged in a hierarchical
-  structure
+# Slide format
+- Each slide should start with:
+  ```
+  * Slide title
+  ```
+- Each slide contains bullet point arranged in a hierarchical structure
   - Every line starts with a bullet point
   - Do not use period at the end of a phrase
 
-# Suggest Images When Possible
-
-- When an image might help with clarity, add a description of it like:
+- Use italic and add quotes for questions
   ```
-  <image>
-  Description of the image
-  </image>
+  - E.g., _"If we lower prices by 10%, will revenue increase?"_
   ```
-
-# Output Is Markdown
-
-- Write the output in a markdown format in the form of code

.claude/skills/slides.read_chapter_and_write_slides/SKILL.md

@@ -0,0 +1,6 @@
+---
+description: Read a chapter of a book and write lecture slides
+---
+
+/book.read_chapter /Users/saggese/src/notes1/books/facure2.md "Neutral Controls"
+/slides.write_slides create one slide for the "Neutral controls"