study-notes-creator
- Repo stars 17
- Author updated Live
- Author repo vibe-study-skills
- Domain
- Documentation
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @szeyu · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools,默认拥有全部工具权限。
---
name: study-notes-creator
description: Create organized, visual study notes with folder structures, diagrams, and example-based learnin…
category: documentation
runtime: no special runtime
---
# study-notes-creator output preview
## PART A: Task fit
- Use case: Create organized, visual study notes with folder structures, diagrams, and example-based learning from source materials (PDFs, lecture notes, documentation). Use when creating structured learning materials, exam preparation notes, or educational documentation. Triggers - organize study notes, create visual learning materials, generate notes with diagrams, exam prep notes, example-based learning..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Workflow / Step 1: Understand the Source / Step 2: Plan Folder Structure” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Create organized, visual study notes with folder structures, diagrams, and example-based learning from source materials (PDFs, lecture notes, documentation). Use when creating structured learning materials, exam preparation notes, or educational documentation. Triggers - organize study notes, create visual learning materials, generate notes with diagrams, exam prep notes, example-based learning.”.
- **02** When the source has headings, the agent prioritizes “Workflow / Step 1: Understand the Source / Step 2: Plan Folder Structure” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Start with a small task and check whether the result follows “Workflow / Step 1: Understand the Source / Step 2: Plan Folder Structure”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: study-notes-creator
description: Create organized, visual study notes with folder structures, diagrams, and example-based learnin…
category: documentation
source: szeyu/vibe-study-skills
---
# study-notes-creator
## When to use
- Create organized, visual study notes with folder structures, diagrams, and example-based learning from source material…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Workflow / Step 1: Understand the Source / Step 2: Plan Folder Structure” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "study-notes-creator" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Workflow / Step 1: Understand the Source / Step 2: Plan Folder Structure
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
} Study Notes Creator
Transform source materials into organized, visual study notes with themed folders, rich diagrams, and example-based learning.
Workflow
flowchart LR
A[Source Materials] --> B[Extract Topics]
B --> C[Plan Structure]
C --> D[Create Notes]
D --> E[Add Diagrams + Examples]
E --> F[Build Index]
Step 1: Understand the Source
- Read the source - PDFs, lecture notes, existing docs
- Identify 5-8 main topics - Major themes
- Find subtopics - What falls under each theme?
- Note example opportunities - Where can real examples help?
Step 2: Plan Folder Structure
subject/
├── README.md # Master index
├── concepts/ # Core theory
│ ├── 01-introduction.md
│ └── 02-fundamentals.md
├── techniques/ # How-to procedures
│ ├── 01-method-a.md
│ └── 02-method-b.md
├── examples/ # Worked problems
│ ├── 01-basic-examples.md
│ └── 02-advanced-examples.md
└── practice/ # Exercises
└── 01-exercises.md
Step 3: Note Template
# [Topic Title]
One sentence summary.
## Overview
[Mermaid diagram showing the main concept]
## Key Concepts
### Concept 1
Brief explanation.
**Example:**
[Concrete example with real-world scenario]
## Summary Table
| Term | Definition | Example |
|------|------------|---------|
| A | What A is | Real use case |
## Practice Problems
1. Problem statement
<details>
<summary>Solution</summary>
Step-by-step solution
</details>
## Related
- [[other-note]] - Connection
Step 4: Mermaid Diagrams (Primary)
Flowchart (Process Flow)
flowchart LR
A[Start] --> B[Process]
B --> C{Decision}
C -->|Yes| D[Action]
C -->|No| E[End]
Use for: Processes, decision trees, algorithms, workflows
Flowchart TB (Hierarchy/Tree)
flowchart TB
A[Main Topic] --> B[Branch A]
A --> C[Branch B]
A --> D[Branch C]
B --> E[Detail 1]
B --> F[Detail 2]
C --> G[Detail 3]
Use for: Taxonomies, classifications, org charts, topic breakdowns
Sequence Diagram
sequenceDiagram
participant A as Actor
participant S as System
A->>S: Request
S-->>A: Response
A->>S: Follow-up
Use for: Interactions, conversations, API calls, cause-effect chains
State Diagram
stateDiagram-v2
[*] --> Idle
Idle --> Active : Start
Active --> Success : Complete
Active --> Error : Fail
Error --> Idle : Retry
Success --> [*]
Use for: Lifecycles, status changes, phases, state machines
Cycle Diagram
flowchart LR
A[Stage 1] --> B[Stage 2]
B --> C[Stage 3]
C --> D[Stage 4]
D --> A
Use for: Water cycle, feedback loops, iterative processes, life cycles
Timeline
timeline
title Historical Events
1800 : Event A
1850 : Event B
1900 : Event C
1950 : Event D
Use for: Historical timelines, project phases, evolution of concepts
Mind Map
mindmap
root((Topic))
Branch A
Detail 1
Detail 2
Branch B
Detail 3
Detail 4
Use for: Brainstorming, topic overviews, concept relationships
Step 5: ASCII Diagrams (Edge Cases)
Use ASCII only for:
- Overview boxes with custom text layout
- Layer/stack diagrams
- Comparison layouts
Overview Box
┌─────────────────────────────────────────────────────────────────────────────┐
│ TOPIC TITLE │
├─────────────────────────────────────────────────────────────────────────────┤
│ │
│ Key Point 1 Key Point 2 Key Point 3 │
│ │ │ │ │
│ [details] [details] [details] │
│ │
└─────────────────────────────────────────────────────────────────────────────┘
Layers/Stack
┌─────────────────────────────────────────────────────────────────────────────┐
│ Layer 4 (Top) │
├─────────────────────────────────────────────────────────────────────────────┤
│ Layer 3 │
├─────────────────────────────────────────────────────────────────────────────┤
│ Layer 2 │
├─────────────────────────────────────────────────────────────────────────────┤
│ Layer 1 (Bottom) │
└─────────────────────────────────────────────────────────────────────────────┘
Box Characters Reference
Corners: ┌ ┐ └ ┘ Lines: ─ │ T-joints: ├ ┤ ┬ ┴ Arrows: ▶ ▼ ◀ ▲
Step 6: Example-Based Learning Patterns
Pattern 1: Concept → Example → Variation
## [Concept Name]
**Definition:** Brief explanation.
**Example:**
[Concrete, real-world scenario]
**Variation:**
What if [different condition]? → [Different outcome]
Cross-discipline examples:
| Subject | Concept | Example | Variation |
|---|---|---|---|
| Biology | Osmosis | Red blood cells in salt water shrink | In pure water? → Cells swell |
| Economics | Supply/Demand | Oil price rises when OPEC cuts production | New oil discovered? → Price falls |
| Physics | Momentum | Bowling ball vs tennis ball at same speed | Same mass, different speed? |
| History | Cause/Effect | Industrial Revolution → urbanization | No steam engine? |
Pattern 2: Problem → Solution → Explanation
**Problem:** [Specific question]
**Solution:**
Step 1: [Action]
Step 2: [Action]
Result: [Answer]
**Why it works:** [Underlying principle]
Pattern 3: Compare and Contrast
| Aspect | Topic A | Topic B |
|---|---|---|
| Feature 1 | ... | ... |
| Feature 2 | ... | ... |
Similarities: Both... Key Difference: A is... while B is...
Step 7: Build the Index
# [Subject Name]
Brief description.
## Quick Navigation
### 📚 Core Concepts
- [[concepts/01-topic|Topic Name]] - Brief description
### 🔧 Techniques/Methods
- [[techniques/01-method|Method Name]] - Brief description
### 💡 Examples
- [[examples/01-basic|Basic Examples]] - Start here
---
*Last updated: YYYY-MM-DD*
Quality Checklist
- Every note has at least 1 Mermaid diagram
- Every concept has at least 1 concrete example
- Examples use real, relatable scenarios
- Folder structure is numbered for reading order
- README links to all notes
- Wikilinks connect related topics
Decide Fit First
Design Intent
How To Use It
Boundaries And Review