图像生成
- 作者仓库星标 17
- 作者更新于 实时读取
- 作者仓库 vibe-study-skills
- 领域
- 文档
- 兼容 Agent
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- 信任分
- 88 / 100 · 社区维护
- 作者 / 版本 / 许可
- @szeyu · 未声明 license
- Token 消耗评级
- 低消耗
- 接入复杂程度
- 即装即用
- 是否需要外部 API Key
- 不需要
- 兼容的系统
- 未声明(默认跨平台)
- 底层运行要求
- 无特殊要求
- 文件与系统权限
-
- 只读
- 允许写入 / 修改
- 网络行为
- 仅限本地
- 安装命令数
- 26 条
档案由构建时根据 SKILL.md 与安装命令自动衍生,可能与作者实际意图存在差异。
需要注意: 未限定 allowed-tools,默认拥有全部工具权限。
---
name: study-notes-creator
description: Create organized, visual study notes with folder structures, diagrams, and example-based learnin…
category: 文档
runtime: 无特殊运行时
---
# study-notes-creator 输出预览
## PART A: 任务判断
- 适用问题:PRD、RFC、README、项目说明或知识库整理。
- 输入要求:目标材料、限制条件、期望输出和验收方式。
- 证据边界:围绕“Workflow / Step 1: Understand the Source / Step 2: Plan Folder Structure”读取原文规则,不把推断写成作者承诺。
## PART B: 执行结果
- **01** 任务判断:确认你的需求是否属于PRD、RFC、README、项目说明或知识库整理,并标出输入、限制和预期结果。
- **02** 执行计划:优先按“Workflow / Step 1: Understand the Source / Step 2: Plan Folder Structure”拆成步骤,说明每一步会读取什么、修改什么、产出什么。
- **03** 交付结果:给出可复制的命令、文件改动、检查清单或内容草稿,并说明如何继续迭代。
- **04** 风险边界:结合 读取文件、写入/修改文件、主要在本地完成、通常不需要额外 API Key 给出执行前确认项。
## Running Rules
- 读取文件、写入/修改文件;主要在本地完成;通常不需要额外 API Key。
- 先小样例验证,再放大到真实任务。
- 交付时同时给结果、检查口径和下一步迭代建议。 原文没有稳定的斜杠命令要求。安装验证后通常全局生效,直接在对话里点名这个 Skill 并描述任务即可。
告诉 Agent 目标文件或材料、期望结果、不可改范围、是否允许联网或执行命令。本 Skill 的权限画像是:读取文件、写入/修改文件。
先用一个小任务确认它会围绕“Workflow / Step 1: Understand the Source / Step 2: Plan Folder Structure”工作;涉及文件或命令时,先看 diff、日志、预览或测试结果。
检查最终产物是否包含明确结果、必要证据和下一步动作;如果输出泛泛而谈,就补充输入、边界和验收标准后重跑。
---
name: study-notes-creator
description: Create organized, visual study notes with folder structures, diagrams, and example-based learnin…
category: 文档
source: szeyu/vibe-study-skills
---
# study-notes-creator
## 什么时候使用
- study-notes-creator 是文档方向的技能,对外说明 适合处理README、PRD、RFC、教程和知识库文档,核心价值是把输入、判断、执行、验证和交付边界固定下来,避免 Agent 泛泛回答。 把任务拆成可执行、可检查、可…
- 面向PRD、RFC、README、项目说明或知识库整理,优先处理能明确输入、步骤和验收标准的工作。
## 需要提供什么
- 目标材料、目录范围、期望结果和不可改动内容。
- 是否允许联网、执行命令、读写文件或调用外部服务。
## 执行规则
- 围绕「Workflow / Step 1: Understand the Source / Step 2: Plan Folder Structure」组织步骤,不把推断写成作者事实。
- 读取文件、写入/修改文件;主要在本地完成;通常不需要额外 API Key。
- 先跑小样例,确认结果可检查后再扩大任务范围。
## 输出要求
- 给出最终产物、关键证据、验证方式和下一步动作。
- 信息不足时标记 unknown,不编造命令、平台或依赖。 作者原文负责流程事实;仓库文件负责来源和命令;流狐只补充适用场景、限制和质量判断。
skill "study-notes-creator" {
输入层 -> 用户目标 + 目标文件 + 禁止范围 + 验收标准
上下文层 -> Workflow / Step 1: Understand the Source / Step 2: Plan Folder Structure
规则层 -> SKILL.md 触发条件 / 执行顺序 / 输出格式
运行层 -> 无特殊运行时 | 读取文件、写入/修改文件 | 主要在本地完成
安全层 -> 通常不需要额外 API Key + 小任务验证 + diff / 日志复核
输出层 -> 可复制结果 + 检查清单 + 下一步迭代
} 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
先判断是否适合
作者设计意图
作者的方法与取舍
边界和复核