generate_slides_link
Create interactive learning slides to explain technical concepts from codebases. Generate Marble platform links for tutorials based on code analysis and structured queries.
Instructions
Use this tool to generate a Marble platform link for interactive learning slides that EXPLAIN or TEACH concepts. Trigger this for ANY mention of: 'slides', 'marble slides', 'explain', 'teach me', 'show me', 'help me understand', 'how does X work', 'how is X done', 'how are X generated', 'walkthrough', 'tutorial', 'lesson', 'presentation', 'break down', 'give me an explanation', or similar explanation/teaching phrases. IMPORTANT: The query parameter must be LIMITED TO 6 PARAGRAPHS MAXIMUM. Before calling this tool, you should: 1) Read relevant code files from the codebase, 2) Analyze the code patterns and structure, 3) Summarize the most important context into 6 paragraphs or fewer. Focus on quality over quantity - include only the most relevant details. CRITICAL: After calling this tool, you MUST include the returned markdown link in your response to the user. The tool returns a clickable link - DO NOT just summarize or describe what the slides contain. Always show the actual link so the user can click it.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| title | Yes | A short, concise title for the slides (e.g., 'React Hooks', 'Authentication Flow', 'Database Design'). Should be free of special characters except spaces. This will be used as the link text. | |
| query | Yes | A comprehensive but CONCISE query LIMITED TO 6 PARAGRAPHS MAXIMUM. Each paragraph should cover one key aspect: (1) The main topic or concept to explain, (2) Key code patterns or snippets (keep code examples brief), (3) Important implementation details, (4) How the concept is used in context, (5) Specific focus areas, (6) Any additional critical context. DO NOT exceed 6 paragraphs - summarize and prioritize the most important information. Example: 'Explain React hooks in our codebase. We use useState for local state management, particularly in UserProfile.tsx for form data. Our useEffect patterns handle data fetching with cleanup functions to prevent memory leaks. The dependency array is carefully managed to avoid infinite loops. Focus on explaining these patterns and best practices.' |