Agent skill
learn
Index lecture note PDFs into the knowledge base
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/learn-surya-sunkari-continuous-algorithm
SKILL.md
Knowledge Base Indexer
You are indexing lecture notes from a CS 395T (Continuous Algorithms) assignment into a persistent knowledge base of theorems, definitions, and lemmas.
The target assignment folder is: $ARGUMENTS
PHASE 1: Validation
- Verify that
$ARGUMENTS/notes/exists and contains.pdffiles. If not, stop and tell the user. - Create the
knowledge_base/directory at the project root if it does not exist. - List all existing YAML files in
knowledge_base/so you know what's already indexed.
PHASE 2: Index New Notes
For each PDF file in $ARGUMENTS/notes/:
- Derive the YAML filename:
knowledge_base/<pdf-filename-without-extension>.yaml - Check if this YAML file already exists. If it does, skip this PDF and tell the user it's already indexed.
- If not indexed yet, read the PDF using the Read tool. For PDFs longer than 10 pages, read in chunks using the
pagesparameter. - Extract ALL of the following into structured YAML:
- Definitions (with number and full statement)
- Theorems (with number, name if any, full statement, and proof sketch if short)
- Lemmas (with number, name if any, full statement)
- Corollaries (with number and full statement)
- Propositions (with number and full statement)
- Key remarks (only if they state a useful result)
- Key intermediate results within proofs — if a proof contains a numbered equation, a named intermediate claim, or a step that is independently useful, capture it in
proof_notes.
- Write the YAML file following this schema:
source: "filename.pdf"
lecture_number: 5
title: "Lecture title extracted from PDF"
items:
- type: theorem # theorem | lemma | definition | corollary | proposition | remark
number: "5.1" # numbering as it appears in the notes
name: "Named theorem" # if the theorem has a name, otherwise empty string
statement: |
Full mathematical statement in plain text with LaTeX math notation
context: "Brief note on when/how this result is typically used"
proof_notes: # optional — omit if the proof has no citable internals
- label: "(3)" # equation/line label as it appears in the notes (e.g. "(3)", "Line 4", "Claim 1")
content: |
The exact equation or claim in LaTeX math notation
description: "What this equation/step establishes and when it is useful to cite directly"
Populate proof_notes whenever:
- The proof contains a numbered or labeled equation that could be reused independently
- The proof establishes an intermediate claim or inequality that is stronger or more specific than the theorem statement itself
- A specific line or step is the crux of the argument and could be invoked directly in another proof
PHASE 3: Report
Tell the user:
- How many PDFs were found in
$ARGUMENTS/notes/ - How many were newly indexed vs. already indexed
- Total number of items extracted (theorems, definitions, lemmas, etc.) from newly indexed PDFs
- Where the YAML files were saved
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?