使用方法
- 复制安装命令，在自己的智能体环境安装前先检查源码包。
- 从原始文档核对所需工具、凭据和支持的宿主。
- 说明输入材料与期望交付物，并对照来源检查输出。
npx skills add https://github.com/szeyu/vibe-study-skills --skill obsidian-notes-creator开始前需了解
- 安装不包含模型订阅、API 额度或访问文件的权限。
- 仓库星数和安装量反映活跃情况，不等于独立质量或安全测试。
按源仓库内容呈现，保留标题、案例、代码、表格、链接以及原文引用的演示图片。
Obsidian Notes Creator
Make notes accurate, understandable, and useful for solving unfamiliar problems. Match depth to the learner and the requested scope; decoration and length are not evidence of quality.
1. Inspect and choose the mode
- Create: identify the source, audience, prerequisites, and learning objectives before choosing a structure.
- Improve: read existing notes, neighbouring notes, assets, and relevant vault instructions. Repair and deepen those files in place. Preserve filenames, folders, links, original dates, and useful author wording. Do not create a parallel study guide, rename files, or impose a new folder tree unless requested or necessary to the task.
- Audit: report specific gaps with file references; do not silently rewrite an audit-only request.
For a folder-wide task, inventory every Markdown file first. Track each as unreviewed, reviewed unchanged, improved, or unresolved, with a short reason. A small selection of polished notes is a targeted pass, not a completed folder review. Keep this working record outside the notes unless requested.
Defaults: answers and solutions are directly visible; SVG figures have a white background. Explicit user preferences override these defaults.
2. Understand before expanding
Identify missing reasoning, prerequisites, assumptions, definitions, and misleading claims. Distinguish source statements from derived examples and uncertain material. Keep source citations near the claims they support; never invent page numbers, measurements, or experimental results.
Prioritise correctness, complete worked reasoning, and useful connections. Add a visual, analogy, table, or exercise only when it teaches something the existing explanation does not.
- Single note: adaptable content modules.
- Multi-file notes: ownership, granularity, and preservation.
- Index notes: update existing navigation when needed.
3. Explain and demonstrate
For unfamiliar material, connect motivation and intuition to the formal statement. Reference notes may lead with a definition; worked problems may lead with the question. No mandatory analogy or diagram quota.
- Intuition and mathematics: symbols, assumptions, derivations, and limits.
- Analogies: explicit mapping and where it breaks.
- Examples: complete solutions, independent checks, and diagnostic questions.
- Comparisons: method choice, guarantees, and fair evidence.
4. Use the appropriate representation
Choose prose, a table, ASCII, Mermaid, or SVG according to what the reader needs to see. Keep equations in rendered LaTeX. Make visuals consistent with the surrounding worked example.
5. Verify and report honestly
Use the verification workflow and quality checklist. Verify calculations separately from rendering. Inspect generated figures at their intended embed size. Check changed links and assets.
Report coverage, substantive improvements, checks actually run, and unresolved issues. Distinguish reviewed, executed, and rendered. Never claim exhaustive validation from samples, syntax checks, or file counts alone.
