skills/92bilal26/summary-generator/SKILL.md
This skill should be used when generating lesson summaries for educational content. It extracts key concepts, mental models, patterns, and common mistakes from lesson markdown files using a Socratic extraction process. Use this skill when a lesson file needs a `.summary.md` companion file, or when reviewing/refreshing existing summaries.
npx skillsauth add aiskillstore/marketplace summary-generatorInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
This skill generates concise, scannable summaries for educational lessons by extracting the essential learning elements through Socratic questioning. Summaries serve two user needs: quick review (students returning to refresh understanding) and just-in-time reference (students checking back mid-practice).
To generate a summary, work through these questions in order. Each question extracts content for one section of the summary.
"If a student remembers only ONE thing from this lesson tomorrow, what must it be?"
Extract the single most important takeaway in 1-2 sentences. This should be the foundational insight that unlocks everything else.
Test: Could someone who only read this sentence explain the lesson's purpose to a peer?
"What mental frameworks does this lesson install in the student's mind? What 'lenses' do they now see problems through?"
Extract 2-3 mental models—these are the reusable thinking patterns, not facts. Look for:
Test: Are these transferable to new situations, or are they lesson-specific facts?
"What practical techniques or patterns does this lesson teach? What can the student now DO that they couldn't before?"
Extract 2-4 actionable patterns from the lesson. These come from:
Test: Could a student apply these patterns without re-reading the lesson?
"How does AI help with this topic? What prompts or collaboration patterns make the difference?"
Extract 1-2 insights about working with AI on this topic. This should NOT expose the Three Roles framework—focus on practical collaboration patterns.
Note: Skip this section if the lesson doesn't involve AI collaboration (Layer 1 content).
"Where do students typically go wrong? What misconceptions does this lesson correct?"
Extract 2-3 common mistakes from:
Test: Would knowing these prevent a real mistake?
"What prerequisite knowledge does this build on? Where does this lead next?"
Extract navigation links:
Note: This section is optional. Skip if connections aren't clear or useful.
Generate the summary following this exact structure:
### Core Concept
[1-2 sentences from Question 1]
### Key Mental Models
- **[Model Name]**: [Brief explanation]
- **[Model Name]**: [Brief explanation]
- **[Model Name if needed]**: [Brief explanation]
### Critical Patterns
- [Pattern/technique 1]
- [Pattern/technique 2]
- [Pattern/technique 3 if applicable]
- [AI collaboration pattern if applicable]
### Common Mistakes
- [Mistake 1 and why it's wrong]
- [Mistake 2 and why it's wrong]
- [Mistake 3 if applicable]
### Connections
- **Builds on**: [Prior concept/chapter]
- **Leads to**: [Next concept/chapter]
Adjust summary length based on lesson complexity (from frontmatter proficiency_level):
| Proficiency | Target Length | Reason | |-------------|---------------|--------| | A1-A2 (Beginner) | 150-250 words | Simpler concepts, fewer patterns | | B1-B2 (Intermediate) | 200-350 words | More nuanced, multiple techniques | | C1-C2 (Advanced) | 250-400 words | Complex topics, many interconnections |
Following Principle 7: Minimal Sufficient Content, summaries must NOT contain:
Summary files are named by appending .summary.md to the lesson filename (without extension):
# Lesson file:
apps/learn-app/docs/05-Python/17-intro/01-what-is-python.md
# Summary file:
apps/learn-app/docs/05-Python/17-intro/01-what-is-python.summary.md
.summary.md fileFor a lesson teaching Python data types at A2 proficiency:
### Core Concept
Data types are Python's classification system—they tell Python "what kind of data is this?" and "what operations are valid?"
### Key Mental Models
- **Types → Operations**: Numbers enable math; text enables joining; booleans enable decisions
- **Type Mismatch → Error**: `5 + "hello"` fails because Python can't add numbers to text
- **Type Decision Framework**: Ask "What kind of data?" to determine the right type
### Critical Patterns
- Use `type()` to verify what type Python assigned: `type(42)` returns `<class 'int'>`
- Type hints express intent: `age: int = 25` tells both AI and humans what you expect
- 7 categories cover all data: Numeric, Text, Boolean, Collections, Binary, Special (None)
### Common Mistakes
- Storing numbers as text (`"25"` instead of `25`) prevents math operations
- Forgetting that `0.1 + 0.2` doesn't exactly equal `0.3` (floating point precision)
- Mixing types in operations without explicit conversion
### Connections
- **Builds on**: Python installation and first programs (Chapter 17)
- **Leads to**: Deep dive into numeric types and text handling (Chapters 18-20)
Word count: ~175 words (appropriate for A2)
development
Apple Human Interface Guidelines for content display components. Use this skill when the user asks about charts component, collection view, image view, web view, color well, image well, activity view, lockup, data visualization, content display, displaying images, rendering web content, color pickers, or presenting collections of items in Apple apps. Also use when the user says how should I display charts, what's the best way to show images, should I use a web view, how do I build a grid of items, what component shows media, or how do I present a share sheet. Cross-references: hig-foundations for color/typography/accessibility, hig-patterns for data visualization patterns, hig-components-layout for structural containers, hig-platforms for platform-specific component behavior.
tools
Automate HelpDesk tasks via Rube MCP (Composio): list tickets, manage views, use canned responses, and configure custom fields. Always search tools first for current schemas.
testing
Expert Haskell engineer specializing in advanced type systems, pure functional design, and high-reliability software. Use PROACTIVELY for type-level programming, concurrency, and architecture guidance.
tools
GraphQL gives clients exactly the data they need - no more, no less. One endpoint, typed schema, introspection. But the flexibility that makes it powerful also makes it dangerous. Without proper controls, clients can craft queries that bring down your server. This skill covers schema design, resolvers, DataLoader for N+1 prevention, federation for microservices, and client integration with Apollo/urql. Key insight: GraphQL is a contract. The schema is the API documentation. Design it carefully.