使用经过验证的知识管理系统，保持您的Obsidian保险库有序、连接且健康。基于ACE框架（Atlas/Calendar/Efforts）、LYT（连接你的思维）约定以及ARC工作流程（添加 - 关联 - 沟通）。

你得到了什么

三种互补技能协同工作：

• 创意管理 - 创建笔记，构建MOC，连接概念，维护结构
• 创意丰富 - 处理文章和研究，提取概念，捕捉重复
• 理念性维护 - 审计你的保险库，发现断裂链接，识别孤立笔记

高效的工作流程

审计并识别缺口：

进行一次完整的保险库审计。给我展示挤压点（概念被提及10+次且无MOC），这样我就知道在哪里建新结构

在我的保险库里找到所有孤儿笔记。告诉我哪些可以关联到现有的MOC，哪些是归档的

检查我的前置要求，找出缺少必需元数据的笔记

系统性地吸收知识：

我收集了8篇关于事件来源的研究论文。逐篇处理：提取核心概念，将每个概念分类为原则/模式/概念，检查重复内容后再做笔记

Ideaverse Skills

Keep your Obsidian vault organized, connected, and healthy using proven knowledge management systems. Built on the ACE framework (Atlas/Calendar/Efforts), LYT (Linking Your Thinking) conventions, and the ARC workflow (Add - Relate - Communicate).

What you get

Three complementary skills that work together:

• ideaverse - Create notes, build MOCs, link concepts, maintain structure
• ideaverse-enrichment - Process articles and research, extract concepts, catch duplicates
• ideaverse-maintenance - Audit your vault, find broken links, identify orphaned notes

Effective workflows

Audit and identify gaps:

Run a full vault audit. Show me squeeze points (concepts referenced 10+ times without a MOC) so I know where to build new structure

Find all orphan notes in my vault. Tell me which ones could be linked to existing MOCs versus archived

Check my frontmatter compliance and identify notes missing required metadata

Assimilate knowledge systematically:

I’ve collected 8 research papers on event sourcing. Process them one by one: extract core concepts, classify each as principle/pattern/concept, check for duplicates before creating notes

Add these bookmarks from my vault. For each: extract atomic concepts, check if they already exist, add to appropriate MOC with proper relationships

Extract the actionable workflows from this article and create process notes linked to existing related concepts

Link and improve structure:

I see Distributed Systems is referenced 34 times. Create a MOC for it, reorganize related notes underneath, and show me the new structure

Review my APIs MOC and identify child concepts that lack proper definition or are missing connections to related patterns

Find all notes linking to Microservices but not yet organized. Create hierarchy and add them to a coherent MOC

Maintain vault health:

Find broken links introduced recently and fix them

Which notes haven’t been touched in 3+ months and might be candidates for archival?

Show me if my MOCs are getting bloated (which ones exceed 50 links and should be split?)

Installation

Use skills.sh (no installation needed):

npx skills add mrfelton/ideaverse

Getting started

• New to ideaverse? Start with skills/ideaverse/SKILL.md to learn the methodology
• Want to add content? See skills/ideaverse-enrichment/SKILL.md for knowledge assimilation
• Need to audit your vault? Check skills/ideaverse-maintenance/SKILL.md for diagnostics